devtools-source-maps

Guidelines for utilizing source maps and structured stack traces in DevTools. Covers DebuggerWorkspaceBinding, StackTrace, SymbolizedError, and related UI widgets.

Quality

65%

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

Quality

Content

80%

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 concise, actionable DevTools reference with concrete TypeScript API and widget examples plus a verification checklist. Its main gap is structural: it is a monolithic file with no progressive disclosure to separate reference materials and no explicit error-recovery feedback loop.

Dimension	Reasoning	Score
Conciseness	The body is lean and reference-style with executable snippets and minimal prose, never explaining concepts Claude already knows; every section earns its place, matching the 3 anchor rather than the padded 2.	3 / 3
Actionability	It gives concrete, specific API method calls (rawLocationToUILocation, createStackTraceFromProtocolRuntime, createSymbolizedError) with real import paths and widget usage, which is copy-paste-shaped executable guidance rather than pseudocode.	3 / 3
Workflow Clarity	Structure and a verification checklist are present, but the skill is reference-oriented rather than a sequenced multi-step workflow and lacks an explicit validate-to-fix-to-retry feedback loop, so it does not reach the 3 anchor.	2 / 3
Progressive Disclosure	Sections are well-organized, but the skill is a monolithic single file over 50 lines with no external references or content split, so it sits at the 2 anchor rather than the one-level-deep reference structure of 3.	2 / 3
	Total	10 / 12 Passed

Description

50%

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 identifies a clear, specific niche and concrete components but is framed as passive "guidelines" with no action verbs and no "Use when" trigger clause. It is solid but unspecific in voice and trigger guidance, landing at 2 across all dimensions.

Suggestions

Add an explicit 'Use when...' clause stating when Claude should invoke this skill (e.g., 'Use when rendering or parsing stack traces, symbolized errors, or source-mapped locations in the DevTools frontend').

Replace passive framing ('Guidelines for utilizing', 'Covers') with concrete action verbs (e.g., 'Map runtime coordinates to original source locations, build structured stack traces, and render symbolized errors').

Lead with natural user-facing trigger terms (source maps, stack traces, error rendering) and demote internal class names (DebuggerWorkspaceBinding, SymbolizedError) to keep trigger-term quality high.

Dimension	Reasoning	Score
Specificity	It names a concrete domain and specific components ("DebuggerWorkspaceBinding, StackTrace, SymbolizedError"), but the only verbs are vague ("utilizing", "Covers") rather than multiple specific concrete actions, so it does not reach the multi-action anchor of 3.	2 / 3
Completeness	It answers "what" (guidelines for utilizing source maps and structured stack traces, covering named components) but provides no "Use when..." or equivalent explicit trigger guidance, which caps completeness at 2 per the rubric guideline.	2 / 3
Trigger Term Quality	Natural terms like "source maps" and "stack traces" appear, but they are padded with internal class-name jargon ("DebuggerWorkspaceBinding", "SymbolizedError") users would not say, and common variations are missing, so it stops at 2 rather than 3.	2 / 3
Distinctiveness Conflict Risk	The DevTools source-map/stack-trace niche is genuinely specific and unlikely to conflict, but the description lacks distinct explicit triggers and leans on internal class names, so it does not meet the 3 anchor's requirement of distinct triggers.	2 / 3
	Total	8 / 12 Passed

Validation

100%

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: ChromeDevTools/devtools-frontend
Path: .agents/skills/devtools-source-maps/SKILL.md
Commit: 184a74d

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.