CtrlK
BlogDocsLog inGet started
Tessl Logo

devtools-setting-migration

Workflow for splitting an existing SettingRegistration into a SettingDescriptor (placed in the lowest layer where used: core/, models/, or ui/settings/) and SettingUIDescriptor (registered in a higher-level -meta.ts file, outside of core/ and models/).

57

Quality

65%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/devtools-setting-migration/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

73%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 highly actionable with executable examples and a clear migration workflow, supported by well-organized sections; it is somewhat verbose due to repeated critical-rule emphasis and lacks per-step validation feedback loops.

Suggestions

Consolidate the 'CRITICAL RULE' prohibitions stated in both Key Principles and Step 1 to reduce repetition and save tokens.

Add an explicit validation checkpoint earlier in the workflow (e.g. verify the descriptor resolves and imports compile) rather than only a final build/lint/test step.

Consider moving the full Interface Reference Summary into a separate reference file once the skill grows, keeping SKILL.md as an overview.

DimensionReasoningScore

Conciseness

The body is mostly efficient and well-structured, but it is fairly long with some repetitive emphasis (e.g. 'CRITICAL RULE' blocks restated in both principles and steps) that could be tightened without losing clarity.

3 / 5

Actionability

Provides copy-paste-ready TypeScript code for descriptor definition, UI registration, and call-site updates, with concrete before/after examples covering the common core and panel cases.

5 / 5

Workflow Clarity

A clear six-step sequence with explicit file-location rules and a final verification step (autoninja, lint, tests), but verification is listed only at the end rather than as explicit per-step validation checkpoints with feedback loops.

4 / 5

Progressive Disclosure

Good structure with logical sections (principles, step-by-step, examples, interface reference) and no nested references; there are no bundle files so content is self-contained, though the interface reference summary could be split out at scale.

4 / 5

Total

16

/

20

Passed

Description

56%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 delineates a distinct DevTools migration task, but it omits any explicit 'when to use' trigger guidance and relies on internal jargon rather than natural user-facing trigger terms.

Suggestions

Add an explicit 'Use when...' clause, e.g. 'Use when migrating a legacy SettingRegistration in DevTools or when refactoring DevTools settings registration.'

Include more natural trigger terms a user might say (e.g. 'DevTools setting', 'settings registration', 'meta file refactor') alongside the internal type names.

Broaden the action list slightly to cover the full workflow (locate registration, define descriptor, move UI registration, update call sites) for more comprehensive capability coverage.

DimensionReasoningScore

Specificity

Names the domain and several concrete actions ('splitting', 'placed in the lowest layer', 'registered in a higher-level -meta.ts file'), though the action set is narrow (split/place/register) rather than a broad list of capabilities.

4 / 5

Completeness

It clearly states what the skill does (split a SettingRegistration into descriptor types) but provides no 'Use when...' clause or equivalent trigger guidance, capping completeness at 3 per the rubric.

3 / 5

Trigger Term Quality

Contains domain terms ('SettingRegistration', 'SettingDescriptor', 'SettingUIDescriptor', '-meta.ts', 'core/', 'models/', 'ui/settings/') but these are internal technical jargon; natural user-facing trigger phrases a user would actually say are missing.

3 / 5

Distinctiveness Conflict Risk

The very specific DevTools setting-migration niche with named file types and layer boundaries makes it clearly distinct from other skills, with only minor overlap risk against general DevTools refactoring skills.

4 / 5

Total

14

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
ChromeDevTools/devtools-frontend
Reviewed

Table of Contents

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.