control-ui

Build or adapt a local browser/CDP harness to drive and inspect a web, IDE, or Electron UI. Use for local UI verification, screenshots, accessibility snapshots, perf profiles, visual diffs, or reproducing UI bugs.

Quality

88%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Discovery

100%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

This is a strong skill description that clearly communicates both what the skill does and when to use it. It lists specific, concrete capabilities and includes natural trigger terms that developers would use. The CDP/browser harness focus gives it a distinct niche that minimizes conflict with other skills.

Dimension	Reasoning	Score
Specificity	Lists multiple specific concrete actions: 'build or adapt a local browser/CDP harness', 'drive and inspect a web, IDE, or Electron UI', 'screenshots', 'accessibility snapshots', 'perf profiles', 'visual diffs', 'reproducing UI bugs'. These are concrete, actionable capabilities.	3 / 3
Completeness	Clearly answers both what ('Build or adapt a local browser/CDP harness to drive and inspect a web, IDE, or Electron UI') and when ('Use for local UI verification, screenshots, accessibility snapshots, perf profiles, visual diffs, or reproducing UI bugs'). The 'Use for' clause serves as an explicit trigger guidance.	3 / 3
Trigger Term Quality	Includes strong natural keywords users would say: 'browser', 'CDP', 'screenshots', 'accessibility snapshots', 'visual diffs', 'UI bugs', 'Electron', 'perf profiles', 'UI verification'. Good coverage of terms a developer would naturally use when needing this skill.	3 / 3
Distinctiveness Conflict Risk	Highly distinctive niche: local browser/CDP harness for UI inspection. The combination of CDP, browser automation, Electron, accessibility snapshots, and visual diffs creates a clear, specific domain unlikely to conflict with general testing or web development skills.	3 / 3
	Total	12 / 12 Passed

Implementation

77%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This is a solid, actionable skill with executable code examples and clear workflow sequencing. Its main strengths are the concrete Playwright harness examples and the well-structured interaction loop with validation checkpoints. Minor weaknesses include some unnecessary explanatory text and the lack of progressive disclosure to supporting files, though the content length is reasonable for a standalone skill.

Suggestions

Trim the 'What It Is Used For' section or merge it into a single-line description, as the frontmatter description already covers the purpose.

Consider extracting the CDP Capabilities bullet list and the detailed CDP harness example into a separate reference file to improve progressive disclosure.

Dimension	Reasoning	Score
Conciseness	The skill is mostly efficient but includes some sections that could be tightened. The 'What It Is Used For' section is somewhat redundant given the description, and some explanatory text (e.g., 'Use raw CDP only when higher-level browser APIs are insufficient') states things Claude would already know. However, the code examples and guardrails are lean.	2 / 3
Actionability	Provides fully executable JavaScript code examples for both web and CDP harnesses, with concrete Playwright API calls, specific selectors (getByRole), and clear placeholder conventions (<port>, <app-root-selector>). The interaction loop and setup pattern give specific, concrete steps.	3 / 3
Workflow Clarity	The Interaction Loop provides a clear 6-step sequence with explicit validation checkpoints (capture before, act, capture after, verify state change). The Setup Pattern is well-sequenced. The page selection section includes error recovery (list available pages instead of guessing). The guardrails section adds important safety validation steps.	3 / 3
Progressive Disclosure	The content is well-organized with clear section headers and logical grouping, but it's all inline in a single file with no references to supporting files. The CDP Capabilities section is a bullet list that could be split out, and the document is moderately long. However, with no bundle files provided, there's limited opportunity for external references.	2 / 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 — 11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository: cursor/plugins
Commit: b8f2564

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.