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

skill-forge

作者 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.

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

なぜ使うのか

主な機能

ライブデモ

実際の動作

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

インストール

クライアントを選択

~/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
    }
  }
}

Claude Desktop → Settings → Developer → Edit Config を開く。保存後、アプリを再起動。

~/.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 は Claude Desktop と同じ mcpServers スキーマを使用。プロジェクト設定はグローバルより優先。

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
    }
  }
}

Cline サイドバーの MCP Servers アイコンをクリックし、"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
    }
  }
}

Claude Desktop と同じ形式。Windsurf を再起動して反映。

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

Continue はマップではなくサーバーオブジェクトの配列を使用。

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

context_servers に追加。保存時に Zed がホットリロード。

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

ワンライナー。claude mcp list で確認、claude mcp remove で削除。

ユースケース

実用的な使い方： 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

使うタイミング： You have a workflow you repeat (e.g. code review, PR description writing) and want it automated into a skill.

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

結果： A shippable skill in your skills directory that passes the audit.

注意点
  • Over-scoping — trying to make a monster skill — Start at tier 1 (single-file). Promote tiers only when real needs push you there
組み合わせ： filesystem · github

Audit and improve a skill someone else wrote

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

使うタイミング： You inherited a skill and want to know if it meets the bar.

フロー
  1. Run the audit
    /skill-forge review path/to/skill — give me the scorecard and top 5 issues.✓ コピーしました
    → Score + prioritized fix list
  2. Evolve
    /skill-forge evolve — fix the top 5 findings and re-score.✓ コピーしました
    → Higher score, changelog

結果： 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

使うタイミング： You need 5–10 related skills that hand off cleanly to each other.

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

結果： A consistent pack rather than a collection of mismatched skills.

注意点
  • Duplicating capabilities across skills — The plan step detects overlap — revisit if flagged

組み合わせ

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

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.✓ コピーしました
skill-forge-skill + github

Publish skill to a public GitHub repo for distribution

Publish and push the .skill archive to a new GitHub release.✓ コピーしました

ツール

このMCPが提供する機能

ツール入力呼び出すタイミングコスト
/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

コストと制限

運用コスト

APIクォータ
None
呼び出しあたりのトークン
Large — scaffolding and review are token-heavy (15–40k per phase)
金額
Free
ヒント
Plan in a cheap model, then switch to Opus for build and review

セキュリティ

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

認証情報の保管： None in the skill itself
データ送信先： None

トラブルシューティング

よくあるエラーと対処法

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>/

確認： ls ~/.claude/skills/<name>/SKILL.md

代替案

skill-forge 他との比較

代替案代わりに使う場面トレードオフ
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

その他

リソース

📖 GitHub の公式 README を読む

🐙 オープンな issue を見る

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