/ Annuaire / Playground / skill-forge
← Tous les serveurs ↗ GitHub
● Communauté AgriciDaniel ⚡ Instantané

skill-forge

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

▶ Voir la démo 📦 Installer 💡 Cas d'usage

Pourquoi l'utiliser

Fonctionnalités clés

Démo en direct

Aperçu en pratique

skill-forge-skill.replay ▶ prêt
0/0

Installer

Choisissez votre client

~/Library/Application Support/Claude/claude_desktop_config.json  · Windows: %APPDATA%\Claude\claude_desktop_config.json
{
  "mcpServers": {
    "skill-forge-skill": {
      "command": "git",
      "args": [
        "clone",
        "https://github.com/AgriciDaniel/skill-forge",
        "~/.claude/skills/skill-forge"
      ],
      "_inferred": true
    }
  }
}

Ouvrez Claude Desktop → Settings → Developer → Edit Config. Redémarrez après avoir enregistré.

~/.cursor/mcp.json · .cursor/mcp.json
{
  "mcpServers": {
    "skill-forge-skill": {
      "command": "git",
      "args": [
        "clone",
        "https://github.com/AgriciDaniel/skill-forge",
        "~/.claude/skills/skill-forge"
      ],
      "_inferred": true
    }
  }
}

Cursor utilise le même schéma mcpServers que Claude Desktop. La config projet l'emporte sur la globale.

VS Code → Cline → MCP Servers → Edit
{
  "mcpServers": {
    "skill-forge-skill": {
      "command": "git",
      "args": [
        "clone",
        "https://github.com/AgriciDaniel/skill-forge",
        "~/.claude/skills/skill-forge"
      ],
      "_inferred": true
    }
  }
}

Cliquez sur l'icône MCP Servers dans la barre latérale Cline, puis "Edit Configuration".

~/.codeium/windsurf/mcp_config.json
{
  "mcpServers": {
    "skill-forge-skill": {
      "command": "git",
      "args": [
        "clone",
        "https://github.com/AgriciDaniel/skill-forge",
        "~/.claude/skills/skill-forge"
      ],
      "_inferred": true
    }
  }
}

Même format que Claude Desktop. Redémarrez Windsurf pour appliquer.

~/.continue/config.json
{
  "mcpServers": [
    {
      "name": "skill-forge-skill",
      "command": "git",
      "args": [
        "clone",
        "https://github.com/AgriciDaniel/skill-forge",
        "~/.claude/skills/skill-forge"
      ]
    }
  ]
}

Continue utilise un tableau d'objets serveur plutôt qu'une map.

~/.config/zed/settings.json
{
  "context_servers": {
    "skill-forge-skill": {
      "command": {
        "path": "git",
        "args": [
          "clone",
          "https://github.com/AgriciDaniel/skill-forge",
          "~/.claude/skills/skill-forge"
        ]
      }
    }
  }
}

Ajoutez dans context_servers. Zed recharge à chaud à la sauvegarde.

claude mcp add skill-forge-skill -- git clone https://github.com/AgriciDaniel/skill-forge ~/.claude/skills/skill-forge

Une seule ligne. Vérifiez avec claude mcp list. Supprimez avec claude mcp remove.

Cas d'usage

Usages concrets : 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

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

Prérequis
  • Skill cloned — git clone https://github.com/AgriciDaniel/skill-forge ~/.claude/skills/skill-forge
Déroulement
  1. Plan
    /skill-forge plan — I want a skill that does structured code review comments on PRs. Use cases, sub-skills, I/O.✓ Copié
    → Architecture with sub-skills enumerated
  2. Build
    /skill-forge build code-review-commenter — scaffold the tree per the plan.✓ Copié
    → SKILL.md + sub-files generated
  3. Review
    /skill-forge review code-review-commenter — give me the 100-point audit.✓ Copié
    → Score + findings per category
  4. Evolve + publish
    Fix each finding then /skill-forge publish — make a .skill archive.✓ Copié
    → Installable archive

Résultat : A shippable skill in your skills directory that passes the audit.

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

Audit and improve a skill someone else wrote

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

Quand l'utiliser : You inherited a skill and want to know if it meets the bar.

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

Résultat : 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

Quand l'utiliser : You need 5–10 related skills that hand off cleanly to each other.

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

Résultat : A consistent pack rather than a collection of mismatched skills.

Pièges
  • Duplicating capabilities across skills — The plan step detects overlap — revisit if flagged

Combinaisons

Associez-le à d'autres MCPs pour un effet X10

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

Publish skill to a public GitHub repo for distribution

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

Outils

Ce que ce MCP expose

OutilEntréesQuand appelerCoût
/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

Coût et limites

Coût d'exécution

Quota d'API
None
Tokens par appel
Large — scaffolding and review are token-heavy (15–40k per phase)
Monétaire
Free
Astuce
Plan in a cheap model, then switch to Opus for build and review

Sécurité

Permissions, secrets, portée

Stockage des identifiants : None in the skill itself
Sortie de données : None

Dépannage

Erreurs courantes et correctifs

Review score stays low despite fixes

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

Build step creates skill but Claude doesn't pick it up

Ensure SKILL.md frontmatter is valid and the skill sits directly under ~/.claude/skills/<name>/

Vérifier : ls ~/.claude/skills/<name>/SKILL.md

Alternatives

skill-forge vs autres

AlternativeQuand l'utiliserCompromis
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

Plus

Ressources

📖 Lire le README officiel sur GitHub

🐙 Voir les issues ouvertes

🔍 Parcourir les 400+ serveurs MCP et Skills