CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

error-debugging-multi-agent-review

Use when working with error debugging multi agent review

Quality

43%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/error-debugging-multi-agent-review/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

25%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 reads as a design document for an imaginary tool rather than operational guidance: buzzword-heavy prose plus pseudocode of non-existent APIs, with no executable workflow or validation steps. Its genuinely useful material (local execution boundary, safety limitations, fallback behavior) is buried in roughly 200 lines of padding.

Suggestions

Replace the illustrative pseudocode and marketing prose with one concrete, executable review sequence (e.g. run quality/security/architecture checks, collect findings, verify each finding against the source, then synthesize a prioritized report) with explicit validation checkpoints.

Cut conceptual sections like 'Context and Purpose', 'Depth/Breadth/Intelligence/Adaptability', and the seven coordination-strategy subsections — Claude already knows multi-agent orchestration concepts; keep only what is specific to this skill.

Resolve the 'Reference Implementations' dead end: either expand the two named scenarios into worked examples or move detailed orchestration material into real reference files and link them one level deep.

DimensionReasoningScore

Conciseness

The body is heavily padded with marketing prose ("transcend traditional single-perspective review approaches", "Contextual Intelligence", "Intelligent Consolidation") and ~90 lines of illustrative pseudocode that adds no executable knowledge. A few tight sections (Local execution boundary, Limitations) keep it above the 'severely verbose' anchor.

2 / 5

Actionability

Every code block invokes non-existent machinery (ConflictResolutionEngine(), QualityScoreCalculator, multi_agent_review()), and the only real directives are high-level ("perform the review roles directly in sequence") without the specific steps to execute. This matches 'minimal concrete guidance; high-level hints' rather than anchor 3, since the pseudocode illustrates concepts rather than incomplete-but-real steps.

2 / 5

Workflow Clarity

The numbered sections (1-7) form a taxonomy of concepts, not a sequenced workflow: no ordered steps for conducting a review, no validation checkpoints, and the fallback path never defines which 'sequence' the roles should run in. Anchor 2 ('rough sequence present but many gaps; validation absent') fits; anchor 3 would require an actual step list.

2 / 5

Progressive Disclosure

No bundle files exist and ~220 lines are inlined, including orchestration patterns and API-style detail that clearly belong in separate reference files. The 'Reference Implementations' section lists two bare titles as dead ends. Anchor 2 ('content that clearly belongs in separate files is inlined') matches; it is not a monolithic unstructured wall (1) because section headers exist.

2 / 5

Total

8

/

20

Passed

Description

36%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 is a garbled trigger clause that names a domain but says nothing about what the skill does. It would rarely trigger correctly because users are unlikely to phrase a need this way, and it cannot be distinguished from general debugging or review skills.

Suggestions

State concrete capabilities in third person, e.g. 'Orchestrates multiple specialized review agents (security, architecture, performance) to produce a consolidated, prioritized code review report.'

Rewrite the trigger with natural user phrasing: 'Use when asked to review code or a PR with multiple perspectives, run a multi-agent code review, or consolidate findings from several reviewers.'

Ensure both 'what' and 'when' appear explicitly so the completeness dimension is fully answered.

DimensionReasoningScore

Specificity

The description names a domain ("error debugging multi agent review") but lists zero concrete actions or capabilities — it is a trigger clause with no 'what'. This sits between anchor 1 (entirely vague) and anchor 3 (1-2 concrete actions), closer to the vague end since no action verb or capability appears.

2 / 5

Completeness

Only a 'when' is present ("Use when working with...") with no 'what' — the exact anchor-2 pattern ("Use when working with documents"). It cannot score 3 because no capability is stated, and cannot score 1 because the trigger guidance is explicit.

2 / 5

Trigger Term Quality

"error debugging" and "multi agent review" are semi-natural keywords a user might say, but common variations and synonyms ("code review", "review agents", "debug a review pipeline") are missing, matching the anchor for some relevant keywords without common variations.

3 / 5

Distinctiveness Conflict Risk

The multi-agent review niche is somewhat specific, but the keyword-salad phrasing and absence of stated capabilities leave it overlapping with general debugging and code-review skills. Not mostly-distinct (4) since nothing delineates its scope; not very-broad (2) since the domain term is fairly narrow.

3 / 5

Total

10

/

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.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository

BigSimmo/Communication

Path

.agents/skills/error-debugging-multi-agent-review/SKILL.md

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.