CtrlK
BlogDocsLog inGet started
Tessl Logo

agent-analyze-code-quality

Agent skill for analyze-code-quality - invoke with $agent-analyze-code-quality

59

1.49x
Quality

40%

Does it follow best practices?

Impact

94%

1.49x

Average score across 3 eval scenarios

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/agent-analyze-code-quality/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

72%Weight 40%Scale 1-3

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

The body is concise and well-organized with a clear output template, but it offers descriptive analysis guidance rather than executable steps and lacks a sequenced review workflow with validation checkpoints. It works as an instruction-only skill but would benefit from more concrete, actionable procedure.

Suggestions

Add a concrete review workflow: an ordered sequence (e.g. select target files -> run lint/complexity checks -> classify findings -> produce report) with an explicit validation or self-check step before emitting the report.

Provide at least one executable example (e.g. a grep/complexity command or AST-based check) so the analysis is actionable rather than purely descriptive.

Specify how the 'Overall Quality Score: X/10' is computed so the output is reproducible rather than subjective.

DimensionReasoningScore

Conciseness

The body is lean — short bulleted lists and a tight output template with no padding and no explanations of concepts Claude already knows; every token roughly earns its place.

3 / 3

Actionability

It provides a concrete, copy-paste-ready output template and specific thresholds (e.g. '>50 lines', '>500 lines'), but the analysis guidance is descriptive rather than executable, with no code or commands to run.

2 / 3

Workflow Clarity

Responsibilities are listed and the output is structured, but there is no sequenced multi-step workflow and no validation/feedback checkpoint for the review process.

2 / 3

Progressive Disclosure

With no external bundle files needed, the content is organized into clear, single-level sections (responsibilities, criteria, smell detection, output format) that are easy to navigate.

3 / 3

Total

10

/

12

Passed

Description

7%Weight 40%Scale 1-3

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 generic boilerplate that names a domain and invocation syntax but fails to state what the skill does or when to use it, and includes no natural trigger terms. It is distinguishable only by its named niche, not by its wording.

Suggestions

Rewrite the description to state concrete actions, e.g. 'Reviews code for smells, complexity, and technical debt, and suggests refactoring opportunities.'

Add an explicit 'Use when...' clause with natural trigger terms users would actually say (e.g. 'Use when the user asks for a code review, wants to find code smells, or needs to assess technical debt').

Drop the invocation-syntax boilerplate ('invoke with $agent-analyze-code-quality') from the description; it adds no capability or trigger information.

DimensionReasoningScore

Specificity

The phrase 'Agent skill for analyze-code-quality - invoke with $agent-analyze-code-quality' names a domain but lists no concrete actions, only an invocation mechanism; closest to the 'vague or no actions' anchor.

1 / 3

Completeness

It answers neither 'what does this do' (the phrase is circular) nor 'when should Claude use it'; both are weak or missing, matching the lowest anchor.

1 / 3

Trigger Term Quality

It contains no natural keywords a user would say; 'invoke with $agent-analyze-code-quality' is command syntax/jargon, matching the 'no natural keywords; technical jargon' anchor.

1 / 3

Distinctiveness Conflict Risk

The named niche 'analyze-code-quality' is somewhat specific, but the surrounding boilerplate ('Agent skill for X - invoke with $X') is generic and could overlap with other analysis skills.

2 / 3

Total

5

/

12

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
ruvnet/claude-flow
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.