CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

brewcode-review

Review Brewcode product hooks, scripts, skills, agents, templates, and native compatibility contracts using the shared report-only superreview workflow.

Quality

70%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./.codex/skills/brewcode-review/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

61%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 a deliberately terse adapter skill that efficiently delegates the review engine to superreview while adding a concrete product-specific checklist, but it reads as dense thematic paragraphs rather than an actionable workflow — no step sequence, validation checkpoints, or executable checks are given inline.

Suggestions

Convert the implicit flow into a short numbered sequence with an explicit validation checkpoint (e.g., validate each finding against evidence/counterexamples before reporting).

Include at least one concrete executable check or command per major surface (e.g., how to run the existing non-mutating parity checks referenced in the text).

Add section headers (e.g., "## Scope", "## Check surfaces", "## Reporting") so the dense paragraphs are scannable without loading the referenced skill.

DimensionReasoningScore

Conciseness

The body is lean, assumes Claude's competence, and explains no known concepts, but a few dense phrases (e.g., "keeping the user's explicit product/path/revision boundary" restating the opening boundary) could be tightened.

4 / 5

Actionability

Concrete guidance exists in the enumerated check surfaces ("hook event/schema and JSON output; ESM/async/error handling; shell interpreter/platform assumptions"), but there are no commands, runnable checks, or file-specific steps — execution details are entirely delegated to the linked superreview skill.

3 / 5

Workflow Clarity

A rough implicit sequence runs through the paragraphs (apply contract → read sources → check surfaces → review via consumer → report), but steps are not enumerated and validation checkpoints are implicit rather than explicit.

3 / 5

Progressive Disclosure

The body is short with clearly signaled one-level-deep references to the sibling superreview skill and its review contract, but it uses dense paragraphs with no section headers, leaving minor organization gaps.

4 / 5

Total

14

/

20

Passed

Description

66%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 specific and well-scoped to the Brewcode domain with concrete artifact types and third-person voice, but it entirely lacks a "Use when..." trigger clause and leans on internal jargon ("report-only superreview workflow", "native compatibility contracts") that users would not naturally say.

Suggestions

Add an explicit trigger clause, e.g., "Use when the user asks to review or audit a Brewcode product's hooks, scripts, skills, agents, or templates."

Include natural synonyms users might say such as "audit" or "check" alongside "review".

Trim internal jargon like "report-only superreview workflow" or pair it with a plain-language equivalent.

DimensionReasoningScore

Specificity

Names six concrete artifact types ("hooks, scripts, skills, agents, templates, and native compatibility contracts") with a clear "Review" action, but uses only a single verb rather than multiple distinct concrete actions.

4 / 5

Completeness

Has a clear "what" (review Brewcode product artifacts via the superreview workflow) but no "when" — there is no "Use when..." clause or equivalent trigger guidance, which caps completeness at 3.

3 / 5

Trigger Term Quality

"hooks", "scripts", "skills", "agents", "templates", and "review" are natural terms a user would say, giving good keyword coverage, though jargon like "report-only superreview workflow" and missing synonyms (e.g., "audit", "check") keep it below comprehensive.

4 / 5

Distinctiveness Conflict Risk

The "Brewcode product" scope creates a clear niche with distinct artifact-type triggers, leaving only minor overlap risk with generic code-review skills.

4 / 5

Total

15

/

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.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 2 suspicious

Warning

Total

15

/

16

Passed

Repository

kochetkov-ma/claude-brewcode

Path

.codex/skills/brewcode-review/SKILL.md

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.