agentleFS
Sign inStart free
AlomoesDataScienceAlomoesDataScience/claude-skills/.claude/skills/skill-sync/SKILL.md

skill-sync

Skill1 starsChanged 10 days agoNo licenceView on GitHub

Keep skills up to date with the skills they learn from, and move single files in and out of skills (sync.py). A skill's sources are the generic skills it builds on or names and its counterparts in other games (dom6-map <-> fog2m-map); mark records "up to date with these sources", status shows what changed in them since (new, changed, removed SKILL.md sections and scripts), diff shows the changes, gaps lists skills one game has and another lacks, load copies a script or side file into a skill with its origin recorded, unload retires a file to retired/ with the reason, provenance flags loaded files whose original changed. Use when a generic skill or another game's skill gained lessons or tools that should reach this game, at the start of a session with a game whose skills may be stale, after a game session that changed skills (carry it to the other games), when porting a tool from one game to another, when a file in a skill is obsolete, or when the user says skills are out of date.

21 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use session-handoff, verification-before-completion and 2 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.
  • wpankSkill

    session-handoff

    WHAT: Create comprehensive handoff documents that enable fresh AI agents to seamlessly continue work with zero ambiguity. Solves long-running agent context exhaustion problem.

    Also in 3 projects that use this

  • OpenAISkill

    verification-before-completion

    Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always

    Also in 3 projects that use this

  • OpenAISkill

    test-driven-development

    Use when implementing any feature or bugfix, before writing implementation code

    Also in 3 projects that use this

  • GoogleSkill

    tdd

    Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.

    Also in 4 projects that use this

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 18 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 3

    Very specific

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

No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.

“Common” is measured: kept by at least 6 in 10 of the 18 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.

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.

Check your setup, free