devtools-model-management

Guidelines for creating, migrating, and registering models in front_end/models/. Covers BUILD.gn, devtools_grd_files.gni, and entrypoints.

Quality

74%

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-model-management/SKILL.md

Quality

Content

86%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 a tight, well-structured procedural guide with concrete commands, explicit 'Crucial' warnings, and a verification checklist. Its main opportunity is providing one fully-worked BUILD.gn example and tightening validation into an interleaved feedback loop rather than a final-stage checklist.

Dimension	Reasoning	Score
Conciseness	The body is lean and bullet-driven with concrete commands and no padding or re-explanation of concepts Claude already knows; every line earns its place.	5 / 5
Actionability	Provides concrete commands and copy-paste-adaptable build templates (e.g., 'devtools_module("<model_name>")', 'entrypoint = "<model_name>.ts"', 'deps = [ ":bundle" ]') with specific file paths, but relies on placeholders rather than a single fully-worked example, leaving minor gaps.	4 / 5
Workflow Clarity	A clearly sequenced 0-5 workflow with a baseline-test checkpoint up front and a final Build/Lint/Test verification checklist including a regression check; validation is end-staged rather than a tight interleaved feedback loop, placing it just below the score-5 anchor.	4 / 5
Progressive Disclosure	Under 50 lines, single-purpose, and organized into clearly-headed sections with no nested references; per the simple-skills note this qualifies for a 5 with just well-organized sections.	5 / 5
	Total	18 / 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 is specific and clearly distinct within a narrow DevTools niche, but it omits any 'Use when...' trigger clause and leans on technical jargon over natural user phrasing. Adding explicit trigger guidance and common-synonym terms would raise completeness and trigger-term quality.

Suggestions

Append an explicit 'Use when ...' clause (e.g., 'Use when creating or migrating a model into front_end/models/, or when wiring a new model into BUILD.gn / devtools_grd_files.gni.') to satisfy the completeness 'when' requirement.

Add natural-sounding synonyms a user might say (e.g., 'DevTools model', 'add a new model module', 'register a model target') alongside the existing build-system jargon to improve trigger-term quality.

Optionally mention file extensions or concrete triggers (e.g., '.gn', '.gni') to broaden natural keyword coverage.

Dimension	Reasoning	Score
Specificity	Names the domain and three concrete actions ('creating, migrating, and registering models') tied to specific build artifacts ('BUILD.gn, devtools_grd_files.gni, and entrypoints'), matching the score-4 anchor of several specific actions with minor coverage gaps.	4 / 5
Completeness	The 'what' is clearly stated, but there is no 'Use when...' or equivalent explicit trigger guidance, which per the judging guidelines caps completeness at 3.	3 / 5
Trigger Term Quality	Keywords are present ('models', 'migrating', 'BUILD.gn', 'entrypoints') but skew toward DevTools-internal jargon rather than natural phrases a user would say, and lack synonyms or file-extension variants.	3 / 5
Distinctiveness Conflict Risk	The description targets a narrow niche (DevTools models in front_end/models/ with BUILD.gn and grd_files.gni), giving it distinct triggers and minimal overlap with other skills.	5 / 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-model-management/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.