/ ディレクトリ / プレイグラウンド / SkillForge
← 全サーバー ↗ GitHub
● コミュニティ tripleyak ⚡ 即起動

SkillForge

作者 tripleyak · tripleyak/SkillForge

Phase-based skill router + creator — triages each request, analyzes via 11 thinking lenses, generates XML specs, and runs multi-agent approval before shipping.

SkillForge is a meta-skill for Claude Code and Codex that decides whether to USE an existing skill, IMPROVE one, CREATE new, or COMPOSE from multiple. It runs 4 phases: triage → deep 11-lens analysis → XML spec → generation with multi-agent synthesis. v5.0 streamlined the SKILL.md to 313 lines with lazy-loaded references so the context stays lean.

▶ デモを見る 📦 インストール 💡 ユースケース

なぜ使うのか

主な機能

ライブデモ

実際の動作

skillforge-skill.replay ▶ 準備完了
0/0

インストール

作者のリポジトリ · Claude Skills の公式ドキュメント

ユースケース

実用的な使い方： SkillForge

Find the right existing skill instead of reinventing one

👤 Anyone with a big skill library and no memory of what's installed ⏱ ~5 min beginner

使うタイミング： You have a task and aren't sure if something already covers it.

フロー
  1. Describe the task
    Use skillforge. I need to turn our docs site into a searchable knowledge base.✓ コピーしました
    → Triage returns USE_EXISTING with a recommendation (e.g. skill-seekers)
  2. Confirm and hand off
    Good — run that skill.✓ コピーしました
    → Routes to the recommended skill

結果： You use what's already there rather than writing a new skill.

注意点
  • Triage is over-eager to create new — Explicitly ask 'prefer USE_EXISTING unless match score < 70%'
組み合わせ： skill-seekers-skill

Create a new skill with engineered rigor

👤 Skill authors who want quality, not vibes ⏱ ~30 min intermediate

使うタイミング： Triage returned CREATE_NEW and you want the full 4-phase generation.

フロー
  1. Approve triage
    skillforge — CREATE_NEW for a skill that drafts ADRs from design discussions.✓ コピーしました
    → Phase 1 analysis begins with 11 lenses
  2. Review the spec
    Show me the XML spec before generation.✓ コピーしました
    → Structured spec you can critique
  3. Run synthesis
    Generate, then run the multi-agent panel.✓ コピーしました
    → Panel verdict with unanimous approval or concrete objections

結果： A production-quality SKILL.md ready to install.

注意点
  • Panel stuck in endless loop — Cap iterations — SkillForge supports an iteration limit flag
組み合わせ： skill-seekers-skill

組み合わせ

他のMCPと組み合わせて10倍の力を

skillforge-skill + skill-seekers-skill

Use SkillForge to decide, then Skill Seekers to actually ingest sources for CREATE_NEW

skillforge triage, then if CREATE_NEW, use skill-seekers to pull in the docs.✓ コピーしました
skillforge-skill + filesystem

Skill output goes straight into ~/.claude/skills/

Write the generated SKILL.md and references to ~/.claude/skills/<name>/.✓ コピーしました

ツール

このMCPが提供する機能

ツール入力呼び出すタイミングコスト
Phase 0 triage task description + skill library Start of every request 0
Phase 1 deep analysis (11 lenses) task After triage, before generation 0
Phase 2-3 XML spec + generation analysis CREATE_NEW or IMPROVE_EXISTING 0
Phase 4 multi-agent synthesis draft Final quality gate 0

コストと制限

運用コスト

APIクォータ
None
呼び出しあたりのトークン
Full 4-phase generation is token-heavy (10-30k)
金額
Free — skill is local
ヒント
Use triage-only for simple routing; invoke full pipeline only for real skill authoring.

セキュリティ

権限、シークレット、影響範囲

認証情報の保管： No credentials — skill is prompts
データ送信先： None from the skill itself

トラブルシューティング

よくあるエラーと対処法

Triage picks wrong verdict

Provide the current skill library list so triage can match properly.

Multi-agent panel keeps rejecting

Check the objections — often a missing section in the spec. Fix once, re-run.

Generated skill feels generic

Give more source material in Phase 1; skill quality follows source quality.

代替案

SkillForge 他との比較

代替案代わりに使う場面トレードオフ
skill-seekers-skillYou want document-ingest-first rather than analysis-firstSeekers is heavier on source processing; SkillForge is heavier on engineering rigor
Manual SKILL.md authoringThe skill is small and you have a clear specFastest for trivial skills

その他

リソース

📖 GitHub の公式 README を読む

🐙 オープンな issue を見る

🔍 400以上のMCPサーバーとSkillsを見る