evaluate-ai-css-completion

Expose a temporary evaluation hook in DevTools and run a Puppeteer script to validate CSS code completion trigger rates.

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/evaluate-ai-css-completion/SKILL.md

Quality

Content

82%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 body is a well-structured, highly actionable five-step workflow with executable code, exact commands, a confirmation checklist, diagnostics, and a revert step. Minor conciseness and workflow-checkpoint integration improvements keep it just below top marks.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with direct commands and code blocks; the only padding is the opening line 'This skill allows you to temporarily expose an evaluation hook…' which restates the description, fitting the 'efficient; minor instances of over-explanation' anchor.	4 / 5
Actionability	Provides a complete, copy-paste-ready TypeScript patch and exact executable commands ('npm start -- --no-watch …', 'autoninja -C out/Default', 'node …/evaluate.js', 'git checkout …'), matching the 'fully executable; copy-paste ready' anchor.	5 / 5
Workflow Clarity	Five steps are clearly sequenced with a user-confirmation checklist, a diagnostics feedback loop for 0% trigger rates, and an explicit revert step; validation is present so the destructive-operation cap does not apply, but checkpoints between steps could be more tightly integrated, fitting 4 over 5.	4 / 5
Progressive Disclosure	Content is organized into clear step sections with a real one-level-deep reference to scripts/evaluate.js (verified to exist); the large inlined patch is justified because it must be pasted into a specific source file, fitting 'good structure; most content appropriately placed'.	4 / 5
	Total	17 / 20 Passed

Description

58%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, naming concrete actions and a unique niche. Its main weakness is the missing 'when to use' trigger guidance, which caps completeness, and limited natural-language keyword variations.

Suggestions

Add an explicit 'Use when…' clause (e.g., 'Use when measuring or debugging CSS code completion trigger rates in local DevTools builds') to lift completeness above 3.

Include more natural trigger phrases and synonyms a user might say, such as 'CSS autocomplete', 'AI CSS suggestions', or 'completion rate', to improve trigger term coverage.

Consider mentioning the measurable outcome ('report trigger-rate results') to round out the action list toward comprehensive coverage.

Dimension	Reasoning	Score
Specificity	Names three concrete actions — 'Expose a temporary evaluation hook in DevTools', 'run a Puppeteer script', 'validate CSS code completion trigger rates' — with only minor coverage gaps, matching the 'several specific actions' anchor rather than the fully comprehensive 5.	4 / 5
Completeness	The 'what' is clear but there is no 'Use when…' clause or equivalent explicit trigger guidance, so per the judging guidelines completeness is capped at 3.	3 / 5
Trigger Term Quality	Relevant keywords exist ('DevTools', 'Puppeteer script', 'CSS code completion') but natural synonyms and variations a user might say are missing, fitting the 'some relevant keywords but missing common variations' anchor.	3 / 5
Distinctiveness Conflict Risk	The combination of DevTools evaluation hook + Puppeteer + CSS completion trigger rates is a distinct niche with minimal overlap risk, fitting 'mostly distinct; minor overlap risk' rather than the maximally distinct 5.	4 / 5
	Total	14 / 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/evaluate-ai-css-completion/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.