/ Verzeichnis / Playground / skill-forge
← Alle Server ↗ GitHub
● Community AgriciDaniel ⚡ Sofort

skill-forge

von AgriciDaniel · AgriciDaniel/skill-forge

Plan → Build → Review → Evolve → Publish pipeline for creating production-grade Claude Code skills, with a 100-point health score.

Skill Forge is a meta-skill for authoring skills. It walks you through analyzing use cases, scaffolding a full skill file tree (SKILL.md, sub-skills, scripts, docs), auditing with a 0-100 score across 6 categories, refining based on findings, and packaging as a .skill archive. Supports four complexity tiers from single-file to enterprise.

▶ Demo ansehen 📦 Installieren 💡 Anwendungsfälle

Warum nutzen

Hauptfunktionen

Live-Demo

In der Praxis

skill-forge-skill.replay ▶ bereit
0/0

Installation

Repository des Autors · Offizielle Dokumentation zu Claude Skills

Anwendungsfälle

Praxisnahe Nutzung: skill-forge

Go from idea to published skill in one session

👤 Developers who keep copy-pasting the same prompt and want to ship it as a reusable skill ⏱ ~90 min intermediate

Wann einsetzen: You have a workflow you repeat (e.g. code review, PR description writing) and want it automated into a skill.

Ablauf
  1. Plan
    /skill-forge plan — I want a skill that does structured code review comments on PRs. Use cases, sub-skills, I/O.✓ Kopiert
    → Architecture with sub-skills enumerated
  2. Build
    /skill-forge build code-review-commenter — scaffold the tree per the plan.✓ Kopiert
    → SKILL.md + sub-files generated
  3. Review
    /skill-forge review code-review-commenter — give me the 100-point audit.✓ Kopiert
    → Score + findings per category
  4. Evolve + publish
    Fix each finding then /skill-forge publish — make a .skill archive.✓ Kopiert
    → Installable archive

Ergebnis: A shippable skill in your skills directory that passes the audit.

Fallstricke
  • Over-scoping — trying to make a monster skill — Start at tier 1 (single-file). Promote tiers only when real needs push you there
Kombinieren mit: filesystem · github

Audit and improve a skill someone else wrote

👤 Platform engineers curating an internal skills library ⏱ ~45 min beginner

Wann einsetzen: You inherited a skill and want to know if it meets the bar.

Ablauf
  1. Run the audit
    /skill-forge review path/to/skill — give me the scorecard and top 5 issues.✓ Kopiert
    → Score + prioritized fix list
  2. Evolve
    /skill-forge evolve — fix the top 5 findings and re-score.✓ Kopiert
    → Higher score, changelog

Ergebnis: An upgraded skill with measurable quality improvement.

Design a coordinated pack of skills for a domain

👤 Teams standardizing how AI agents work in their domain ⏱ ~180 min advanced

Wann einsetzen: You need 5–10 related skills that hand off cleanly to each other.

Ablauf
  1. Plan ecosystem
    /skill-forge plan domain=customer-support — design 6 coordinated skills with clear hand-off boundaries.✓ Kopiert
    → Diagram + per-skill spec
  2. Build in parallel
    /skill-forge build — all 6 skills, same sprint.✓ Kopiert
    → Skills generated with shared conventions

Ergebnis: A consistent pack rather than a collection of mismatched skills.

Fallstricke
  • Duplicating capabilities across skills — The plan step detects overlap — revisit if flagged

Kombinationen

Mit anderen MCPs für 10-fache Wirkung

skill-forge-skill + filesystem

Edit the generated skill files directly in the same session

After /skill-forge build, hand-edit the SKILL.md tone — the filesystem skill keeps Claude editing in-place.✓ Kopiert
skill-forge-skill + github

Publish skill to a public GitHub repo for distribution

Publish and push the .skill archive to a new GitHub release.✓ Kopiert

Werkzeuge

Was dieses MCP bereitstellt

WerkzeugEingabenWann aufrufenKosten
/skill-forge plan domain or use case Start of any new skill project 0
/skill-forge build skill name (+ plan) After plan is approved 0
/skill-forge review skill path After any significant change 0
/skill-forge evolve findings to fix Improvement loop 0
/skill-forge publish skill path Ready to ship 0

Kosten & Limits

Was der Betrieb kostet

API-Kontingent
None
Tokens pro Aufruf
Large — scaffolding and review are token-heavy (15–40k per phase)
Kosten in €
Free
Tipp
Plan in a cheap model, then switch to Opus for build and review

Sicherheit

Rechte, Secrets, Reichweite

Credential-Speicherung: None in the skill itself
Datenabfluss: None

Fehlerbehebung

Häufige Fehler und Lösungen

Review score stays low despite fixes

Read the findings carefully — some are structural (tier mismatch) and need redesign, not patching

Alternativen

skill-forge vs. andere

AlternativeWann stattdessenKompromiss
gsd-skill-creatorYou want skills to be auto-suggested from observed patternsMore framework, higher learning curve
Hand-authoring SKILL.mdSingle, simple skill you understand fullyNo review layer, easy to miss conventions

Mehr

Ressourcen

📖 Offizielle README auf GitHub lesen

🐙 Offene Issues ansehen

🔍 Alle 400+ MCP-Server und Skills durchsuchen