source-maps

Use when auditing slow page loads, heavy assets, or rendering delays related to Provide source maps for production debugging. Verify the actual bottleneck in DevTools, Lighthouse, or field data before recommending changes.

Quality

50%

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/source-maps/SKILL.md

Quality

Content

57%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is a well-structured overview with excellent progressive disclosure to a real references/rule.md file, but it leans on templated audit sections and defers all executable code to the reference, leaving the body itself only partially actionable with no explicit validation loop.

Suggestions

Move at least one copy-paste-ready build config snippet (e.g. webpack devtool or Vite sourcemap:'hidden') into the body so the skill is actionable without opening the reference.

Replace the generic 'Code Review' section (routes/assets/loading behavior) with source-map-relevant review guidance to avoid off-topic boilerplate.

Add an explicit validation checkpoint linking the Check outcome to the Fix step (e.g. confirm the error tracker de-minifies stack traces before considering the change done).

Dimension	Reasoning	Score
Conciseness	The body is mostly lean, but templated boilerplate ('Explain how source maps enable developers to debug...') and an off-topic 'Code Review' section about routes/assets/loading behavior add unnecessary tokens that don't serve the source-map task.	2 / 3
Actionability	Quick Reference gives concrete-ish guidance ('Upload source maps to error tracking services (e.g., Sentry)', 'Ensure source maps are correctly linked'), but the body has no executable code or commands — all real examples are deferred to references/rule.md, and 'Fix' stays abstract.	2 / 3
Workflow Clarity	Check → Fix gives a simple audit sequence with a verification step ('Verify if the project's build process generates source maps'), but there are no explicit validation checkpoints or feedback loops tying the check outcome to the fix.	2 / 3
Progressive Disclosure	The body is a concise overview that clearly signals a single one-level-deep reference ('see references/rule.md'), and that bundle file exists, giving clean navigation without nested references.	3 / 3
	Total	9 / 12 Passed

Description

42%

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 a templated performance-audit trigger with the rule title inserted mid-sentence, making it grammatically awkward and semantically misaligned with what source maps actually do. It has an explicit 'Use when' clause but describes the wrong domain and conflicts with other performance skills.

Suggestions

Rewrite the description to describe the actual capability (generate and upload source maps for production debugging of minified code) rather than generic performance auditing.

Use source-map-specific trigger terms users would naturally say, e.g. 'production errors', 'minified code', 'stack traces', 'Sentry', or 'source maps'.

Remove the inserted rule title ('related to Provide source maps for production debugging') and distinguish the trigger from sibling performance rules to reduce conflict risk.

Dimension	Reasoning	Score
Specificity	It names concrete actions ('auditing slow page loads, heavy assets, or rendering delays', 'Verify the actual bottleneck in DevTools, Lighthouse, or field data'), but those describe generic performance auditing rather than source-map generation/upload, and the rule title is wedged in mid-sentence, so coverage is not comprehensive or on-target.	2 / 3
Completeness	An explicit 'Use when...' clause is present, but the 'what' is muddled by the inserted rule title ('related to Provide source maps for production debugging') and does not clearly state the skill's actual capability, so it stops short of a clear what+when.	2 / 3
Trigger Term Quality	Terms like 'slow page loads', 'heavy assets', 'Lighthouse', and 'DevTools' are natural but belong to performance auditing; source-map-specific triggers users would say (source maps, minified code, stack traces, error tracking, Sentry) are largely absent.	2 / 3
Distinctiveness Conflict Risk	The trigger language ('slow page loads, heavy assets, rendering delays') is generic performance-audit phrasing that would fire for many sibling performance skills, creating high overlap and conflict risk.	1 / 3
	Total	7 / 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/source-maps/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.