/ Каталог / Песочница / Vibe-Skills
● Сообщество foryourhealth111-pixel ⚡ Сразу

Vibe-Skills

автор foryourhealth111-pixel · foryourhealth111-pixel/Vibe-Skills

A super-skill that routes between 340+ governed sub-skills with a clarify→plan→execute→verify workflow and cross-session memory.

VibeSkills is more than a collection — the VCO (Vibe Code Orchestrator) runtime routes tasks to the right sub-skill, enforces a 4-phase workflow, and maintains memory across sessions in the same workspace. It supports 3 execution grades (M/L/XL) for task complexity and coordinates parallel agents on large jobs.

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

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

Живое демо

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

vibe-skill.replay ▶ готово
0/0

Установка

Выберите клиент

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

Откройте Claude Desktop → Settings → Developer → Edit Config. Перезапустите после сохранения.

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

Cursor использует ту же схему mcpServers, что и Claude Desktop. Конфиг проекта приоритетнее глобального.

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

Щёлкните значок MCP Servers на боковой панели Cline, затем "Edit Configuration".

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

Тот же формат, что и Claude Desktop. Перезапустите Windsurf для применения.

~/.continue/config.json
{
  "mcpServers": [
    {
      "name": "vibe-skill",
      "command": "git",
      "args": [
        "clone",
        "https://github.com/foryourhealth111-pixel/Vibe-Skills",
        "~/.claude/skills/Vibe-Skills"
      ]
    }
  ]
}

Continue использует массив объектов серверов, а не map.

~/.config/zed/settings.json
{
  "context_servers": {
    "vibe-skill": {
      "command": {
        "path": "git",
        "args": [
          "clone",
          "https://github.com/foryourhealth111-pixel/Vibe-Skills",
          "~/.claude/skills/Vibe-Skills"
        ]
      }
    }
  }
}

Добавьте в context_servers. Zed перезагружается автоматически.

claude mcp add vibe-skill -- git clone https://github.com/foryourhealth111-pixel/Vibe-Skills ~/.claude/skills/Vibe-Skills

Однострочная команда. Проверить: claude mcp list. Удалить: claude mcp remove.

Сценарии использования

Реальные сценарии: Vibe-Skills

Ship a medium-complexity feature end-to-end with governed phases

👤 Developers who want structure instead of improv ⏱ ~90 min intermediate

Когда использовать: A feature that touches 3+ files and a data migration — too big to yolo, not big enough for a full project.

Поток
  1. State the goal
    Use VibeSkills. Add role-based access to our admin panel — execution grade L.✓ Скопировано
    → VCO enters clarify phase, asks focused questions
  2. Approve the plan
    Plan looks right, execute.✓ Скопировано
    → VCO executes phases in order, verifies at each boundary
  3. Resume later
    Continue where we left off.✓ Скопировано
    → VCO restores memory and proceeds

Итог: A feature shipped without the usual agent-drift.

Подводные камни
  • Wrong grade chosen, over/under-engineered result — Set M for quick tasks, XL only for multi-day efforts
Сочетать с: filesystem · github

Run parallel agents on independent parts of a large refactor

👤 Devs tackling a refactor that touches many modules ⏱ ~60 min advanced

Когда использовать: You have 5 modules to update with the same pattern and want them done in parallel.

Поток
  1. Describe the parallel work
    VibeSkills — parallelize: update each of these 5 modules to use the new auth client. Grade L.✓ Скопировано
    → VCO spawns parallel workers with conflict guards
  2. Review the verify output
    Show the verify-phase report for each worker.✓ Скопировано
    → Per-worker pass/fail with the concrete checks run

Итог: Several modules updated in one session with a clean audit trail.

Подводные камни
  • Shared-state conflicts (e.g. same config file) — VCO serializes writes to shared files; you'll see delays on contested paths
Сочетать с: filesystem · git

Комбинации

Сочетайте с другими MCP — эффект x10

vibe-skill + filesystem

VCO drives the work; filesystem MCP is the hands

VibeSkills + filesystem — scaffold the new feature structure.✓ Скопировано
vibe-skill + git

Checkpoint each phase as a git commit so you can roll back

VibeSkills — commit after each phase with a descriptive message.✓ Скопировано

Инструменты

Что предоставляет этот MCP

ИнструментВходные данныеКогда вызыватьСтоимость
VCO orchestrator task + optional grade Start of any non-trivial task 0
Clarify phase task brief Auto — first phase 0
Plan phase clarified task Auto — second phase 0
Execute phase approved plan Auto — after plan approval 0
Verify phase execution results Auto — before reporting success 0

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

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

Квота API
None
Токенов на вызов
Higher than simple skills — the 4-phase workflow adds overhead
Деньги
Free — skill is local
Совет
Use grade M for small tasks; XL burns tokens fast.

Безопасность

Права, секреты, радиус поражения

Хранение учётных данных: No credentials — skill is prompts
Исходящий трафик: None from the skill itself

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

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

VCO doesn't route to expected sub-skill

Name the sub-skill explicitly: 'use VibeSkills > <sub-skill>'

Clarify phase asks too many questions

Set grade M explicitly — XL invokes deeper clarification.

Memory seems to leak between projects

Memory scopes to working directory; switch folders to switch context.

Альтернативы

Vibe-Skills в сравнении

АльтернативаКогда использоватьКомпромисс
planning-with-files-skillYou just want the 3-file persistence pattern without the full orchestratorSimpler, less structured
skillforgeYou want an intelligent skill router without the governed workflow overheadLighter weight

Ещё

Ресурсы

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

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

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