Skill486 repo starsupdated yesterday

toolbox

The toolbox skill organizes named bundles of Claude skills and agents configured to run before development work begins or after work concludes, enabling automated code review, security audits, documentation checks, and refactoring validation. Use it at feature completion, repository initialization, pre-commit hooks, or when sharing standardized development workflows across teams through the CLI commands for listing, activating, exporting, and importing toolbox configurations.

View source Repository: ctx

Install in Claude Code

Copy

git clone --depth 1 https://github.com/stevesolun/ctx /tmp/toolbox && cp -r /tmp/toolbox/skills/toolbox ~/.claude/skills/toolbox

Then start a new Claude Code session; the skill loads automatically.

Definition

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 starts
- `post` — agents that form the council after work ends
- `scope.analysis` — `diff` | `full` | `graph-blast` | `dynamic`
- `trigger` — `slash`, `pre_commit`, `session_end`, or `file_save` glob
- `budget.max_tokens` / `budget.max_seconds` — hard stop on runaway cost
- `dedup.policy` — `fresh` (always re-run) or `cached` (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-init` suggestion).
- User touches security-sensitive paths (triggers `security-sweep` file_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.