/ 目錄 / 演練場 / Vibe-Skills
← 全部伺服器 ↗ GitHub
● 社群 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

安裝

作者儲存庫 · Claude Skills 官方文件

使用場景

實戰用法： 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 搭配，撬動十倍槓桿

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

更多

資源

📖 閱讀 GitHub 上的官方 README

🐙 查看未解決的 issue

🔍 瀏覽全部 400+ MCP 伺服器和 Skills