ca-new-skill
Author a new codeArbiter skill: prove the gap is real, get the spec approved, then write it.
npx skills add arbiterForge/codeArbiter --skill ca-new-skill --agent codex
Same command for any agent — swap --agent for claude-code, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# $ca-new-skill — author a skill The only permitted entry to creating a skill. Nothing is written until the gap is proven uncovered — skills are not created speculatively. Name the skill in verb-noun form (`"dependency-review"`), not as a description (`"the thing that checks packages"`). ## Flow Routes to the `skill-author` skill, which owns the work end to end through its five gated phases — gap evidence, scope, authoring, self-review against the v2 house style, and routing integration (the `INDEX.md` + routing-table entry that makes the new skill reachable). The phase definitions live in the skill; this command does not restate them. Nothing is authored until an existing skill or agent is proven not to cover the need; nothing ships until the new skill carries gated phases, hard rules, and its routing entry. ## Routes to `skill-author` (`${CLAUDE_PLUGIN_ROOT}/routines/skill-author/SKILL.md`) — all five phases. ## When NOT to use - A one-time action → `$ca-feature` or a command definition. - An existing skill nearly covers it → extend that skill via `$ca-feature`. - "Do we even need a skill here?" → `$ca-btw`. ## Hard gate MUST prove the gap is real in Phase 1 before writing any sk
- Flow
- Routes to
- When NOT to use
- Hard gate
What does the ca-new-skill skill do?
Author a new codeArbiter skill: prove the gap is real, get the spec approved, then write it.
How do I install it?
Run `npx skills add arbiterForge/codeArbiter --skill ca-new-skill --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From arbiterForge/codeArbiter, a repository with 138 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.