CtrlK
BlogDocsLog inGet started
Tessl Logo

cerebro-regression-tests

Add focused regression coverage for Cerebro review findings, bugs, and security edge cases.

62

Quality

73%

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 ./.claude/skills/cerebro-regression-tests/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

93%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 content is an exemplary lean, actionable skill body with concrete Go/Rust commands, specific boundary categories, and well-organized sections, with only a minor gap in explicit error-recovery feedback loops.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence, providing no concept padding and only the directives and commands needed, with every token earning its place.

5 / 5

Actionability

It gives fully executable commands ('-count=1 -v', 'cargo test -p <crate>', 'make changed-check', 'make verify'), names specific package domains, and enumerates concrete security boundary cases, covering the common cases copy-paste ready.

5 / 5

Workflow Clarity

The five-step sequence is clear with explicit verification commands ('make changed-check', 'make verify') and a success-criteria checkpoint, but it lacks an explicit if-fails-then-retry feedback loop.

4 / 5

Progressive Disclosure

Under 50 lines with no need for external references, the skill uses well-organized 'Instructions' and 'Success Criteria' sections, which per the rubric earns a 5 for simple skills.

5 / 5

Total

19

/

20

Passed

Description

53%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 concise and third-person with a clear, niche-scoped 'what', but it lacks an explicit 'when to use' trigger clause and offers only modest keyword variation, capping completeness and trigger-term quality at the midpoint.

Suggestions

Append an explicit 'Use when...' clause, e.g. 'Use when adding regression tests after fixing Cerebro bugs or security findings.'

Broaden trigger terms with natural synonyms like 'regression tests', 'security edge cases', 'vulnerabilities', or 'tenant/auth/pagination fixes' so users' phrasings match.

Spell out concrete actions (reproduce, write table-driven test, assert boundary) in the description to lift specificity above a single verb.

DimensionReasoningScore

Specificity

The phrase 'Add focused regression coverage' names the domain and one concrete action, with enumerated targets ('review findings, bugs, and security edge cases'), but it is a single action rather than a comprehensive list of distinct capabilities.

3 / 5

Completeness

It has a clear 'what' (add focused regression coverage for named categories) but no 'Use when...' clause or equivalent trigger guidance, so per the rubric completeness is capped at 3.

3 / 5

Trigger Term Quality

It includes relevant keywords like 'regression coverage', 'bugs', and 'security edge cases' that a user might say, but misses common synonyms and variations such as 'tests', 'vulnerabilities', or 'fixes'.

3 / 5

Distinctiveness Conflict Risk

The Cerebro-scoped regression-testing niche is mostly distinct with minimal overlap risk, though the general testing framing could lightly overlap with broader test-writing skills.

4 / 5

Total

13

/

20

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
writer/cerebro
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.