CtrlK
BlogDocsLog inGet started
Tessl Logo

clean-up-comments

Use when reviewing templates, rendered HTML, or shared components related to Remove comments and debug code in production. Validate the final browser-facing markup, not just the source framework abstraction.

61

Quality

72%

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 ./skills/clean-up-comments/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

70%

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 well-organized, simple review skill with clean progressive disclosure to a verified reference, but its guidance is instructional rather than executable and includes some generic restating.

Suggestions

Replace generic prompt sections (e.g., 'Explain why...') with concrete, value-adding guidance or remove them to improve token efficiency.

Add executable specifics for the build-tool guidance, such as named tools (esbuild/Terser html-minifier-terser) or a one-line config snippet for stripping comments.

Tighten the Check/Fix sections into a concrete review checklist of exact element types to flag rather than restated task descriptions.

DimensionReasoningScore

Conciseness

The body is mostly efficient and avoids over-explaining basics, but generic prompt sections like 'Explain why cleaning up code before production is important...' restate knowledge Claude already has and could be tightened.

2 / 3

Actionability

It gives concrete categories to act on ('Remove TODO, FIXME, DEBUG comments', 'Configure build tools to strip comments automatically') but stays at an instructional/flagging level without executable specifics such as named build tools or commands.

2 / 3

Workflow Clarity

This is a simple single-purpose review skill whose single action (review rendered HTML and flag comment/debug violations) is unambiguous and sequenced via its section ordering, qualifying for level 3 under the simple-skills guidance.

3 / 3

Progressive Disclosure

The body is a concise overview that points to one real, existing reference ('references/rule.md') with a clear signal, keeping references one level deep and easy to navigate.

3 / 3

Total

10

/

12

Passed

Description

75%

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 explicitly covers both what and when with a clear 'Use when...' trigger and a distinct niche, but its action list is not comprehensive and its trigger-term coverage could be broader.

Suggestions

List multiple specific concrete actions (e.g., 'Strip TODO/FIXME/DEBUG comments, remove console logs and unused markup, configure build-tool comment stripping') to reach full specificity.

Broaden trigger terms with common user phrasings such as 'production build', 'HTML cleanup', or 'remove debug code from markup'.

DimensionReasoningScore

Specificity

It names a domain ('templates, rendered HTML, or shared components') and concrete actions ('reviewing...', 'Validate the final browser-facing markup'), but does not list multiple specific concrete actions as the level-3 anchor requires.

2 / 3

Completeness

Both 'what' (review and validate the final browser-facing markup) and 'when' (explicit 'Use when reviewing templates, rendered HTML, or shared components...') are present, matching the level-3 anchor with an explicit trigger.

3 / 3

Trigger Term Quality

It includes relevant natural terms a user might say ('templates, rendered HTML, shared components', 'comments and debug code'), but the coverage of common variations is limited and tied closely to the rule title phrase.

2 / 3

Distinctiveness Conflict Risk

It targets a clear niche (production comment/debug cleanup in rendered HTML/templates) with distinct triggers, making it unlikely to fire for unrelated skills; more specific than the level-2 overlap example.

3 / 3

Total

10

/

12

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

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository
thedaviddias/Front-End-Checklist
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.