devtools-model-management

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

Quality

78%

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

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 lean, highly actionable, well-sequenced guide with explicit verification checkpoints and self-contained organization that needs no external references.

Dimension	Reasoning	Score
Conciseness	Lean bullet-point structure with no padding or explanation of concepts Claude already knows; every line (commands, callouts, paths) earns its place.	3 / 3
Actionability	Provides concrete executable commands (npm run test, autoninja -C out/Default, npm run lint) and copy-paste-ready BUILD.gn/import snippets with justified <model_name> placeholders.	3 / 3
Workflow Clarity	Clear numbered sequence (Preparation through Verification) with an explicit baseline checkpoint in §0 and a build/lint/test verification checklist in §5; the Common Pitfalls section maps errors to fixes as a feedback aid.	3 / 3
Progressive Disclosure	Self-contained single document with no bundle files, no nested references, and well-organized sections; meets the rubric's allowance for skills with no need for external references.	3 / 3
	Total	12 / 12 Passed

Description

57%

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 concise, third-person, and distinctively scoped to a specific DevTools workflow, but it states only the what and omits any explicit when/trigger guidance while leaning on technical jargon over natural user terms.

Suggestions

Add an explicit trigger clause, e.g. 'Use when creating, migrating, or registering a model under front_end/models/ in DevTools.'

Soften jargon with natural phrasing a contributor would say, e.g. 'DevTools model', 'add a new model', 'move a model to front_end/models'.

Consider stating a concrete outcome or two (e.g. 'sets up BUILD.gn targets and grd registration') to lift specificity from process-level to operation-level.

Dimension	Reasoning	Score
Specificity	Names the domain and three actions ("creating, migrating, and registering models") plus concrete artifacts ("BUILD.gn, devtools_grd_files.gni, and entrypoints"), but the actions are process-level rather than the granular concrete operations of the anchor-3 example.	2 / 3
Completeness	Clearly answers what ("Guidelines for creating, migrating, and registering models") but provides no "Use when..." or equivalent explicit trigger guidance, capping completeness at 2 per the rubric guideline.	2 / 3
Trigger Term Quality	Contains relevant domain terms a contributor would say ("models", "front_end/models/", create/migrate/register) but leans on technical jargon (BUILD.gn, devtools_grd_files.gni) and misses common natural variations.	2 / 3
Distinctiveness Conflict Risk	The narrow DevTools-specific niche ("front_end/models/", "BUILD.gn", "devtools_grd_files.gni") makes it clearly distinguishable and unlikely to trigger for the wrong skill.	3 / 3
	Total	9 / 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-model-management/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.