you-might-not-need-a-comment

Analyze and fix redundant or self-explanatory inline comments — remove noise, promote genuine documentation to TSDoc

Quality

76%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/you-might-not-need-a-comment/SKILL.md

Quality

Content

87%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 lean, highly actionable, and well-structured, but its short workflow omits a validation checkpoint for what is a destructive, batch-style edit pass.

Suggestions

Add an explicit validation step after applying fixes (e.g. 'After deletion/promotion, ensure the project still type-checks/tests pass') to lift workflow_clarity above 3.

Consider a brief 'verify the comment was truly redundant' checkpoint before each deletion to make the safety bias operational in the workflow.

Dimension	Reasoning	Score
Conciseness	Lean and well-organized; assumes Claude's competence, never explains what a comment is, and every section (anti-patterns, do-not-flag, bias) earns its place.	5 / 5
Actionability	Concrete, executable guidance with specific before/after examples ('// increment counter' above 'counter++') and decisive verbs (Delete, Convert) covering the common cases for an instruction-only skill.	5 / 5
Workflow Clarity	A clear two-step sequence is present, but the destructive/batch comment-deletion pass lacks an explicit validation checkpoint (e.g. recompile/retest after removal), capping this dimension at 3 per the rubric.	3 / 5
Progressive Disclosure	Under 50 lines with no need for external references; well-organized sections (rule, anti-patterns, do-not-flag, bias, steps) make navigation trivial, qualifying for the simple-skill exception.	5 / 5
	Total	18 / 20 Passed

Description

66%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 specific and distinct, naming concrete actions and a clear niche, but it lacks an explicit 'Use when...' trigger clause, which caps its completeness.

Suggestions

Add an explicit 'Use when...' clause, e.g. 'Use when cleaning up noisy comments, removing redundant inline comments, or promoting documentation to TSDoc.'

Include a few more natural trigger synonyms users might say (e.g. 'unnecessary comments', 'clean up comments').

Dimension	Reasoning	Score
Specificity	Lists several concrete actions ('remove noise', 'promote genuine documentation to TSDoc', 'fix redundant or self-explanatory inline comments') with only minor coverage gaps.	4 / 5
Completeness	The 'what' is clear and concrete, but there is no 'Use when...' clause or equivalent explicit trigger guidance, capping completeness at 3 per the rubric.	3 / 5
Trigger Term Quality	Natural phrases like 'redundant or self-explanatory inline comments' and 'noise' align with what a user would say, though a few common variants ('clean up comments', 'unnecessary comments') are absent.	4 / 5
Distinctiveness Conflict Risk	The comment-cleanup / TSDoc-promotion niche is clearly distinct from other skills with only minor overlap risk against general linting skills.	4 / 5
	Total	15 / 20 Passed

Validation

93%

Warnings & errors only

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

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: simstudioai/sim
Path: .agents/skills/you-might-not-need-a-comment/SKILL.md
Commit: 7945b29

Reviewed: 3 days ago

Table of Contents

Discovery Implementation Validation

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.