mcpbeat

Local Vco Roles

foryourhealth111-pixel/local-vco-roles

Codex-local role pack for dialectic multi-agent reviews, designed to be compatible with the local vibe skill.

2k tokens
context cost
the whole folder, loaded on every use
8
files
ships runnable scripts
0
copies elsewhere
how many repositories repackaged it
2583
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository
npx skills add https://github.com/foryourhealth111-pixel/Vibe-Skills --skill local-vco-roles

What comes with it

4 208 bytes besides the instruction
references/role-prompts/arch-critic.md
references/role-prompts/bug-analyst.md
references/role-prompts/integration-analyst.md
references/role-prompts/team-lead.md
references/role-prompts/usability-analyst.md
references/vibe-compatibility.md
scripts/new-run.ps1

The instruction itself

6 sections, as written by the author

local-vco-roles

Codex-local role pack for dialectic multi-agent reviews, designed to be compatible with the local vibe skill.

When to Use

Use this skill when:

  • You run /vibe and need a stable role set for dialectic review.
  • You want reproducible multi-role analysis using TeamCreate-style orchestration.
  • You need standardized outputs across team-lead / bug / architecture / integration / usability roles.

Vibe Compatibility Contract (Must Follow)

  • Grade handshake:
  • M/L: do NOT force TeamCreate orchestration.
  • XL: TeamCreate workflow is allowed.
  • Rule-1 boundary:
  • Never mix multiple agent systems for the same task.
  • Follow vibe conflict rules first.
  • Command priority:
  • User explicit command > vibe routing > this role pack defaults.
  • Output severity:
  • Always use CRITICAL > HIGH > MEDIUM > LOW.
  • Staged confirmation:
  • Keep major confirmation points aligned with vibe team protocol.
  • Memory behavior:
  • Default state tracking via TodoWrite-style task state.
  • Optional enhancements (if available) must not become hard dependencies.

Role Prompt Library

  • Team lead: references/role-prompts/team-lead.md
  • Bug analyst: references/role-prompts/bug-analyst.md
  • Architecture critic: references/role-prompts/arch-critic.md
  • Integration analyst: references/role-prompts/integration-analyst.md
  • Usability analyst: references/role-prompts/usability-analyst.md
  • Read references/vibe-compatibility.md.
  • Create 5 tasks (lead + 4 analysts).
  • Assign each role using the prompt files above.
  • Collect results and aggregate by severity.
  • Produce one merged decision set (keep / simplify / remove).

Optional Utility

  • Run scaffold helper: scripts/new-run.ps1 -Topic <name>

How to use it

Copy the folder

Take foryourhealth111-pixel/local-vco-roles from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.