Is local-vco-roles safe to install?

SaferSkills independently audited local-vco-roles (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.

CategoryWeightCategory scoreContribution

Securityprompt, exec, net, exfil, eval

35%

100

35.0 pts

Supply chainhash, typosquat, maintainer, lockfile

20%

100

20.0 pts

Maintenancestaleness, pinning, CI

15%

100

15.0 pts

TransparencySKILL.md, perms, README

15%

100

15.0 pts

Communityinstalls, verify, response

15%

100

15.0 pts

Findings & checks · 0 flagged

Securityscore 100 · 0 findings

✓—All security checks passedNo findings in this category for the latest scan.pass

Supply chainscore 100 · 0 findings

✓—All supply chain checks passedNo findings in this category for the latest scan.pass

Maintenancescore 100 · 0 findings

✓—All maintenance checks passedNo findings in this category for the latest scan.pass

Transparencyscore 100 · 0 findings

✓—All transparency checks passedNo findings in this category for the latest scan.pass

Communityscore 100 · 0 findings

✓—All community checks passedNo findings in this category for the latest scan.pass

The primary manifest — the file an agent reads to learn what this artifact does.

bundled/skills/local-vco-roles/SKILL.md · 1 file

bundled/skills/local-vco-roles/SKILL.md1.9 KB · Markdown

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:

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>

local-vco-roles— agent skill

Is local-vco-roles safe to install?

local-vco-roles

When to Use

Vibe Compatibility Contract (Must Follow)

Role Prompt Library

Recommended XL Workflow

Optional Utility

Audit the pieces. Scan the whole. Decide.