skill-forge MCP — Сценарии использования, Установка & Живое демо

Зачем использовать

Ключевые функции

5-stage workflow: plan, build, review, evolve, publish
0-100 health score across 6 quality categories
Four tiers: single-file, multi-file, agent-assisted, enterprise
3-layer architecture: Directive + Orchestration + Execution
Packages to .skill archives with install scripts

Живое демо

Как выглядит на практике

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 использует ту же схему mcpServers, что и Claude Desktop. Конфиг проекта приоритетнее глобального.

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

Щёлкните значок MCP Servers на боковой панели Cline, затем "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 использует массив объектов серверов, а не 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"
        ]
      }
    }
  }
}

Добавьте в 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

Поток

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
Build

/skill-forge build code-review-commenter — scaffold the tree per the plan.✓ Скопировано

→ SKILL.md + sub-files generated
Review

/skill-forge review code-review-commenter — give me the 100-point audit.✓ Скопировано

→ Score + findings per category
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.

Поток

Run the audit

/skill-forge review path/to/skill — give me the scorecard and top 5 issues.✓ Скопировано

→ Score + prioritized fix list
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.

Поток

Plan ecosystem

/skill-forge plan domain=customer-support — design 6 coordinated skills with clear hand-off boundaries.✓ Скопировано

→ Diagram + per-skill spec
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 — эффект 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.✓ Скопировано

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
/skill-forge build	skill name (+ plan)	After plan is approved
/skill-forge review	skill path	After any significant change
/skill-forge evolve	findings to fix	Improvement loop
/skill-forge publish	skill path	Ready to ship

Стоимость и лимиты

Во что обходится

Квота 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

Generated skills are your responsibility — run the review step before shipping and never auto-publish without human sign-off.

Устранение неполадок

Частые ошибки и исправления

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-creator	You want skills to be auto-suggested from observed patterns	More framework, higher learning curve
Hand-authoring SKILL.md	Single, simple skill you understand fully	No review layer, easy to miss conventions

Ещё

Ресурсы

📖 Читать официальный README на GitHub

🐙 Открытые задачи

🔍 Все 400+ MCP-серверов и Skills