/ 目錄 / 演練場 / 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 搭配，撬動十倍槓桿

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
每次呼叫 Token 數
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