sync-tools

Solid

Generate multi-CLI distribution packages from the Claude Code plugin. Converts shared skills and package assets for OpenCode, Codex CLI, and Pi under dist/. Run after changing plugin components to keep distributions in sync.

AI & Automation 69 stars 9 forks Updated today MIT

Install

View on GitHub

Quality Score: 87/100

Stars 20%
61
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# /sync-tools — Multi-CLI Distribution Generator Generate distribution packages for OpenCode, Codex CLI, and Pi from the Claude Code plugin. **Input**: `$ARGUMENTS` — optional CLI name (`opencode`, `codex`, `pi`) to sync one target. Empty = all targets. ## Paths | Role | Path | |------|------| | Sources (read-only) | `claude-plugins/manifest-dev/` and `claude-plugins/manifest-dev-tools/` | | Output | `dist/{opencode,codex,pi}/` | | Conversion rules | `.claude/skills/sync-tools/references/{cli}-cli.md` | | Per-CLI sync state | `dist/{cli}/.sync-meta.json` (records last-synced source SHA — drives diff-first workflow) | | Pi namespace metadata | `dist/pi/component-namespaces.json` (component → owning plugin; Pi only) | | GitHub repo | `doodledood/manifest-dev` | ## Scope Sync only these source payloads: - `claude-plugins/manifest-dev/` — core workflow skills. - `claude-plugins/manifest-dev-tools/` — tools skills. Both plugins are skills-only — manifest-dev ships no agents or hooks on any target (the former functional agents are skills). Never sync other plugins (e.g., `manifest-dev-collab` — uses Agent Teams/Slack, inherently incompatible). Never modify source files. Skip `sync-tools` skill from output (meta-tool). **Namespacing model is per-CLI** (see each reference file): - **Plugin-native targets (Codex, OpenCode)**: the plugin is the distribution unit. Codex: two plugins (`manifest-dev`, `manifest-dev-tools`) each bundle their skills under original names. OpenCode: ...

Details

Author
doodledood
Repository
doodledood/manifest-dev
Created
6 months ago
Last Updated
today
Language
Python
License
MIT

Integrates with

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Listed

sync-configs

Audit and sync Claude Code and Codex CLI configurations so both tools share the same instructions, skills, subagents, MCP servers, hooks, and permission intent. Accepts an optional argument naming one skill, agent, or config file to sync just that item without a full audit. Use this whenever the user mentions config drift, syncing/aligning Claude and Codex, AGENTS.md vs CLAUDE.md differences, keeping skills or agents consistent across AI CLIs, or after editing one tool's config and wanting the other to match — e.g. "sync this skill to codex", "I changed my-agent.md, mirror it". Also use when the user asks "are my Claude and Codex setups aligned?" or wants to migrate config from one tool to the other.

1 Updated 4 days ago
supermodo
AI & Automation Listed

syncing-agent-skills

Keeps skill definitions aligned between Claude Code and Codex. Use when creating, migrating, renaming, or updating skills that must work across `.claude/skills` and `.agents/skills`, or when auditing drift between the two systems.

8 Updated today
dork-labs
AI & Automation Solid

sync-claude-code-plugins

Sync the prompt-engineering plugin from a local clone of claude-code-plugins into .claude/ so the repo is self-contained for isolated/web environments. Copies agents/skills, removes only previously-synced items that disappeared upstream. Other content in .claude/ is left alone. Use when asked to sync claude-code-plugins, pull prompt-engineering, refresh prompt-engineering plugin.

69 Updated today
doodledood