sync-skills
Skill28 starsChanged 58 days agoApache-2.0View on GitHub
Fetch the team's shared skills — reset each disposable team clone to origin/main — and show the outcome per team as a Markdown board from the terum-skills CLI. Use when the user wants the newest catalogue, receipts or roster before listing, searching or installing.
23 other projects use a version of this.
Adopted by
Most recently taken up by
- coder013/claude-skillstheir own version, first seen Nov 16, 2026
- morodomi/dev-crewtheir own version, first seen Nov 12, 2026
- devjiwonchoi/skillstheir own version, first seen Nov 8, 2026
- snuffish/dotfilestheir own version, first seen Nov 1, 2026
- dsonders/claude-skillstheir own version, first seen Oct 20, 2026
- SummerSec/SumSec-Skillstheir own version, first seen Oct 15, 2026
Used with
Projects with it also use explain, create-skill and 4 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.
sunnyclinches44Skillexplain
Explains code using real-world analogies and ASCII diagrams
Also in 3 projects that use this
ElasticSkillcreate-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
NVIDIASkillresearch
Before designing a feature, research how comparable libraries solve the problem, check best practices, known pitfalls, and upstream changes. Use when starting a new feature, investigating an unfamiliar area, or the user asks to research something.
Also in 3 projects that use this
MicrosoftSkillhandoff
Compact the current conversation into a handoff document for another agent to pick up.
Also in 4 projects that use this
SentrySkillcommit
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
GoogleSkillgrill-me
A relentless interview to sharpen a plan or design.
Also in 3 projects that use this
Other versions23 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 23
- Tasihi89/sync-skills★ 29same name
- qa-aman/claude-skills★ 24same name
- SummerSec/SumSec-Skills★ 8same name
- fotis89/ctx-launcher★ 4same name
- madnpc/skills★ 3same name
- devjiwonchoi/skills★ 2same name
- paulo-yamagishi/claude-code-setup★ 2same name
- t0ddharris/claude-code-skills★ 2same name
- GalvinGao/skills★ 1same name
- GuanqiHe/claude-skills★ 1same name
13 more not listed
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 repository9 other files it gives its agents.
- AGENTS.mdAGENTS.md
- desktop/AGENTS.mdAGENTS.md
- eval-reportSkill
- evalSkill
- list-skillsSkill
- search-skillsSkill
- skill-infoSkill
- skill-statusSkill
- terum-skillsSkill
The file
We split this skill into the rules it gives an agent
4 rules. 0 are common, 0 are distinctive, and 4 are very specific to this project.
0
Common
Most of the 19 edited versions we read keep these.
0
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
- Very specific: line 17
Run it in the background when your shell tool can: a slow fetch takes a while.
- Very specific: line 29
No TTY: never pipe y, never drive the CLI with expect, never add --frames to dodge a question.
- Very specific: line 30
Never use the skill-file
!commandinjection. - Very specific: line 31
Do not cd; run from the current working directory and pass absolute paths.
“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.
Files
Refresh the local team clone.
Arguments: everything after the command (in Claude Code this arrives as "$ARGUMENTS"): --team <name> when the user names a team, passed through; nothing else is expected.
Command
npx -y terum-skills@latest sync --format mdRun it in the background when your shell tool can: a slow fetch takes a while. Never run sync --hook by hand; that is the session-start entry.
Before
Say what it does in one sentence before running: it fetches and resets each disposable team clone to origin/main; it never uploads, places or edits the user's skill folders.
After
Show the board verbatim. Disclose each team the board reports as not refreshed, with its reason. A team whose repository was recreated elsewhere is offered team move on the board: that verb asks a question, so hand it to a terminal.
Rules
- No TTY: never pipe
y, never drive the CLI withexpect, never add--framesto dodge a question. A question the CLI asks means the verb belongs in a terminal: say so and hand over the command. - Never use the skill-file
!`command`injection; run every command with your shell tool and read its output. - Do not
cd; run from the current working directory and pass absolute paths. - Exit 1 is a result, not a retry: show the failure block, do not re-run, and do not claim earlier steps were rolled back.
Sandbox
When CODEX_SANDBOX_NETWORK_DISABLED=1 is set and the command starts with npx, add --prefer-offline after npx so a cached package resolves without the registry; if npx still reports a network error, ask the user to run the command in a terminal. In that sandbox the verbs that need the network — sync, install, publish, invite, eval, and update's release probe — are handed to a terminal with the reason.
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
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.

