CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

brooks-lint

AI code reviewer grounded in classic software engineering books for catching design smells, coupling issues, and architectural risks.

Quality

60%

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 ./.agents/skills/brooks-lint/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

46%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 well-sectioned and the example output format is a genuine strength, but roughly a third of the content is README-style marketing (origin story, installation, related skills, external links) and the actual review methodology remains high-level. Defining severity levels and a concrete review procedure would convert the book-lens concept into executable guidance.

Suggestions

Cut the README-only sections — the Fred Brooks naming story, Installation, Related Skills, and Additional Resources links — they spend tokens without improving review behavior.

Define the severity scheme (CRITICAL/HIGH/LOW) that Best Practices tells the user to act on, and specify the required output format (the '[Book] finding' lines) as a rule rather than only an implicit example.

Replace the six one-line 'How It Works' hints with a short sequenced procedure (read the target, apply each Review Category, rank findings by severity, output in the defined format).

DimensionReasoningScore

Conciseness

The body reads like a promotional README: the naming origin story ("Named after Fred Brooks... because the hardest bugs are conceptual"), a restated overview paragraph, Installation, Related Skills, and external links (GitHub, Dev.to) are all padding a skill does not need, and the book-principles table largely restates concepts Claude already knows. Several sections could be cut outright, matching the 'noticeably verbose; several unnecessary explanations or padded sections' anchor.

2 / 5

Actionability

There is some concrete material — the example output block demonstrates the "[Book] finding" format and the Review Categories table maps categories to books and catchable issues — but the core review procedure stays at the hint level ('Smell detection: Flags violations of DRY, SRP, Law of Demeter'), severity levels (CRITICAL/HIGH/LOW) are referenced but never defined, and no concrete steps for conducting a review are given. This fits 'some concrete guidance but incomplete; missing key details'.

3 / 5

Workflow Clarity

The 'How It Works' numbered list enumerates analysis types rather than a sequenced review procedure, and there is no checkpoint guidance (e.g. how to prioritize or verify findings before reporting). It reaches 'steps listed but... checkpoints missing or implicit'; it cannot score higher because the single action — apply lenses and emit findings — is never laid out end-to-end, though the read-only nature avoids the destructive-operation cap.

3 / 5

Progressive Disclosure

There are no bundle files (references/, scripts/, assets/ all absent), so all content lives in a single SKILL.md; sections and tables are clearly headed and easy to navigate, and the core lens/category content is appropriately placed inline for a prompt-style skill. It falls short of 5 only because README-style sections (Installation, Related Skills, Additional Resources) are inlined where they add no navigational value, a minor organization gap matching the 'good structure... minor organization gaps' anchor.

4 / 5

Total

12

/

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 communicates a clear niche — book-grounded design/architecture review — with reasonably natural trigger terms, but it omits any explicit 'when to use' guidance and describes only one broad action. Adding a 'Use when...' clause and enumerating a couple more concrete actions would lift it substantially.

Suggestions

Add an explicit trigger clause, e.g. 'Use when reviewing code for design quality, before refactors, or when the user mentions code smells, coupling, or architecture.'

Enumerate the concrete actions the reviewer performs (e.g. flags design smells, scores coupling, checks stability patterns, outputs severity-ranked findings) instead of the single 'catching' verb.

Drop 'AI' from 'AI code reviewer' — it adds no trigger value and slightly inflates the claim.

DimensionReasoningScore

Specificity

The description names the domain ("AI code reviewer") and what it catches ("design smells, coupling issues, and architectural risks"), which are specific objects, but the only action offered is a single generic one (reviewing/catching). It sits between the anchor listing 1-2 concrete actions (3) and the one listing several specific actions with minor gaps (4) — it does not enumerate multiple distinct actions like reviewing, scoring, or flagging with severity.

3 / 5

Completeness

The 'what' is clearly stated ("AI code reviewer grounded in classic software engineering books for catching design smells, coupling issues, and architectural risks") but there is no 'Use when...' clause or equivalent trigger guidance, capping completeness at 3 per the judging guidelines.

3 / 5

Trigger Term Quality

"code reviewer", "design smells", "coupling issues", and "architectural risks" are natural phrases users would say when wanting this skill, matching the good-coverage anchor. Common variations such as "refactoring", "code quality", or "software design" are missing, keeping it below 5.

4 / 5

Distinctiveness Conflict Risk

The book-lens framing ("grounded in classic software engineering books") gives it a niche, but "AI code reviewer" for "design smells" and "architectural risks" overlaps heavily with the crowded code-review and refactoring skill space, matching the 'somewhat specific but could still overlap with similar skills' anchor.

3 / 5

Total

13

/

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

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository

BigSimmo/Communication

Path

.agents/skills/brooks-lint/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.