Agent skills (the SKILL.md files that Claude Code and Codex load) are easy to share, and GitHub is full of them. Each one was written for its author's project, with their stack, their scripts and their habits.
Copy one into your repo unchanged and your agent inherits all of that. A frontend skill tells it to reach for Tailwind when you use CSS modules. A workflow skill says "run the tests" when your project calls it pnpm test:unit. A cleanup skill says "delete unused files" while your AGENTS.md says never to touch docs/.
I built skilladopt to fix the skill before it goes in.
What it does
npx skilladopt anthropics/skills frontend-design
It fetches the skill at a pinned commit and hands the text, plus a short summary of your project, to an isolated Claude or Codex worker. The worker makes one decision per paragraph:
| Decision | Meaning |
|---|---|
keep |
stays as written |
bind |
a generic command becomes yours: "run the tests" → "run npm test" |
rewrite |
the intent applies, the details don't (you always approve these) |
drop |
doesn't apply here, with the reason |
review |
the AI wasn't sure, so you decide |
Each decision has to cite evidence from your repo: a dependency, an npm script, a line in AGENTS.md or CLAUDE.md. Then plain code checks the answer. A bind may insert exactly one command that really exists in your project and must leave the rest of the sentence identical. A "stack mismatch" drop must point at something your project actually lacks. Paragraphs that carry a duty (a prohibition, an approval step, a verification step) are never dropped or rewritten without you.
Nothing from the skill is executed, and the worker runs without tools (claude -p --safe-mode) or in a read-only sandbox (codex).
A week later
Your teammate renames the test script and adds a rule to AGENTS.md.
npx skilladopt impact
Because every decision recorded its evidence, skilladopt can tell which ones no longer hold. In the demo run that's 1 decision out of 25, plus the new rule that might conflict. You re-check those lines and leave the rest alone. skilladopt update <name> re-fits a skill to its latest upstream version and reuses every decision whose paragraph and evidence haven't changed.
Let your agent do it
npx skilladopt setup
This installs a small skill for Claude Code and Codex. After that you can ask, in any project, "add a frontend design skill to this project". The agent searches for one, adopts it with skilladopt, shows you what changed and asks before installing.
Where it stands
It's v0.1, MIT, with no runtime dependencies. It only handles Markdown skills and refuses skills that need scripts. I haven't measured how much time it saves, and that's the part I'd most like to hear about. If it makes a decision you disagree with, an issue with the skill and the decision would help a lot.
Top comments (0)