← use cases · per-repo
Per-project skill overrides
Pin repo-specific skills that win over your personal and system skills inside that project.
Who it's for
Developers who work across repos where the same command name means different things or needs different flags.
The problem
A globally-installed skill for a common tool can be wrong for a specific repo's wrapper or version. You want per-project truth without clobbering your global setup.
How skillterm does it
- 1
Drop a SKILL.md into the project's ./.skillterm/skills/ directory.
- 2
skillterm searches project → user → system in order, so the project copy wins inside that repo.
- 3
Outside the repo, your user-level skills apply as normal.
- 4
Nothing global is mutated; the override is scoped to the directory tree.
The outcome
Completions that are correct for the repo you are actually in, layered cleanly over your personal defaults.