How do I install the Local Vco Roles skill?

Run npx skillmds add majiayu000/local-vco-roles in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Local Vco Roles safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Local Vco Roles?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Local Vco Roles free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Local Vco Roles?

majiayu000 (@majiayu000) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Local Vco Roles by majiayu000 — Agent Skill

Name: Local Vco Roles
Rating: 4.2 (5 reviews)
Author: majiayu000

File contents

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

Recommended XL Workflow

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>

---name: local-vco-rolesdescription: Codex-local role pack for dialectic multi-agent reviews, designed to be compatible with the local vibe skill.--- # 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: 1. You run `/vibe` and need a stable role set for dialectic review. 2. You want reproducible multi-role analysis using TeamCreate-style orchestration. 3. You need standardized outputs across team-lead / bug / architecture / integration / usability roles. ## Vibe Compatibility Contract (Must Follow) 1. Grade handshake: - M/L: do NOT force TeamCreate orchestration. - XL: TeamCreate workflow is allowed. 2. Rule-1 boundary: - Never mix multiple agent systems for the same task. - Follow `vibe` conflict rules first. 3. Command priority: - User explicit command > `vibe` routing > this role pack defaults. 4. Output severity: - Always use `CRITICAL > HIGH > MEDIUM > LOW`. 5. Staged confirmation: - Keep major confirmation points aligned with `vibe` team protocol. 6. 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` ## Recommended XL Workflow 1. Read `references/vibe-compatibility.md`. 2. Create 5 tasks (lead + 4 analysts). 3. Assign each role using the prompt files above. 4. Collect results and aggregate by severity. 5. Produce one merged decision set (`keep / simplify / remove`). ## Optional Utility - Run scaffold helper: `scripts/new-run.ps1 -Topic <name>`

Frequently asked questions