CtrlK
BlogDocsLog inGet started
Tessl Logo

local-vco-roles

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

50

Quality

55%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./bundled/skills/local-vco-roles/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

65%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is well-structured and token-efficient with excellent progressive disclosure through real, one-level-deep reference files. Its main weakness is the workflow: steps are sequenced but lack validation checkpoints and executable detail for aggregation.

Suggestions

Add an explicit validation/verification step to the XL workflow, e.g. after collecting results, check that every role returned a finding set before aggregating, and re-run any missing role.

Make the aggregation step actionable: specify the severity ordering (CRITICAL > HIGH > MEDIUM > LOW) and how to deduplicate or prioritize overlapping findings into the keep/simplify/remove decision set.

Show a minimal example of how a task is assigned from a role-prompt file (e.g. the TodoWrite/TeamCreate call shape) so the workflow is copy-paste executable.

DimensionReasoningScore

Conciseness

The body is lean with well-organized sections and avoids explaining concepts Claude already knows; only minor phrasing in the contract/workflow lists could be tightened, fitting 'Efficient; minor instances of over-explanation that could be trimmed'.

4 / 5

Actionability

It points to real role-prompt files and gives one concrete command (`scripts/new-run.ps1 -Topic <name>`), but the core workflow steps ('Collect results and aggregate by severity', 'Produce one merged decision set') describe outcomes without executable detail, matching 'Some concrete guidance but incomplete'.

3 / 5

Workflow Clarity

The Recommended XL Workflow is a clear 5-step numbered sequence, but it contains no validation or verification checkpoints for a batch multi-agent operation, which caps workflow_clarity at 3 per the rubric's batch-operation rule.

3 / 5

Progressive Disclosure

The body is an overview with well-signaled, one-level-deep references to real files (role-prompt markdown files, vibe-compatibility.md, new-run.ps1), and content is appropriately split, matching 'Clear overview with well-signaled one-level-deep references'.

5 / 5

Total

15

/

20

Passed

Description

45%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description clearly states what the skill is but omits any 'when to use it' trigger guidance, which caps completeness and reduces trigger quality. It is third-person and reasonably distinct but action-light and jargon-heavy.

Suggestions

Add an explicit 'Use when...' clause naming natural triggers, e.g. 'Use when running /vibe and you need a reproducible multi-role review team.'

Replace or supplement jargon like 'dialectic' with concrete actions users would say, such as 'run multi-role analysis', 'assign review roles', and 'aggregate findings by severity'.

Sharpen distinctiveness by stating how this role pack differs from invoking /vibe alone.

DimensionReasoningScore

Specificity

The description names the domain ("dialectic multi-agent reviews") and what the artifact is ("role pack"), but lists no concrete actions or verbs describing what it does, matching the anchor 'Names the domain but actions are minimal or generic'.

2 / 5

Completeness

A clear 'what' is present (a role pack for dialectic multi-agent reviews) but there is no 'Use when...' or equivalent trigger guidance for when Claude should invoke it, which caps completeness at 3 per the rubric guidelines.

3 / 5

Trigger Term Quality

It includes some relevant terms ("multi-agent reviews", "role pack", "vibe skill"), but leans on technical jargon ("dialectic") and misses natural user phrasings and synonyms, fitting 'Some relevant keywords but missing common variations or synonyms'.

3 / 5

Distinctiveness Conflict Risk

It occupies a niche (role pack tied to the local vibe skill) but explicitly targets compatibility with the existing vibe skill and overlaps with other review-oriented skills, fitting 'Somewhat specific but could still overlap with similar skills'.

3 / 5

Total

11

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

referenced_paths_exist

Referenced path issues: 5 deeper-than-1-level

Warning

Total

15

/

16

Passed

Repository
foryourhealth111-pixel/Vibe-Skills
Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.