agentleFS
paulo-yamagishipaulo-yamagishi/claude-code-setup/.claude/skills/sync-skills/SKILL.md

sync-skills

Skill2 starsChanged 9 months agoMITView on GitHub

Check /setup and /bootstrap skills for consistency with core guides

22 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use explain, create-skill and 3 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • sunnyclinches44Skill

    explain

    Explains code using real-world analogies and ASCII diagrams

    Also in 3 projects that use this

  • ElasticSkill

    create-skill

    Interactively create a new Claude Code skill and add it to the elastic-docs-skills catalog. Use when the user wants to generate a new skill, scaffold a slash command, or build automation for docs tasks.

    Also in 3 projects that use this

  • MicrosoftSkill

    handoff

    Compact the current conversation into a handoff document for another agent to pick up.

    Also in 4 projects that use this

  • SentrySkill

    commit

    Create commit messages following Sentry conventions. Use when committing code changes, writing commit messages, or formatting git history. Follows conventional commits with Sentry-specific issue references.

    Also in 3 projects that use this

  • GoogleSkill

    grill-me

    A relentless interview to sharpen a plan or design.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

7 rules. 0 are common, 3 are distinctive, and 4 are very specific to this project.

  • 0

    Common

    Most of the 19 edited versions we read keep these.

  • 3

    Distinctive

    This author's own choices. Worth a look.

  • 4

    Very specific

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

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

    Check hook event names match core/hooks-guide.md

    line 29
  2. Very specific:

    Check settings keys match core/settings-reference.md

    line 30
  3. Very specific:

    Check skill frontmatter fields match core/skills-guide.md

    line 31
  4. Very specific:

    Check MCP config structure matches core/mcp-guide.md

    line 32
  5. Distinctive:

    Check that feature lists in setup audit checks align with what bootstrap actually generates

    line 35
  6. Distinctive:

    Check that any "best practice" advice in one skill doesn't contradict the other

    line 36
  7. Distinctive:

    If no issues found, report: "Skills are in sync with core guides."

    line 41

“Common” is measured: kept by at least 6 in 10 of the 19 edited versions of this file we could read. “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 Skills

Cross-reference the two main skills against core guides to find inconsistencies.

Steps

  1. Read source of truth:
    • skill/SKILL.md Section 4 (Config Reference) — canonical config formats
    • core/hooks-guide.md — hook events, matcher syntax, environment variables
    • core/settings-reference.md — settings structure, permission patterns
    • core/skills-guide.md — skill frontmatter format, allowed-tools syntax
    • core/mcp-guide.md — MCP server config format
  2. Read skills to check:
    • skill/SKILL.md — the /setup skill (full file)
    • .claude/skills/bootstrap/SKILL.md — the /bootstrap skill (full file)
  3. Cross-reference config formats:
    • Compare every JSON template in bootstrap against the canonical format in setup Section 4
    • Check hook event names match core/hooks-guide.md
    • Check settings keys match core/settings-reference.md
    • Check skill frontmatter fields match core/skills-guide.md
    • Check MCP config structure matches core/mcp-guide.md
  4. Cross-reference content claims:
    • Check that feature lists in setup audit checks align with what bootstrap actually generates
    • Check that any "best practice" advice in one skill doesn't contradict the other
  5. Report discrepancies:
    • For each issue, show: file, line number, what's inconsistent, and the correct value from the source of truth
    • Group by severity: MISMATCH (wrong value) vs STALE (outdated but not wrong) vs MISSING (should be present)
    • If no issues found, report: "Skills are in sync with core guides."

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.