console-cleanup

Use when reviewing scripts, client components, bundles, or runtime behavior related to Remove console statements in production. Inspect both source code and the browser execution path so fixes target the real bottleneck or bug.

Quality

64%

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 ./skills/console-cleanup/SKILL.md

Quality

Content

72%

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, token-efficient overview that correctly delegates detail to a real one-level reference, scoring highly on conciseness and progressive disclosure. It loses points on actionability and workflow clarity because executable code and validation checkpoints are not present in the body itself.

Suggestions

Include at least one small executable snippet or exact command in the body (e.g. the ESLint `no-console` rule or Terser `drop_console: true`) so the skill is copy-paste actionable without opening the reference.

For the Code Review mode, add a short sequenced check-and-verify loop (locate statements -> remove/replace -> verify in browser DevTools) with an explicit validation checkpoint.

Keep the current lean structure; only surface the most-used fix inline and leave the rest in references/rule.md.

Dimension	Reasoning	Score
Conciseness	The body is lean (~30 lines) with no padded explanations of what console statements are, uses terse Quick Reference bullets and short task directives, and defers detail to the reference — every token earns its place, matching the 'lean and efficient' anchor.	3 / 3
Actionability	It names specific methods ("Remove console.log, console.debug, console.table") and gives direction ("Configure build tools to strip console statements automatically"), but the body itself contains no executable code blocks — the copy-paste-ready examples live in references/rule.md, so guidance is 'concrete but incomplete'.	2 / 3
Workflow Clarity	It organizes parallel task modes (Check / Fix / Explain / Code Review) but presents no sequenced multi-step workflow and no in-body validation checkpoints, matching the 'steps listed but validation gaps; checkpoints missing' anchor.	2 / 3
Progressive Disclosure	The body is a concise, well-organized overview that clearly signals a single one-level-deep reference ("see `references/rule.md`"), and that bundle file exists, matching the 'clear overview with well-signaled one-level-deep references' anchor.	3 / 3
	Total	10 / 12 Passed

Description

57%

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 has an explicit trigger clause and a clear, distinctive niche, but the capability statement is weakened by the rule title being pasted mid-sentence and by missing common trigger variants like 'console.log'. Tightening the grammar and adding natural logging terms would lift the lower dimensions.

Suggestions

Rewrite the description in clean third-person prose led by the capability (e.g. "Reviews JavaScript source and browser execution paths to find and remove console statements for production"), eliminating the mid-sentence pasted rule title.

Add natural trigger terms users would actually say — "console.log", "debug logging", "remove logs", "console statements" — to broaden trigger coverage.

Keep the "Use when..." clause but make the 'what it does' a distinct action sentence rather than reusing the rule name as a noun phrase.

Dimension	Reasoning	Score
Specificity	Quotes concrete actions ("reviewing scripts, client components, bundles, or runtime behavior", "Inspect both source code and the browser execution path") but they overlap around a single review/inspect theme rather than a broad set of distinct operations, matching the 'names domain and some actions' anchor.	2 / 3
Completeness	The 'when' is explicit ("Use when reviewing...") and the 'what' is present, but the capability is conveyed via the awkwardly embedded rule title ("related to Remove console statements in production") rather than a clean verb-led statement, so the 'what' is weak/implied rather than clearly stated.	2 / 3
Trigger Term Quality	It includes a "Use when..." clause with relevant terms ("scripts", "client components", "bundles", "console statements", "production") but omits common user phrasings like "console.log", "logging", or "debug statements", so it has 'some relevant keywords but missing common variations'.	2 / 3
Distinctiveness Conflict Risk	The console-cleanup niche is clear and specific ("Remove console statements in production", "console statements") with distinct triggers unlikely to fire for unrelated skills, matching the 'clear niche with distinct triggers' anchor.	3 / 3
	Total	9 / 12 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
metadata_version	'metadata.version' is missing	Warning

	Total	15 / 16 Passed

Repository: thedaviddias/Front-End-Checklist
Path: skills/console-cleanup/SKILL.md
Commit: 48405aa

Reviewed: about 8 hours 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.