CtrlK
BlogDocsLog inGet started
Tessl Logo

cerebro-regression-tests

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

81

1.11x
Quality

72%

Does it follow best practices?

Impact

94%

1.11x

Average score across 3 eval scenarios

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.factory/skills/cerebro-regression-tests/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

86%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 a tight, well-structured instruction set that assumes Claude's competence and includes concrete commands plus a verification checkpoint. The main gap is the absence of an executable example test and an explicit validate-and-retry loop.

DimensionReasoningScore

Conciseness

The body is lean and efficient with no padding or over-explanation of concepts Claude already knows; every step earns its place.

5 / 5

Actionability

Guidance is concrete and executable — table-driven Go tests, the specific `-count=1 -v` flag, `make verify`, and enumerated boundary categories — but lacks a copy-paste example test, leaving a minor gap.

4 / 5

Workflow Clarity

A clear numbered reproduce → write → secure → fixture → run sequence is present with a verification checkpoint (`-count=1 -v` then `make verify`), but the validate-fix-retry feedback loop is only implicit.

4 / 5

Progressive Disclosure

This simple, single-purpose skill is well under 50 lines with no need for external references and is organized into clear Instructions and Success Criteria sections, meeting the simple-skill exception for a top score.

5 / 5

Total

18

/

20

Passed

Description

58%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 reasonably specific, scoping to a clear Cerebro regression niche, but it omits any explicit 'Use when…' trigger guidance and could surface more natural synonyms. Adding a trigger clause would most directly raise the completeness and trigger-term scores.

Suggestions

Append an explicit 'Use when…' clause naming concrete triggers, e.g. 'Use when fixing a Cerebro review finding, bug, or security edge case and you need to lock in regression coverage.'

Broaden trigger-term coverage with natural synonyms users actually say, such as 'regression tests', 'test failures', and 'reproduce the bug'.

Reframe the action list as distinct operations (reproduce, write table-driven test, add security boundary cases, verify) rather than a list of targets to strengthen specificity.

DimensionReasoningScore

Specificity

The description names the domain ('regression coverage') and lists several concrete targets — 'Cerebro review findings, bugs, and security edge cases' — which goes beyond 1-2 actions but stops short of comprehensive distinct operations.

4 / 5

Completeness

It clearly states what the skill does but lacks any explicit 'Use when…' trigger clause, so 'when' is only weakly implied — capping completeness at 3 per the guidelines.

3 / 5

Trigger Term Quality

It includes relevant natural terms ('regression coverage', 'bugs', 'security edge cases') a debugging user might say, but misses common synonyms like 'regression tests' or 'test failures'.

3 / 5

Distinctiveness Conflict Risk

The 'Cerebro review findings' scoping carves a distinct niche with specific triggers and only minor overlap risk with adjacent testing skills.

4 / 5

Total

14

/

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.