CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

56

Quality

63%

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

65%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.

A well-structured, lean overview that correctly defers detail to a single real reference file, but the body itself stops short of executable guidance and lacks an explicit verify-after-fix checkpoint for what is effectively a batch code modification.

Suggestions

Move at least one concrete executable snippet inline (e.g. a minimal eslint 'no-console' rule or a Terser drop_console config) so the body is actionable without opening the reference.

Add an explicit validation step to the workflow — e.g. 'After removing, run the build and confirm no console.* calls remain in the production bundle' — to lift the workflow_clarity cap.

De-duplicate the console method list between Quick Reference and the Check section to tighten token efficiency.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence — short imperatives and bullets, no explaining what console is — with only minor redundancy (the Check section re-lists methods already in Quick Reference and Code Review echoes the description).

4 / 5

Actionability

Quick Reference names concrete methods to remove, but the executable guidance (eslint/webpack/vite config, logging utility code) is deferred to references/rule.md, and 'Configure build tools to strip console statements automatically' is a high-level hint without the actual config in the body.

3 / 5

Workflow Clarity

Check → Fix → Explain → Code Review gives a rough sequence, but there is no explicit validation checkpoint; 'state how the change should be verified in the browser' instructs Claude to describe verification rather than performing it, and removing console statements across a codebase is a batch operation that the rubric caps at 3 without validation.

3 / 5

Progressive Disclosure

The body is a concise overview with well-organized sections and a single, clearly signaled one-level-deep reference ('see references/rule.md', verified to exist) for full implementation details, code examples, and framework-specific guidance.

5 / 5

Total

15

/

20

Passed

Description

62%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 and targets a distinct niche, but its actions are framed as generic review/inspect verbs rather than the concrete removal work the skill performs, and it leans on a grammatically awkward 'related to Remove console statements' phrasing.

Suggestions

Lead with the concrete action the skill performs (e.g. 'Remove console.log/debug/table statements from production JavaScript') before the review framing.

Add natural trigger synonyms users would say — 'console.log', 'logging', 'debug statements' — alongside 'console statements'.

Tighten the awkward 'related to Remove console statements in production' clause into a clean third-person capability statement.

DimensionReasoningScore

Specificity

Names the console-statement domain and a couple concrete review actions ('Inspect both source code and the browser execution path'), but the actions are generic review/inspect verbs rather than the skill's actual removal actions, and coverage is not comprehensive.

3 / 5

Completeness

Both halves are present — 'Use when reviewing scripts, client components, bundles, or runtime behavior…' (when) and 'Inspect both source code and the browser execution path so fixes target the real bottleneck or bug' (what) — but the 'when' clause could be more specific and the what/when phrasing is awkwardly fused.

4 / 5

Trigger Term Quality

'console statements' and 'production' are natural user terms, but common synonyms and variations like 'console.log', 'logging', or 'debug statements' are missing.

3 / 5

Distinctiveness Conflict Risk

'Remove console statements in production' is a distinct niche with minimal conflict risk, though the broad 'reviewing scripts, client components, bundles, or runtime behavior' prefix overlaps slightly with other frontend review skills.

4 / 5

Total

14

/

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.

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.