sync-from-vibe-workflow

Convert vibe-workflow skills into Codex-compatible frontmatter and invocation formats.

4|1|Updated Jan 11, 2026
One-click install
npx skills add https://github.com/doodledood/codex-workflow --skill sync-from-vibe-workflow
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sync-from-vibe-workflow
Source: https://github.com/doodledood/codex-workflow/tree/main/.claude/skills/sync-from-vibe-workflow
Command: npx skills add https://github.com/doodledood/codex-workflow --skill sync-from-vibe-workflow

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Syncs and harmonizes skill implementations between claude-code-plugins vibe-workflow and the codex-workflow repository, ensuring Claude Code features map to Codex equivalents.

Core Features & Use Cases

  • Automated syncing: replicate upstream vibe-workflow skills to Codex format with Codex-adapted frontmatter and invocation styles.
  • Agent-to-skill adaptation: translate subagent or agent-based implementations into inline Codex workflows.
  • Validation & governance: verify frontmatter, references, and file mappings during sync.

Quick Start

Run a sync from vibe-workflow to update this repository with Codex-adapted skill implementations.

Frequently Asked Questions about sync-from-vibe-workflow

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I sync Claude Code vibe-workflow skills to Codex format?

To sync vibe-workflow skills to Codex, this skill automates the replication of upstream implementations, adapting Claude Code frontmatter and invocation styles into Codex-compatible formats.

What is the best way to convert vibe-workflow subagent patterns for Codex?

Converting vibe-workflow subagent patterns for Codex is handled by translating agent-based implementations into inline Codex workflows, mapping agent logic directly to Codex equivalents.

Does converting Skill invocations to Codex preserve AGENTS.md references?

Yes, converting Skill invocations to Codex preserves AGENTS.md references while translating Skill("vibe-workflow:skill-name") calls into the $skill-name format required by Codex.

How do I validate frontmatter correctness after syncing workflows to Codex?

Validating frontmatter after syncing workflows to Codex is built into the process, which verifies frontmatter fields, file mappings, and AGENTS.md references to ensure governance and correctness.

Can I automate phase-driven sync across auxiliary workflows for Codex?

Yes, phase-driven sync across core and auxiliary workflows is fully automated, coordinating and harmonizing all vibe-workflow skill implementations into the codex-workflow repository.

What are the limitations of translating Claude Code agents into inline Codex executions?

Translating Claude Code agents into inline Codex executions requires mapping specific agent logic to Codex equivalents, meaning complex subagent patterns must be carefully restructured as inline workflows.