/ Diretório / Playground / Vibe-Skills
← Todos os servidores ↗ GitHub
● Comunidade foryourhealth111-pixel ⚡ Instantâneo

Vibe-Skills

por 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.

▶ Ver demo 📦 Instalar 💡 Casos de uso

Por que usar

Principais recursos

Demo ao vivo

Como fica na prática

vibe-skill.replay ▶ pronto
0/0

Instalação

Repositório do autor · Documentação oficial de Skills do Claude

Casos de uso

Usos do mundo real: Vibe-Skills

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

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

Quando usar: A feature that touches 3+ files and a data migration — too big to yolo, not big enough for a full project.

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

Resultado: A feature shipped without the usual agent-drift.

Armadilhas
  • Wrong grade chosen, over/under-engineered result — Set M for quick tasks, XL only for multi-day efforts
Combine com: filesystem · github

Run parallel agents on independent parts of a large refactor

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

Quando usar: You have 5 modules to update with the same pattern and want them done in parallel.

Fluxo
  1. Describe the parallel work
    VibeSkills — parallelize: update each of these 5 modules to use the new auth client. Grade L.✓ Copiado
    → VCO spawns parallel workers with conflict guards
  2. Review the verify output
    Show the verify-phase report for each worker.✓ Copiado
    → Per-worker pass/fail with the concrete checks run

Resultado: Several modules updated in one session with a clean audit trail.

Armadilhas
  • Shared-state conflicts (e.g. same config file) — VCO serializes writes to shared files; you'll see delays on contested paths
Combine com: filesystem · git

Combinações

Combine com outros MCPs para 10× de alavancagem

vibe-skill + filesystem

VCO drives the work; filesystem MCP is the hands

VibeSkills + filesystem — scaffold the new feature structure.✓ Copiado
vibe-skill + git

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

VibeSkills — commit after each phase with a descriptive message.✓ Copiado

Ferramentas

O que este MCP expõe

FerramentaEntradasQuando chamarCusto
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

Custo e limites

O que custa rodar

Cota de API
None
Tokens por chamada
Higher than simple skills — the 4-phase workflow adds overhead
Monetário
Free — skill is local
Dica
Use grade M for small tasks; XL burns tokens fast.

Segurança

Permissões, segredos, alcance

Armazenamento de credenciais: No credentials — skill is prompts
Saída de dados: None from the skill itself

Solução de problemas

Erros comuns e correções

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.

Alternativas

Vibe-Skills vs. outros

AlternativaQuando usarTroca
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

Mais

Recursos

📖 Leia o README oficial no GitHub

🐙 Ver issues abertas

🔍 Ver todos os 400+ servidores MCP e Skills