merging-devtools-module

Workflow for merging a DevTools submodule into its parent module. Covers BUILD.gn consolidation and updating devtools_grd_files.gni.

Quality

70%

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/merging-devtools-module/SKILL.md

Quality

Content

72%

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 well-organized, mostly actionable single-file workflow with strong before/after examples, weakened by the absence of any build verification step after destructive config changes and a slightly verbose barrel-file section.

Suggestions

Add an explicit validation step after the destructive edits, e.g. run `gn gen out/Default && autoninja -C out/Default` (or the project's build command) and only proceed when the build passes.

Tighten the 'Removing Barrel Files' section: replace 'Follow the instructions in the repository' with the concrete install/run commands for unbarrelify, or move it to a short reference.

Add a brief verification note for the devtools_grd_files.gni edit (e.g. confirm the removed bundled source no longer appears and the unbundled .ts paths resolve).

Dimension	Reasoning	Score
Conciseness	The core workflow is lean and assumes Claude's knowledge of DevTools/GN, but the 'Removing Barrel Files' section is padded with explanatory prose and hand-wavy guidance ('Follow the instructions in the repository') that could be tightened.	2 / 3
Actionability	The main workflow provides executable commands (`rm <child_module_path>/BUILD.gn`), specific file paths, and concrete before/after BUILD.gn and .gni diffs that are effectively copy-paste ready, despite the weaker unbarrelify pointer.	3 / 3
Workflow Clarity	Steps are clearly numbered and sequenced, but the workflow involves destructive operations (deleting BUILD.gn, removing bundled sources) with no build/compile validation checkpoint, which caps workflow clarity at 2 per the rubric.	2 / 3
Progressive Disclosure	No bundle files exist and the skill is a self-contained single-file workflow with well-organized sections (Prerequisites, Workflow Steps, Example, Removing Barrel Files) and only a clearly-signaled one-level external pointer, so it is appropriately structured.	3 / 3
	Total	10 / 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 well-scoped to a clear DevTools build niche, but it omits any explicit 'Use when...' trigger guidance and its keywords are somewhat technical rather than naturally user-spoken.

Suggestions

Add an explicit 'Use when...' clause, e.g. 'Use when merging a DevTools submodule into its parent module or when consolidating BUILD.gn files.'

Include a few natural-language trigger terms users would actually say (e.g. 'merge DevTools module', 'consolidate BUILD.gn') alongside the technical file names.

Dimension	Reasoning	Score
Specificity	Names the concrete domain and two specific artifacts/operations — 'BUILD.gn consolidation and updating devtools_grd_files.gni' — which qualifies as multiple specific concrete actions rather than vague abstraction.	3 / 3
Completeness	It clearly answers 'what' (merge submodule, consolidate BUILD.gn, update .gni) but provides no 'Use when...' trigger guidance, which caps completeness at 2 per the rubric.	2 / 3
Trigger Term Quality	It has relevant domain terms ('merge a DevTools submodule into its parent', 'BUILD.gn', 'devtools_grd_files.gni') but these lean toward technical jargon and lack common natural-language variations a user might say.	2 / 3
Distinctiveness Conflict Risk	The niche is highly specific (DevTools submodule merging, BUILD.gn, devtools_grd_files.gni) and unlikely to trigger for any other skill, so it does not overlap with similar 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/merging-devtools-module/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.