CtrlK
BlogDocsLog inGet started
Tessl Logo

cerebro-source-integration

Scaffold Cerebro source integrations following existing source, preview, runtime, and test patterns.

60

Quality

71%

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-source-integration/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 exceptionally lean and well-structured with a clear sequenced workflow and concrete verification commands. Its main gap is the absence of explicit error-recovery guidance and any executable code examples.

DimensionReasoningScore

Conciseness

The body is lean and directive with no concept re-explanation or padding; every line (Instructions, Boundaries) earns its place and assumes Claude's competence.

5 / 5

Actionability

Concrete commands ("make changed-check", "make verify") and specific test categories (config validation, preview decoding, pagination) are present, but as an instruction-only skill it lacks executable code examples for the common cases.

4 / 5

Workflow Clarity

A clear 7-step sequence ends with a validation chain (focused tests, then changed-check, then verify), but there is no explicit error-recovery feedback loop describing what to do when a check fails.

4 / 5

Progressive Disclosure

Under 50 lines with well-organized sections (Instructions, Boundaries) and a single clearly-signaled one-level reference to AGENTS.md, fitting the simple-skill exception for a 5.

5 / 5

Total

18

/

20

Passed

Description

57%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 distinct but lacks explicit trigger guidance (no "Use when..." clause) and relies on product jargon rather than natural user phrasing. It answers "what" clearly while omitting "when."

Suggestions

Add a "Use when..." clause naming natural trigger phrases (e.g., "Use when adding or scaffolding a new Cerebro source integration, or when the user asks to wire up a new data source.")

Include everyday synonyms alongside jargon so users who say "add a source" or "set up a connector" are captured.

Consider listing 1-2 more concrete actions (e.g., "scaffold, validate config, and add preview/runtime sync") to lift specificity beyond a single verb.

DimensionReasoningScore

Specificity

The description names the domain (Cerebro source integrations) and one concrete action ("Scaffold") with several pattern areas (source, preview, runtime, test), but it stays at a high level rather than listing multiple distinct concrete actions.

3 / 5

Completeness

It clearly answers the "what" (scaffold source integrations following existing patterns) but provides no "Use when..." clause or equivalent trigger guidance, capping completeness at 3 per the rubric.

3 / 5

Trigger Term Quality

Keywords like "Cerebro source integrations", "preview", "runtime", and "test patterns" are relevant but technical/jargon-heavy, missing the natural phrases a user would actually say.

3 / 5

Distinctiveness Conflict Risk

"Cerebro source integrations" carves out a clear, product-specific niche with distinct triggers and minimal risk of overlapping with unrelated skills.

5 / 5

Total

14

/

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.