Skip to content
Back to skills

Local Vco Roles

ASecurity

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

  • 3,126 stars
  • 0 votes
  • 0 copies
  • 1 view
  • Added May 29, 2026
ai-agents

Security analysis

A100/100

Pro scans all 8 files and shows the line behind each finding

Scanned May 29, 2026

npx -y skills add foryourhealth111-pixel/Vibe-Skills --skill local-vco-roles --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Local Vco Roles?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Local Vco Roles
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/foryourhealth111-pixel-local-vco-roles/badge)](https://www.skillsdirectory.com/skills/foryourhealth111-pixel-local-vco-roles)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: local-vco-roles
description: 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>`

Files in this skill

  • SKILL.md1.9 KB
  • references/role-prompts/arch-critic.md401 B
  • references/role-prompts/bug-analyst.md423 B
  • references/role-prompts/integration-analyst.md420 B
  • references/role-prompts/team-lead.md460 B
  • references/role-prompts/usability-analyst.md379 B
  • references/vibe-compatibility.md1.2 KB
  • scripts/new-run.ps1903 B

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…