/ Verzeichnis / Playground / woodshed
● Community gaearon ⚡ Sofort

woodshed

von gaearon · gaearon/woodshed

Create, run, rate, and iterate your Claude Skills — Dan Abramov's skill-workshop skill, a meta-loop for getting skills actually good.

A meta-skill for authoring other skills. Scaffolds a new skill, runs it on test cases, asks you to rate the output, and uses the feedback to iterate on the skill's prompts. Based on Dan Abramov's 'woodshedding' methodology — deliberate practice applied to skill authoring.

Warum nutzen

Hauptfunktionen

Live-Demo

In der Praxis

woodshed-skill.replay ▶ bereit
0/0

Installation

Repository des Autors · Offizielle Dokumentation zu Claude Skills

Anwendungsfälle

Praxisnahe Nutzung: woodshed

Author a new skill and iterate it to 'actually works'

👤 Skill authors who've noticed their first drafts don't survive real use ⏱ ~120 min advanced

Wann einsetzen: You have an idea for a skill but every time you write one, it degrades after 3 uses.

Ablauf
  1. Scaffold
    Use woodshed. Create a new skill called 'changelog-writer' that turns git logs into user-facing changelogs.✓ Kopiert
    → skills/changelog-writer/ created with SKILL.md
  2. Create test cases
    Generate 5 diverse test inputs.✓ Kopiert
    → tests/ folder with 5 sample git log fixtures
  3. Run and rate
    Run the skill on each. Show me the output; I'll rate.✓ Kopiert
    → Outputs presented with rating slots
  4. Iterate based on ratings
    Based on my ratings, suggest prompt changes to SKILL.md. Don't apply yet.✓ Kopiert
    → Proposed diff with rationale per change

Ergebnis: A skill that works on your real use cases, not just the demo.

Fallstricke
  • Overfitting to test cases — Hold out some tests; re-run after every iteration to catch regressions
Kombinieren mit: filesystem

Improve a skill that's been disappointing you

👤 Anyone with a skill installed they're unhappy with ⏱ ~60 min intermediate

Wann einsetzen: You have a skill that half-works and you can't tell why.

Ablauf
  1. Characterize the failures
    Use woodshed. Here's a skill I installed. Here are 3 sessions where it underperformed. Diagnose.✓ Kopiert
    → Pattern in failures — instruction gap, example gap, framing issue
  2. Propose fixes
    Propose minimal SKILL.md edits to address those patterns.✓ Kopiert
    → Specific diffs

Ergebnis: A skill you can trust.

Kombinationen

Mit anderen MCPs für 10-fache Wirkung

woodshed-skill + skill-fetch-skill

Find skills with skill-fetch, improve them with woodshed

Find a changelog-writer skill; install; run woodshed on it to tune for my repo.✓ Kopiert
woodshed-skill + filesystem

Persist iteration history across sessions

Keep woodshed logs in skills/<name>/.woodshed/ for traceability.✓ Kopiert

Werkzeuge

Was dieses MCP bereitstellt

WerkzeugEingabenWann aufrufenKosten
scaffold_skill skill name, goal New skill 0
run_tests skill + test set Evaluating 0
capture_rating rating + notes After each test 0
iterate_prompt skill + ratings After a rating round 0

Kosten & Limits

Was der Betrieb kostet

API-Kontingent
None
Tokens pro Aufruf
High during iteration (many test runs)
Kosten in €
Free (Claude API usage applies)
Tipp
Keep test sets small — 5 tests beats 50 that never get reviewed.

Sicherheit

Rechte, Secrets, Reichweite

Credential-Speicherung: None
Datenabfluss: None from skill

Fehlerbehebung

Häufige Fehler und Lösungen

Iteration keeps changing but doesn't improve

Your test set is too narrow; add diverse cases

Skill works in woodshed but not in real use

Production prompts differ from test fixtures; add real-session logs to the test set

Alternativen

woodshed vs. andere

AlternativeWann stattdessenKompromiss
Hand-tuning SKILL.md without loopSimple skills with obvious promptsSlower convergence; easier to miss regressions
claude-skills-vault-skillYou want ready-made skills, not authoring toolsDifferent goal

Mehr

Ressourcen

📖 Offizielle README auf GitHub lesen

🐙 Offene Issues ansehen

🔍 Alle 400+ MCP-Server und Skills durchsuchen