devtools-imports

Conventions for importing code in Devtools to avoid build errors. Covers cross-module imports, internal imports, and the "import * as" requirement.

Quality

83%

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

Quality

Content

100%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 content is an exemplary lean, actionable convention guide: concise, fully executable examples, clear scenario separation, and well-organized sections with no unnecessary bundle references. It fully meets the rubric for a simple single-purpose skill.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Claude's competence: a brief intro, a project-specific definition of module/entrypoint, and tight GOOD/BAD code examples with no padding or explanation of basic import concepts, so every token earns its place.	5 / 5
Actionability	Fully executable, copy-paste-ready TypeScript import snippets with concrete relative paths ('../models/trace/trace.js') and direct GOOD/BAD comparisons cover the common cross-module and same-module cases.	5 / 5
Workflow Clarity	This is a simple, single-purpose instruction skill whose single action (how to import) is unambiguous, and the two scenarios are clearly delineated under separate headers; no destructive or batch operations exist to require validation checkpoints.	5 / 5
Progressive Disclosure	At under 50 lines with no need for external references (no references/, scripts/, or assets/ bundle files exist), the content is well-organized into clear section headers, satisfying the simple-skill exception for a top score.	5 / 5
	Total	20 / 20 Passed

Description

66%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 is specific and distinct, clearly conveying what the skill covers for DevTools imports. Its main weakness is the absence of an explicit 'Use when...' trigger clause, which limits completeness to the midpoint.

Suggestions

Add an explicit trigger clause such as 'Use when writing or editing imports in the DevTools (Chrome DevTools) codebase, or when a user mentions DevTools, front_end modules, or build errors from imports.'

Mention concrete trigger terms like 'front_end', 'entrypoint', or '.js/.ts import errors' to broaden natural keyword coverage.

Clarify the trigger scope so it is unambiguous this applies specifically to the DevTools codebase rather than general TypeScript projects.

Dimension	Reasoning	Score
Specificity	Names the DevTools import domain and enumerates concrete covered areas ('cross-module imports, internal imports, and the "import * as" requirement'), giving several specific actions rather than vague language; falls just short of a 5 because the listed actions are conventions rather than the multiple distinct concrete operations (extract, fill, merge) the top anchor implies.	4 / 5
Completeness	The 'what' is clearly stated ('Conventions for importing code in Devtools to avoid build errors') but there is no 'Use when...' clause or equivalent explicit trigger guidance, only a weak implication; the missing-trigger guideline caps completeness at 3.	3 / 5
Trigger Term Quality	Includes natural developer-facing terms like 'importing code', 'Devtools', 'build errors', and 'import * as' that a user would realistically say, but omits common synonyms and file extensions (.ts/.js), so it is good-but-not-comprehensive coverage.	4 / 5
Distinctiveness Conflict Risk	The description targets a narrow, codebase-specific niche (DevTools import conventions) with distinct triggers and minimal overlap with unrelated skills, though it could overlap slightly with a general TypeScript-importing skill.	4 / 5
	Total	15 / 20 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-imports/SKILL.md
Commit: 31f2967

Reviewed: ~15 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.