CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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

70%

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/console-cleanup/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

57%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 a well-structured overview with excellent progressive disclosure — short, cleanly sectioned, with a real, clearly-signaled one-level-deep reference holding the implementation details. It is held back by generic direction instead of executable guidance in the body, no validation step for what is a batch code edit, and redundant 'why it matters' explanation plus Quick Reference/Fix duplication.

Suggestions

Drop the 'why console statements are bad' explanation and the Quick Reference bullets that duplicate the Fix section; a single concrete Fix instruction is sufficient for a skill this simple.

Add one inline validation checkpoint to the Check/Fix sequence (e.g. 'After removal, verify the feature still behaves correctly in the browser, including one lazy-loaded or failing path') to satisfy the batch-operation feedback-loop requirement.

Inline one minimal executable artifact — such as the eslint 'no-console' rule or a terser drop_console snippet — so the body is actionable on its own rather than deferring all specifics to the reference.

DimensionReasoningScore

Conciseness

The body is short but padded: the intro sentence ('Console statements leak sensitive information, impact performance, and create unprofessional user experiences') explains a concept Claude already knows, and the Quick Reference bullets ('Remove console.log...', 'Configure build tools to strip console statements') duplicate the Fix section's guidance. Mostly efficient with some unnecessary explanation — anchor 3, not anchor 4 because of this redundant explanation and bullet/section overlap.

3 / 5

Actionability

Concrete specifics exist — the Check section names exact methods ('console.log, console.debug, console.warn, console.error') and the Quick Reference says 'Keep console.error for critical error tracking' — but the body contains no executable commands or configuration; the how (build-tool stripping, lint rules, logging service setup) is entirely deferred to the reference. Anchor 3 ('some concrete guidance but incomplete'), not 4 since nothing in the body is directly executable.

3 / 5

Workflow Clarity

Check → Fix → Explain → Code Review provides a recognizable sequence, but the body includes no validation checkpoint; verification appears only as something to 'state how the change should be verified in the browser' rather than an actual step. Removing console statements across a codebase is a batch edit, and per the rubric missing validation in batch operations caps workflow_clarity at 3.

3 / 5

Progressive Disclosure

The body is under 50 lines, cleanly sectioned (Quick Reference, Check, Fix, Explain, Code Review), and points to a single one-level-deep reference ('For full implementation details, code examples, and framework-specific guidance, see references/rule.md') which exists and appropriately holds the bulk code examples. Clear overview with a well-signaled reference — anchor 5.

5 / 5

Total

14

/

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 has an explicit 'Use when' trigger, decent natural keyword coverage, and a distinct niche, but its action statements are generic review phrasing ('reviewing', 'inspect') rather than concrete capabilities, and the embedded sentence 'related to Remove console statements in production' reads as ungrammatical boilerplate. Third-person voice is used correctly throughout.

Suggestions

Rewrite 'related to Remove console statements in production' into a grammatical capability statement, e.g. 'Flags and removes console.log/debug/table statements from production JavaScript, or configures build tools to strip them automatically.'

Add the most common natural trigger variations users would say — 'console.log', 'debug logging', 'clean up logs' — to improve trigger term coverage toward anchor 5.

State 2-3 concrete capabilities (scan for specific console methods, replace with a logging service, configure lint/build stripping) instead of the generic 'inspect source code and browser execution path' phrasing.

DimensionReasoningScore

Specificity

Names the domain ('console statements in production') with 1-2 actions ('reviewing scripts, client components, bundles, or runtime behavior', 'Inspect both source code and the browser execution path'), but the actions are generic review verbs rather than a comprehensive list of specific capabilities. It does not reach anchor 4 because no several distinct concrete actions are enumerated, and not anchor 2 because the domain and two inspect actions are explicitly named.

3 / 5

Completeness

Both parts are present: an explicit trigger ('Use when reviewing scripts, client components, bundles, or runtime behavior related to...') and a what ('Inspect both source code and the browser execution path so fixes target the real bottleneck or bug'). Not anchor 5 because the 'what' relies on generic review phrasing rather than clearly stated concrete capabilities.

4 / 5

Trigger Term Quality

Includes natural terms users would say: 'console statements', 'production', 'scripts', 'client components', 'bundles', 'runtime behavior'. Missing common variations such as 'console.log', 'debugger', or 'logging cleanup', so it falls short of anchor 5's comprehensive synonym coverage but sits above anchor 3's partial keyword set.

4 / 5

Distinctiveness Conflict Risk

The 'console statements in production' niche is distinct with minimal conflict risk against other frontend-checklist rules. The broad opener 'reviewing scripts, client components, bundles, or runtime behavior' overlaps with generic code-review skills, keeping it below anchor 5 but above anchor 3 since the console qualifier keeps the trigger specific.

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