majiayu000/spellbook / skills/skill-creator
skill-creator
VerifiedCreate new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, update or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.
| File | Kind | Size |
|---|---|---|
| LICENSE.txt | markdown | 11.1 KB |
| SKILL.md | skill md | 33.1 KB |
| agents/analyzer.md | markdown | 10.1 KB |
| agents/comparator.md | markdown | 7.1 KB |
| agents/grader.md | markdown | 8.8 KB |
| assets/eval_review.html | other | 6.9 KB |
| eval-viewer/generate_review.py | script | 16.0 KB |
| eval-viewer/viewer.html | other | 44.0 KB |
| references/quality-playbook.md | markdown | 2.9 KB |
| references/schemas.md | markdown | 13.0 KB |
| requirements.txt | manifest | 17 B |
| scripts/aggregate_benchmark.pyexecutable | script | 15.0 KB |
| scripts/generate_report.pyexecutable | script | 12.5 KB |
| scripts/improve_description.pyexecutable | script | 10.5 KB |
| scripts/package_skill.pyexecutable | script | 5.9 KB |
| scripts/path_safety.py | script | 3.2 KB |
| scripts/quick_validate.pyexecutable | script | 5.8 KB |
| scripts/run_eval.pyexecutable | script | 11.9 KB |
| scripts/run_loop.pyexecutable | script | 13.4 KB |
| scripts/utils.py | script | 1.6 KB |
references/quality-playbook.md
View on GitHub# Skill Quality Playbook
Use this reference when creating or materially improving a skill. Keep the main
`SKILL.md` short; put large reference tables, scripts, templates, and examples
behind progressive disclosure.
## Pick One Primary Type
Choose the skill's main job before writing:
- Library/API reference: how to use a library, CLI, SDK, or internal platform.
- Product verification: scripts or tool flows that prove product behavior.
- Data fetching/analysis: canonical queries, dashboards, metric names, helpers.
- Business process automation: repeatable team workflow with required state.
- Code scaffolding/templates: boilerplate plus natural-language requirements.
- Code quality/review: deterministic style, review, testing, or policy checks.
- CI/CD/deployment: build, smoke test, deploy, monitor, rollback, PR babysitting.
- Runbook: symptom-driven investigation that returns a structured report.
- Infrastructure operations: guarded maintenance, especially risky actions.
If a draft has two or three primary types, split it or make `SKILL.md` a router
that points to narrower references.
## High-Signal Sections
- **Description**: Write for triggering, not summary. Include when to use the
skill, user phrasing, symptoms, and near-boundary cases.
- **Gotchas**: Add observed failure modes, naming mismatches, false-success
signals, risky defaults, and recovery checks.
- **Verification**: For objective workflows, include scripts, assertions, smoke
tests, browser checks, health checks, or explicit done-when proof.
- **Reliable Skill Contract**: For high-value workflow skills, include negative
examples, phase checkpoints, machine-checkable done conditions, replay or
smoke hooks, and drift signals.
- **Support files**: Use `references/`, `scripts/`, `assets/`, `templates/`, and
`evals/` when detail would otherwise bloat `SKILL.md`.
- **Setup**: If the skill needs user or environment context, describe a config
file or setup flow instead of asking repeatedly.
- **Memory**: Repeated workflows can keep append-only logs, JSON, or SQLite state
when previous runs change the next run.
- **Hooks**: Use on-demand hooks only for temporary guardrails that would be too
annoying to run globally.
## Authoring Checks
Before calling a skill good, ask:
1. Would the model know to trigger this from the `description` alone?
2. Does the skill teach something non-obvious or repo/org-specific?
3. Are the common failure modes captured as gotchas?
4. Does `SKILL.md` point clearly to every support directory it expects to use?
5. Is there a concrete verification path for objective work?
6. Are risky or destructive actions guarded by confirmation or checks?
7. Does a high-value workflow skill include the five Reliable Skill Contract
elements or record why a specific element is deferred?
Run the repository-level audit when available:
```bash
python3 scripts/audit_skill_quality.py <skill-name>
```
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| finishing-a-development-branchobra/superpowersUse when implementation is complete, all tests pass, and you need to decide how to integrate the work | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| systematic-debuggingobra/superpowersUse when encountering any bug, test failure, or unexpected behavior, before proposing fixes | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| test-driven-developmentobra/superpowersUse when implementing any feature or bugfix, before writing implementation code | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| skill-creatoranthropics/skillsCreate new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |