/ 디렉터리 / 플레이그라운드 / 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와 조합해 10배 효율

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

더 보기

리소스

📖 GitHub에서 공식 README 읽기

🐙 열린 이슈 보기

🔍 400+ MCP 서버 및 Skills 전체 보기