devtools-model-management

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

Quality

80%

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

90%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 lean, highly actionable procedural guide with a clear sequenced workflow and verification steps; its main gaps are missing explicit error-recovery loops and minor room for file splitting.

Suggestions

Add an explicit feedback loop in the verification section (e.g., 'If autoninja or tests fail, fix and re-run before proceeding').

Consider moving full BUILD.gn target templates into a reference file to tighten the main body further.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Claude's competence — it never explains what DevTools, BUILD.gn, or barrel files are, and every line is actionable, matching the 5 anchor.	5 / 5
Actionability	Provides copy-paste-ready commands ('npm run test -- front_end/<old_location>', 'autoninja -C out/Default', 'npm run lint'), exact import paths, and concrete BUILD.gn target structures, fully executable across the common cases.	5 / 5
Workflow Clarity	A clear numbered sequence (Preparation → Structure → Build → Registration → Refactoring → Verification) with a verification checklist and regression checks; not a 5 because explicit 'if it fails, fix and re-run' feedback loops are only implied rather than stated.	4 / 5
Progressive Disclosure	Well-organized into clearly headed sections with a self-contained procedure that needs no external references; not a 5 because the body is slightly over the ~50-line simple-skill threshold and a couple of sections (e.g., full BUILD.gn templates) could be split out.	4 / 5
	Total	18 / 20 Passed

Description

70%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 highly distinct, naming concrete actions and config files, but it lacks an explicit 'Use when...' trigger clause, which caps its completeness.

Suggestions

Add an explicit 'Use when...' clause stating when Claude should invoke this skill (e.g., 'Use when creating or migrating a model into front_end/models/').

Expand the action list slightly to move specificity toward comprehensive coverage.

Dimension	Reasoning	Score
Specificity	Names the domain ('creating, migrating, and registering models') and concrete artifacts ('BUILD.gn, devtools_grd_files.gni, and entrypoints') — several specific actions with minor coverage gaps, matching the 4 anchor; not a 5 since it stops short of enumerating the full set of actions.	4 / 5
Completeness	The 'what' is clear ('Guidelines for creating, migrating, and registering models...') but there is no 'Use when...' clause or equivalent explicit trigger guidance, which caps completeness at 3 per the judging guidelines.	3 / 5
Trigger Term Quality	Includes natural contributor phrasing ('creating, migrating, registering models') plus specific filenames ('BUILD.gn', 'devtools_grd_files.gni', 'entrypoints'); good keyword coverage but missing a few common variations, so 4 rather than 5.	4 / 5
Distinctiveness Conflict Risk	Targets a highly specific niche (DevTools model management with named config files) with distinct triggers and minimal conflict risk, matching the 5 anchor.	5 / 5
	Total	16 / 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: 961c606

Reviewed: 2 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.