CtrlK
BlogDocsLog inGet started
Tessl Logo

cerebro-finding-rule

Design or change a Cerebro finding rule. Use for new durable rules, rule lifecycle fixes, fingerprint changes, or promoting source evidence into findings.

70

Quality

86%

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

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.

A tight, well-structured checklist that externalizes design rationale to AGENTS.md and stays focused on actionable decisions and validation. It would benefit only from an explicit validate-fix-retry loop in the Validate section.

Suggestions

Add an explicit feedback loop to the Validate section (e.g., 'If a check fails, fix the rule and re-run until clean') to push workflow_clarity to 5.

Optionally pair the abstract design directives ('Choose the anchor first') with a one-line concrete example to strengthen actionability.

DimensionReasoningScore

Conciseness

The body is a lean working checklist that defers rationale to AGENTS.md and assumes Claude's competence; every line earns its place with no padded concept explanations.

5 / 5

Actionability

Concrete actionable items ("Explicit Lifecycle semantics and stable FingerprintFields", "make finding-dsl-check policy-rule-check ...") are present, but several design directives like "Choose the anchor first" are guidance rather than copy-paste steps.

4 / 5

Workflow Clarity

A clear Decide -> Needs -> Test matrix -> Validate sequence with concrete make targets, though the Validate section lacks an explicit fix-and-retry feedback loop.

4 / 5

Progressive Disclosure

Under 50 lines, well-organized into clearly headed sections, with the single rationale reference (AGENTS.md) one level deep and clearly signaled; no bundle bloat.

5 / 5

Total

18

/

20

Passed

Description

87%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.

A strong, third-person description that pairs a clear capability statement with an explicit "Use for..." trigger clause enumerating concrete scenarios. It is concise, distinct, and avoids fluff.

DimensionReasoningScore

Specificity

"Design or change a Cerebro finding rule" names the domain plus concrete actions, and "new durable rules, rule lifecycle fixes, fingerprint changes, or promoting source evidence into findings" lists several specific use-cases with minor coverage gaps.

4 / 5

Completeness

It explicitly answers what ("Design or change a Cerebro finding rule") and when ("Use for new durable rules, rule lifecycle fixes, fingerprint changes, or promoting source evidence into findings") with concrete trigger phrases.

5 / 5

Trigger Term Quality

Terms like "Cerebro finding rule", "fingerprint changes", and "rule lifecycle fixes" are the natural phrases a user of this domain would say, with good but not exhaustive synonym coverage.

4 / 5

Distinctiveness Conflict Risk

"Cerebro finding rule" is a highly specific internal niche with distinct triggers and minimal overlap risk with other skills.

5 / 5

Total

18

/

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.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 1 suspicious

Warning

Total

15

/

16

Passed

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.