CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

performance-testing-review-multi-agent-review

Use when working with performance testing review multi agent review

Quality

38%

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/performance-testing-review-multi-agent-review/SKILL.md

The canonical home for this skill is error-debugging-multi-agent-review in BigSimmo/Communication

SKILL.md
Quality
Evals
Security

Quality

Content

28%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 actionable guidance: non-executable pseudocode, marketing fluff, and architecture description with no concrete workflow, commands, or validation steps for actually performing a multi-agent review. The safety-oriented 'Local execution boundary' section is the most genuinely instructive part. It needs to be rebuilt around what Claude should actually do with the tools it has.

Suggestions

Replace the pseudocode blocks (route_agents, ReviewContext, execute_review, etc.) with concrete instructions Claude can execute, e.g. how to fan out review dimensions using its actual Agent/subagent tools and how to merge the findings.

Define a real sequenced workflow with validation checkpoints — e.g. gather target scope → run parallel dimension reviews → synthesize and de-duplicate findings → verify each reported issue against the source → present a prioritized report.

Cut the marketing prose ('sophisticated AI-powered', the Depth/Breadth/Intelligence/Adaptability bullets) and move any retained illustrative orchestration examples into a references/ file so SKILL.md stays a lean overview.

DimensionReasoningScore

Conciseness

The body is padded with marketing prose ('sophisticated AI-powered code review system', 'transcend traditional single-perspective review approaches'), abstract bullets (Depth/Breadth/Intelligence/Adaptability), and generic best-practice lists that add nothing Claude doesn't know. It is not 1 because it avoids explaining basic external concepts, but several sections are clearly unnecessary padding.

2 / 5

Actionability

All code is pseudocode invoking undefined constructs (ConflictResolutionEngine, ReviewOptimizer, QualityScoreCalculator, multi_agent_review), and the body itself concedes these are 'illustrative roles and examples, not installed dependencies'. The actual instructions ('Apply relevant best practices and validate outcomes') are high-level hints with no specific executable steps, matching the 'minimal concrete guidance' anchor rather than the pseudocode-with-real-content level of 3.

2 / 5

Workflow Clarity

The Claude-facing sequence is four vague steps (clarify goals, apply best practices, validate outcomes, provide actionable steps) with no checkpoints or commands; the numbered coordination sections and sequential workflow example describe an aspirational tool's architecture rather than an executable review procedure. A rough sequence exists but steps are poorly defined and validation is implicit at best.

2 / 5

Progressive Disclosure

The body has clear section headers and explicitly notes 'no additional playbook is bundled', but roughly 150 lines of illustrative pseudocode and architecture description are inlined in SKILL.md where a lean overview (or reference files holding the examples) would belong. Structure exists, but content that should be separate is inline — the anchor-3 fit; not 4 because the bulk of the file is detail rather than overview.

3 / 5

Total

9

/

20

Passed

Description

20%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, repetitive trigger phrase that omits any statement of what the skill does and mislabels its domain ('performance testing' vs the actual code-review orchestration content). It would rarely be selected correctly and would conflict with performance-testing skills. It needs a full rewrite stating concrete capabilities plus accurate, natural trigger terms.

Suggestions

Rewrite the description to state concrete capabilities, e.g. 'Orchestrates multi-agent code reviews across security, architecture, performance, and code-quality dimensions. Use when the user asks for a comprehensive, multi-perspective code review or mentions multi-agent review orchestration.'

Remove the mismatched 'performance testing' trigger phrase, which points at the wrong domain and invites conflicts with performance-testing skills.

Cover natural trigger variations users would actually say, such as 'code review', 'review my PR/diff', 'multi-agent review', and 'review orchestration'.

DimensionReasoningScore

Specificity

The description 'Use when working with performance testing review multi agent review' names no concrete actions or capabilities whatsoever — it is pure trigger phrasing with no 'what', matching the 'entirely vague; no concrete actions' anchor.

1 / 5

Completeness

Only a 'when' clause is present ('Use when working with...') with no 'what' at all — exactly anchor 2 ('only when is present without what'). It cannot reach 3 because there is no clear statement of what the skill does.

2 / 5

Trigger Term Quality

It contains a couple of domain keywords ('performance testing', 'multi agent review') but they are strung together unnaturally with repetition ('review multi agent review') and 'performance testing' mismatches the skill's actual code-review topic, so users would not naturally say this phrase. It falls below anchor 3's 'some relevant keywords' because the terms are garbled and misleading rather than merely incomplete.

2 / 5

Distinctiveness Conflict Risk

The 'performance testing' wording invites false triggers for performance-testing skills while the body is about multi-agent code review orchestration, creating high overlap and confusion risk with related skills. It is not 1 because it is not entirely generic, but it is clearly below the 'mostly distinct' level.

2 / 5

Total

7

/

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/performance-testing-review-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.