ca-btw
Lightweight Q&A about the project — answer from context and return, no routing, no state change.
npx skills add arbiterForge/codeArbiter --skill ca-btw --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-btw — quick Q&A The one exception to the slash-command pipeline. Answer the question and return. No skill is routed to, no agent dispatched, no file written. Always safe to invoke. ## Flow 1. Read `<project-root>/.codearbiter/` docs as needed to answer accurately — `CONTEXT.md`, `tech-stack.md`, `coding-standards.md`, `security-controls.md`, `decisions/`, `specs/`, `plans/`. 2. Answer directly and conversationally — not a formatted report. 3. If the answer is not in context, say so plainly. Never guess. ## Hard gate Read-only. MUST NOT write or modify any file, route to a skill, dispatch an agent, run tests, or resolve a `[CONFIRM-NN]`. If the question is really a request to build or fix something, say so and point to `$ca-feature` or `$ca-fix` — do not start implementation from `$ca-btw`.
- Flow
- Hard gate
What does the ca-btw skill do?
Lightweight Q&A about the project — answer from context and return, no routing, no state change.
How do I install it?
Run `npx skills add arbiterForge/codeArbiter --skill ca-btw --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.