CtrlK
BlogDocsLog inGet started
Tessl Logo

coding-standards

Use when reviewing code quality, asking whether a refactor or design is good, looking for code smells, or evaluating architecture tradeoffs. Identifies shallow interfaces, invalid state models, unclear boundaries, hidden effects, weak failure contracts, over-mocking, over-abstraction, compatibility glue, and clean-looking code that preserves bad models.

72

Quality

89%

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

78%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 well-structured, mostly lean design-review standard with a strong reference map and a clear applied workflow. Its only weaknesses are decorative epigraphs and the absence of an explicit error-recovery feedback loop in the workflow.

Suggestions

Remove or compress the two opening epigraphs; they are decorative token cost that does not advance the skill's instructions.

Add an explicit feedback loop to 'How to Apply' (e.g., when verification fails, revise the finding's evidence or shape and re-verify before reporting) to push workflow clarity toward 5.

Tighten any abstract prose in 'Core Tenets' into concrete, checkable criteria so actionability reaches fully executable guidance.

DimensionReasoningScore

Conciseness

The body is largely lean and assumes Claude's competence, but the two decorative epigraphs (Abelson/Sussman, Dijkstra) add tokens that do not instruct, keeping it just below a 5.

4 / 5

Actionability

As an instruction-only review skill it provides concrete guidance—a 6-step 'How to Apply' procedure, a ready-finding checklist, and rebutted 'Rejected Framings'—with only minor gaps versus fully copy-paste-ready material.

4 / 5

Workflow Clarity

The 'How to Apply' section gives a clear sequenced workflow with a validation checkpoint ('Verify the claim') and a readiness checklist, but lacks an explicit error-recovery feedback loop, fitting anchor 4 over 5.

4 / 5

Progressive Disclosure

A well-organized overview with a Reference Map table that maps concerns to one-level-deep, clearly signaled markdown links, all 10 of which resolve to real files—exemplary progressive disclosure.

5 / 5

Total

17

/

20

Passed

Description

100%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 exemplary: third-person voice, a clear 'Use when' trigger clause, comprehensive concrete capability list, and a distinctive niche. It answers both what and when with natural, varied trigger terms.

DimensionReasoningScore

Specificity

Lists multiple specific concrete capabilities—'shallow interfaces, invalid state models, unclear boundaries, hidden effects, weak failure contracts, over-mocking, over-abstraction, compatibility glue, and clean-looking code that preserves bad models'—giving comprehensive coverage rather than the minor gaps of a 4.

5 / 5

Completeness

Explicitly answers both 'what' ('Identifies shallow interfaces...') and 'when' with concrete trigger phrases ('Use when reviewing code quality... evaluating architecture tradeoffs'), matching the anchor 5 example.

5 / 5

Trigger Term Quality

Natural phrases a developer would actually say are present and comprehensive: 'reviewing code quality', 'refactor', 'design is good', 'code smells', and 'architecture tradeoffs'.

5 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (code/design review quality) with distinct triggers and minimal overlap risk with other skills.

5 / 5

Total

20

/

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
joshuadavidthomas/agent-skills
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.