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%

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 tight, executable convention guide with clear GOOD/BAD examples and unambiguous rules, well-suited to a simple single-purpose skill. No bundle files are present and none are needed.

Dimension	Reasoning	Score
Conciseness	Lean and efficient; assumes Claude knows what modules and imports are and adds only the DevTools-specific conventions, with every line earning its place.	3 / 3
Actionability	Provides concrete, executable TypeScript import snippets with explicit GOOD/BAD labels and a clear 'import * as' rule, making guidance copy-paste ready.	3 / 3
Workflow Clarity	For this single-task convention skill the required action is unambiguous (import via entrypoint with 'import * as', with a same-module exception), so workflow clarity scores 3 per the simple-skills note.	3 / 3
Progressive Disclosure	Under 50 lines with no external references needed and well-organized sections for cross-module vs same-module imports, satisfying the simple-skills progressive disclosure criteria.	3 / 3
	Total	12 / 12 Passed

Description

67%

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 distinctive, but lacks an explicit 'Use when...' trigger clause, leaving the activation condition only implied. Adding a natural-language trigger phrase would lift completeness and trigger-term quality.

Suggestions

Add an explicit 'Use when writing or modifying imports in DevTools, or when build errors mention cross-module or entrypoint imports.' trigger clause.

Broaden trigger terms to include common user phrasings like 'DevTools import errors' or 'import conventions' rather than relying on technical jargon.

Dimension	Reasoning	Score
Specificity	Lists several concrete actions: 'importing code', 'cross-module imports', 'internal imports', and the 'import * as' requirement, matching the anchor for multiple specific concrete actions.	3 / 3
Completeness	Clearly states what the skill covers, but 'when' is only implied via 'to avoid build errors' with no explicit 'Use when...' trigger, which caps completeness at 2 per the guidelines.	2 / 3
Trigger Term Quality	Includes natural terms like 'importing code' and 'build errors', but leans on technical jargon ('cross-module imports', 'import * as') and misses common user phrasings, so coverage is partial rather than comprehensive.	2 / 3
Distinctiveness Conflict Risk	The Devtools-specific import conventions and the 'import * as' requirement carve out a clear niche unlikely to trigger for unrelated skills.	3 / 3
	Total	10 / 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-imports/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.