toolbox
Pre/post dev toolbox — named bundles of skills/agents loaded before development work and councils of experts invoked after. Run /toolbox or the toolbox.py CLI to list, activate, initialize, export, import, and validate toolboxes. Invoke at the start or end of a dev session, when setting up a new repo, or when sharing toolboxes with a team.
- License 许可
- MIT
- 所属仓库
- stevesolun/ctx
- 最近更新
- 2026-10-15
- Stars
- ★ 593
- Forks
- 69
01 前言 Front Matter
- name
- toolbox
- type
- feature
- priority
- 50
- always_load
- false
- description
- Pre/post dev toolbox — named bundles of skills/agents loaded before development work and councils of experts invoked after. Run /toolbox or the toolbox.py CLI to list, activate, initialize, export, import, and validate toolboxes. Invoke at the start or end of a dev session, when setting up a new repo, or when sharing toolboxes with a team.
03 SKILL.md 正文
toolbox
Named bundles of skills/agents that run before (pre) or after (post)
a development task. Learn patterns from past work and propose new bundles.
Invoke slash, pre-commit, session-end, or file-save.
Quick reference
| Task | Command |
|---|---|
| Seed 5 starter toolboxes | python src/toolbox.py init |
| List available toolboxes | python src/toolbox.py list |
| Inspect one | python src/toolbox.py show ship-it |
| Activate (global) | python src/toolbox.py activate ship-it |
| Export for sharing | python src/toolbox.py export ship-it |
| Import a shared toolbox | python src/toolbox.py import file.yaml |
| Validate config | python src/toolbox.py validate |
Starter templates
| Name | When to use |
|---|---|
| ship-it | End-of-feature: 7-expert council on the change set |
| security-sweep | Security audit with guardrail blocking HIGH findings |
| refactor-safety | Refactors with graph-informed blast radius |
| docs-review | When touching Markdown or API docs |
| fresh-repo-init | Blank repo: run intent interview and scaffold |
Data model
Global: ~/.claude/toolboxes.json.
Per-repo (overrides global): <repo_root>/.toolbox.yaml.
Each toolbox declares:
pre— skills/agents to load before work startspost— agents that form the council after work endsscope.analysis—diff|full|graph-blast|dynamictrigger—slash,pre_commit,session_end, orfile_saveglobbudget.max_tokens/budget.max_seconds— hard stop on runaway costdedup.policy—fresh(always re-run) orcached(reuse within window)guardrail— if true, block commit on HIGH findings
Invoke when
- User says "I'm done with this feature" or commits a feature branch.
- User opens a fresh repo (triggers
fresh-repo-initsuggestion). - User touches security-sensitive paths (triggers
security-sweepfile_save). - User asks "what toolboxes do I have?" or "run the council".
Reasoning
See docs/toolbox/index.md, docs/toolbox/starters.md, and
docs/toolbox/verdicts.md for the current toolbox contract, starter bundles,
and guardrail behavior.
04 同仓库更多 Skills
skill-router
Alive skill router — reads the current project's stack and loads/unloads skills dynamically. Invoke at session start or when project context changes.
repo-stats-autoupdate
Keeps README badge + inline counts in sync with the real number of skills, agents, graph nodes/edges, communities, converted pipelines, and test inventory. Runs automatically on every commit via a git pre-commit hook. Use when the README drifts from reality or before publishing a release.
find-skills
Discover installable agent skills from ctx's shipped Skills.sh catalog, the Skills.sh search API, and the npx skills CLI. Use when a user asks whether a skill exists, wants to add/update a skill, or needs a repeatable procedure for finding candidate skills safely.
no-mistakes
Validate committed feature-branch changes through the no-mistakes pipeline: intent, rebase, review, test, docs, lint, push, PR, and CI. Use when the user asks to run no-mistakes, ship safely, validate before pushing, or gate a change before it reaches upstream.
zoom-out
Tell the agent to zoom out and give broader context or a higher-level perspective. Use when you're unfamiliar with a section of code or need to understand how it fits into the bigger picture.
writing-shape
Take a markdown file of raw material and shape it into an article through a conversational session — drafting candidate openings, growing the piece paragraph by paragraph, arguing about format (lists, tables, callouts, quotes) at each step. Use when the user has a pile of notes, fragments, or a rough draft and wants help turning it into something publishable.