CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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.

Quality

68%

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

53%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 short and correctly delegates detail to references/rule.md, but it spends lines explaining concepts Claude already knows and lacks concrete, executable guidance such as build-tool comment-stripping configurations. The Check/Fix/Explain/Code Review section structure is redundant and reads like a generated prompt template.

Suggestions

Replace the abstract "Configure build tools to strip comments automatically" with concrete configuration examples (e.g., Terser drop_console, html-loader options, or a build-time regex) in the body or rule.md.

Drop or merge the "Explain" section and the security rationale paragraph; keep one concise statement of the rule and link to rule.md for details.

Add a validation checkpoint after removal, such as re-rendering the page and diffing against the original markup to confirm only comments and debug code were stripped.

DimensionReasoningScore

Conciseness

The body is lean overall, but the intro paragraph and the "Explain" section restate concepts Claude already knows (comments leak sensitive info, increase file size) and largely duplicate each other, fitting the 3 anchor of mostly efficient with some unnecessary explanation.

3 / 5

Actionability

Concrete guidance exists about what to remove ("TODO, FIXME, DEBUG comments") and what to keep ("accessibility and legal comments"), but there are no concrete commands or build-tool configuration examples for stripping comments, leaving the guidance incomplete per the 3 anchor.

3 / 5

Workflow Clarity

Check, Fix, and Explain sections provide a rough sequence, but no validation checkpoint exists (e.g., verify markup renders identically after removal) and the Check/Fix/Code Review sections overlap confusingly, matching the 3 anchor of steps listed with validation gaps.

3 / 5

Progressive Disclosure

The body serves as an organized overview with a clearly signaled, one-level-deep reference to references/rule.md (verified to exist with no nested references), though the four overlapping mode sections leave minor organization gaps, fitting anchor 4.

4 / 5

Total

13

/

20

Passed

Description

70%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 answers both what and when with reasonably natural trigger terms, but suffers from awkward machine-generated phrasing ("related to Remove comments and debug code in production") and only one concrete action. Rewriting it as a third-person capability statement with clearer triggers would raise specificity and completeness.

Suggestions

Rewrite the description in third person with a clear what statement, e.g. "Removes development comments, debug code, and temporary markup from production HTML. Use when reviewing templates, rendered HTML, or shared components for leftover TODO/FIXME comments, console.log statements, or debug code before deployment."

Add natural trigger synonyms users would say: console.log, TODO/FIXME comments, strip comments, debug code removal, production build.

Fix the grammatical break "related to Remove comments and debug code in production" so the sentence reads as a coherent trigger clause rather than a pasted rule title.

DimensionReasoningScore

Specificity

The description names the domain (templates, rendered HTML, shared components) and one to two concrete actions ("Validate the final browser-facing markup"), but offers no comprehensive list of specific actions, matching the 3 anchor.

3 / 5

Completeness

Both what ("Validate the final browser-facing markup") and when ("Use when reviewing templates, rendered HTML, or shared components") are answered, but the what is awkwardly phrased and the when could be more specific, matching anchor 4 rather than 5.

4 / 5

Trigger Term Quality

Natural trigger terms like "comments", "debug code", "production", "templates", and "rendered HTML" are present, but common synonyms such as console.log, TODO/FIXME, or "strip comments" are missing, fitting the 4 anchor.

4 / 5

Distinctiveness Conflict Risk

The production comment/debug-code cleanup niche is mostly distinct, but the boilerplate "Use when reviewing templates, rendered HTML, or shared components related to..." prefix would be shared by sibling frontend-checklist skills, creating minor overlap risk.

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

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository

thedaviddias/Front-End-Checklist

Path

skills/clean-up-comments/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.