CtrlK
BlogDocsLog inGet started
Tessl Logo

thermo-nuclear-code-quality-review

Use for a thermo-nuclear code quality review, thermonuclear review, deep code quality audit, or especially harsh maintainability review — abstraction quality, giant files, and spaghetti-condition growth.

60

Quality

69%

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/thermo-nuclear-code-quality-review/SKILL.md

The canonical home for this skill is thermo-nuclear-code-quality-review in cursor/plugins

SKILL.md
Quality
Evals
Security

Quality

Content

60%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 well-structured, actionable review-prompt skill with concrete thresholds, phrases, and remedies. Its main weakness is verbosity: the same core concepts are restated across several large sections, inflating the token budget without adding new guidance.

Suggestions

Consolidate the repeated code-judo, 1k-line, spaghetti, wrapper, and cast themes into a single section; currently they reappear in 'Non-Negotiable Standards', 'What to Flag Aggressively', 'Preferred Remedies', and 'Approval Bar'.

Trim 'What to Flag Aggressively' and 'Preferred Remedies' to the highest-value items, since most map one-to-one onto rules already stated above.

Cut generic exhortations like 'be ambitious' and 'be extremely thorough' that assume little of Claude, or fold them once into the Core Prompt.

DimensionReasoningScore

Conciseness

The body is noticeably verbose and heavily repetitive: the code-judo idea, the 1k-line rule, spaghetti branching, wrappers, and casts each reappear across 'Non-Negotiable Standards', 'Primary Review Questions', 'What to Flag Aggressively', 'Preferred Remedies', and 'Approval Bar', restating the same concepts 3-4 times.

2 / 5

Actionability

For an instruction-only review skill the guidance is concrete and actionable — a hard 1000-line threshold, copy-paste-ready 'good phrases', and a specific list of preferred remedies — though some directives remain abstract ('be ambitious', 'be extremely thorough').

4 / 5

Workflow Clarity

There is no multi-step transformation workflow, but the single review action is unambiguous and the 'Output Expectations' section provides a clear 1-7 priority sequence for findings; no validation checkpoint is needed since the skill produces comments rather than mutating code.

4 / 5

Progressive Disclosure

The file is self-contained with clear, well-labeled section headers and no external references (none exist), making navigation easy; minor gaps come from the length and repetition that could be consolidated into a tighter overview.

4 / 5

Total

14

/

20

Passed

Description

78%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, explicit description with a clear 'Use when' trigger and good synonym coverage, distinguishing itself via the harsh-review framing. It is held back only by listing focus areas rather than concrete reviewer actions and some overlap risk with ordinary code review.

DimensionReasoningScore

Specificity

Names the review domain and several focus areas ('abstraction quality, giant files, and spaghetti-condition growth') but lists no concrete reviewer actions like 'flag', 'suggest remedies', or 'block approval'; coverage of what the review does is partial.

3 / 5

Completeness

Explicitly answers both what (a harsh code-quality review focused on abstraction, file size, and spaghetti growth) and when via the 'Use for ...' clause with multiple concrete trigger phrases.

5 / 5

Trigger Term Quality

Includes natural variations a user would say ('deep code quality audit', 'maintainability review', 'code quality review') plus the 'thermo-nuclear'/'thermonuclear' synonym pair, though the thermo-nuclear phrasing is unusual rather than commonly spoken.

4 / 5

Distinctiveness Conflict Risk

The 'thermo-nuclear / especially harsh' framing carves a distinct niche, but it overlaps with general code-review skills when a user simply asks to 'review this code'.

4 / 5

Total

16

/

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
nearai/ironclaw
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.