agentleFS
hhhyyyy99hhhyyyy99/prot-skills/.agents/skills/sync-agent-skills/SKILL.md

sync-agent-skills

Skill7 starsChanged 5 months agoMITView on GitHub

Maintain repository agent skills across Codex and Claude. Use when adding, removing, renaming, or editing skills under `.agents/skills`, when Claude cannot see repository skills, when `.claude/skills` symlinks need to be generated or checked, or when updating the skill loading bridge between `.agents/skills` and tool-specific skill directories.

1 other project uses a version of this.

Adopted by

Most recently taken up by

  • Other versions1 project uses a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 1

    1. JeffreyFerreiras/ai-skills★ 1same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository7 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

12 rules. About 0 are common, 4 are distinctive, and 8 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 8

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Use .agents/skills as the only maintained source for repository skills.

    line 8
  2. Very specific:

    Read .agents/skills/README.md to confirm the current loading policy.

    line 12
  3. Very specific:

    Put durable repository rules in .agents/rules/.

    line 13
  4. Distinctive:

    After adding, removing, renaming, or editing repository skills, run:

    line 15
  5. Distinctive:

    Verify the bridge with:

    line 21
  6. Distinctive:

    If package scripts or the sync script changed, also run:

    line 28
  7. Very specific:

    Do not copy skill contents into .claude/skills.

    line 36
  8. Very specific:

    Do not maintain .claude/skills by hand except to inspect or remove broken local state after the sync script reports a conflict.

    line 37
  9. Very specific:

    Treat .agents/skills as tracked repository source.

    line 39
  10. Very specific:

    Treat .claude/skills as generated local symlinks for Claude.

    line 40
  11. Distinctive:

    Do not overwrite existing non-symlink Claude skills.

    line 41
  12. Very specific:

    Only remove stale Claude symlinks that point back into this repository's .agents/skills.

    line 42

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Sync Agent Skills

Use .agents/skills as the only maintained source for repository skills.

Workflow

  1. Read .agents/skills/README.md to confirm the current loading policy.
  2. Put durable repository rules in .agents/rules/; put reusable workflows in .agents/skills/<skill-name>/SKILL.md.
  3. After adding, removing, renaming, or editing repository skills, run:

    pnpm skills:sync
  4. Verify the bridge with:

    pnpm skills:check
    pnpm vitest run scripts/tests/sync-agent-skills.test.ts
  5. If package scripts or the sync script changed, also run:

    pnpm harness:check:release

Safety Rules

  • Do not copy skill contents into .claude/skills.
  • Do not maintain .claude/skills by hand except to inspect or remove broken local state after the sync script reports a conflict.
  • Treat .agents/skills as tracked repository source.
  • Treat .claude/skills as generated local symlinks for Claude.
  • Do not overwrite existing non-symlink Claude skills.
  • Only remove stale Claude symlinks that point back into this repository's .agents/skills.

Expected Bridge

pnpm skills:sync creates links shaped like:

.claude/skills/<skill-name> -> ../../.agents/skills/<skill-name>

pnpm skills:check should report:

Agent skills are in sync.

Restart Claude or Codex sessions after skill changes if the tool does not pick up the updated skill list.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.