sync-agent-skills

Synchronizes agent skills and MCP configurations across Pi, OMP, Claude Code, OpenCode, and Codex.

Updated Aug 22, 2026
One-click install
npx skills add https://github.com/MSC72m/DevForge --skill sync-agent-skills-msc72m
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: sync-agent-skills
Source: https://github.com/MSC72m/DevForge/tree/main/skills/sync-agent-skills
Command: npx skills add https://github.com/MSC72m/DevForge --skill sync-agent-skills-msc72m

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Managing skills across multiple AI coding harnesses (Pi, OMP, Claude Code, OpenCode, Codex) is error-prone because each stores configuration in different filesystem paths. This Skill provides a repeatable procedure to add, update, and verify skills while keeping a single source of truth. ## Core Features & Use Cases - Centralized Skill Vault: Maintains ~/.agents/skills/ as the single source of truth, with all harnesses pointing to it via managed symlinks. - Step-by-Step Skill Onboarding: Guides creation of new skill directories with valid frontmatter, symlink verification, and Codex-specific per-folder symlinks. - Git-Backed Sync: Commits new or updated skills back to the DevForge repository for cross-machine reproduction. - Use Case: After writing a new skill locally, follow this procedure to symlink it into Codex, copy it into the DevForge repo, and push it so every machine and harness picks it up. ## Quick Start Ask the agent to add a new skill named my-skill and sync it across all harnesses using the DevForge workflow.

Frequently Asked Questions about sync-agent-skills

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

FAQPage Schema
How do I add a new skill across multiple AI coding agents?▼

Create the skill directory with a SKILL.md file containing name and description frontmatter inside ~/.agents/skills/. Then verify symlinks for Pi, OMP, Claude Code, and OpenCode, add a per-folder symlink for Codex, and commit the skill to the DevForge repository.

How to sync Claude Code and Codex skills from one directory?▼

Keep all skills in ~/.agents/skills/ as the single source of truth. Claude Code uses a directory-level symlink at ~/.claude/skills, while Codex requires individual symlinks from ~/.codex/skills/<skill-name> to each skill folder.

Why does Codex not detect a newly added skill?▼

Codex uses individual symlinks rather than a single directory symlink, so new folders are not picked up automatically. Run ln -sfn ~/.agents/skills/<skill-name> ~/.codex/skills/<skill-name> to register the new skill.

Can I replace the Pi or OMP skills folder with a real directory?▼

No, ~/.pi/agent/skills and ~/.omp/agent/skills must remain symlinked to ~/.agents/skills. Replacing them with standalone directories breaks the single-source-of-truth invariant and causes skills to diverge across harnesses.

How do I back up new skills to the DevForge repository?▼

Copy the skill folder into ~/code/DevForge/skills/, then run git add, commit with a feat(skills) message, and push to origin main. This keeps the vault reproducible on new machines via the sync script.