● Communauté
foryourhealth111-pixel
⚡ Instantané
Vibe-Skills
par 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.
Pourquoi l'utiliser
Fonctionnalités clés
- 340+ sub-skills coordinated by the VCO orchestrator
- Enforced workflow: clarify → plan → execute → verify
- 3 execution grades (M/L/XL) matched to task complexity
- Cross-session memory per workspace — picks up where you left off
- Multi-agent parallelization with conflict prevention
Démo en direct
Aperçu en pratique
Cas d'usage
Usages concrets : Vibe-Skills
Quand l'utiliser : A feature that touches 3+ files and a data migration — too big to yolo, not big enough for a full project.
Déroulement
-
State the goal
Use VibeSkills. Add role-based access to our admin panel — execution grade L.✓ Copié
→ VCO enters clarify phase, asks focused questions
-
Approve the plan
Plan looks right, execute.✓ Copié
→ VCO executes phases in order, verifies at each boundary
-
Resume later
Continue where we left off.✓ Copié
→ VCO restores memory and proceeds
Résultat : A feature shipped without the usual agent-drift.
Pièges
- Wrong grade chosen, over/under-engineered result — Set M for quick tasks, XL only for multi-day efforts
Quand l'utiliser : You have 5 modules to update with the same pattern and want them done in parallel.
Déroulement
-
Describe the parallel work
VibeSkills — parallelize: update each of these 5 modules to use the new auth client. Grade L.✓ Copié
→ VCO spawns parallel workers with conflict guards
-
Review the verify output
Show the verify-phase report for each worker.✓ Copié
→ Per-worker pass/fail with the concrete checks run
Résultat : Several modules updated in one session with a clean audit trail.
Pièges
- Shared-state conflicts (e.g. same config file) — VCO serializes writes to shared files; you'll see delays on contested paths
Combinaisons
Associez-le à d'autres MCPs pour un effet X10
VCO drives the work; filesystem MCP is the hands
VibeSkills + filesystem — scaffold the new feature structure.✓ Copié
Checkpoint each phase as a git commit so you can roll back
VibeSkills — commit after each phase with a descriptive message.✓ Copié
Coût et limites
Coût d'exécution
- Quota d'API
- None
- Tokens par appel
- Higher than simple skills — the 4-phase workflow adds overhead
- Monétaire
- Free — skill is local
- Astuce
- Use grade M for small tasks; XL burns tokens fast.
Sécurité
Permissions, secrets, portée
Stockage des identifiants : No credentials — skill is prompts
Sortie de données : None from the skill itself
- Memory is stored per-workspace; be aware of what Claude retains across sessions.
Dépannage
Erreurs courantes et correctifs
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.
Alternatives
Vibe-Skills vs autres
| Alternative | Quand l'utiliser | Compromis |
|---|
| planning-with-files-skill | You just want the 3-file persistence pattern without the full orchestrator | Simpler, less structured |
| skillforge | You want an intelligent skill router without the governed workflow overhead | Lighter weight |