/ Directory / Playground / skill-forge
← All servers ↗ GitHub
● Community AgriciDaniel ⚡ Instant

skill-forge

by 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.

▶ Watch demo 📦 Install 💡 Use Cases

Why use it

Key features

Live Demo

What it looks like in practice

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

Install

Author repository · Claude Skills documentation

Use Cases

Real-world ways to use 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

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

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

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

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

Audit and improve a skill someone else wrote

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

When to use: You inherited a skill and want to know if it meets the bar.

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

Outcome: 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

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

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

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

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

Combinations

Pair with other MCPs for X10 leverage

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.✓ Copied
skill-forge-skill + github

Publish skill to a public GitHub repo for distribution

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

Tools

What this MCP exposes

ToolInputsWhen to callCost
/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

Cost & Limits

What this costs to run

API quota
None
Tokens per call
Large — scaffolding and review are token-heavy (15–40k per phase)
Monetary
Free
Tip
Plan in a cheap model, then switch to Opus for build and review

Security

Permissions, secrets, blast radius

Credential storage: None in the skill itself
Data egress: None

Troubleshooting

Common errors and fixes

Review score stays low despite fixes

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

Alternatives

skill-forge vs others

AlternativeWhen to use it insteadTradeoff
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

More

Resources

📖 Read the official README on GitHub

🐙 Browse open issues

🔍 Browse all 400+ MCP servers and Skills

Continue exploring

Related tools and workflows

Choose another guide for your workflow, or explore a collection.

Browse all topic collections → · See 29 new official additions →