catalan-adobe/cdp-ext-pilot
Launch Chrome with an unpacked extension and test its UI via CDP. Auto-installs Chrome for Testing if needed. Loads the extension, opens sidepanel/popup/options page, and hands off to cdp-connect for interaction (click, type, screenshot, ax-tree). Handles Chrome 137+ branded build restrictions (Extensions.loadUnpacked via pipe), sidepanel user gesture requirements, and React input quirks. Use when you need to test a Chrome extension's UI, automate extension interactions, or validate extension behavior on a target page. Triggers on: chrome extension test, test extension, load unpacked extension, extension sidepanel, extension popup, test chrome extension, extension testing, chrome extension automation, ext pilot, cdp extension.
100
100%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Advisory
Suggest reviewing before use
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 an excellent skill description that excels across all dimensions. It provides comprehensive technical detail about capabilities, explicitly states when to use it, and includes a thorough list of natural trigger terms. The description is specific enough to avoid conflicts with general browser automation skills while covering the full scope of Chrome extension testing scenarios.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Launch Chrome with an unpacked extension', 'test its UI via CDP', 'Auto-installs Chrome for Testing', 'Loads the extension', 'opens sidepanel/popup/options page', and specific interactions like 'click, type, screenshot, ax-tree'. Also mentions specific technical constraints handled. | 3 / 3 |
Completeness | Clearly answers both what (launch Chrome, load extension, test UI via CDP, handle various technical constraints) AND when with explicit 'Use when...' clause specifying test scenarios, plus a 'Triggers on:' section with specific keywords. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms explicitly listed: 'chrome extension test', 'test extension', 'load unpacked extension', 'extension sidepanel', 'extension popup', 'chrome extension automation'. These match what users would naturally say when needing this functionality. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive niche focused specifically on Chrome extension testing via CDP. The combination of 'unpacked extension', 'CDP', 'sidepanel/popup/options', and Chrome-specific technical details makes it unlikely to conflict with general browser automation or other testing skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
100%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is an excellent skill file that demonstrates strong technical writing. It efficiently covers a complex multi-tool workflow (Chrome extension testing via CDP) with clear phases, executable commands, and practical troubleshooting tips. The composition with cdp-connect is well-signaled, and the tips section addresses real-world edge cases (React inputs, popup context differences) without bloating the main content.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, assuming Claude's competence with CDP, Chrome extensions, and bash scripting. No unnecessary explanations of what extensions are or how CDP works—just actionable commands and essential tips. | 3 / 3 |
Actionability | Provides fully executable bash commands and node invocations with concrete examples. Each phase has copy-paste ready commands with clear parameters and expected outputs (JSON with extensionId, target IDs). | 3 / 3 |
Workflow Clarity | Clear three-phase workflow (Setup → Open UI → Interact) with explicit validation checkpoint ('Verify: Confirm extensionId is non-null') and troubleshooting steps. Cleanup phase is clearly separated with status check before close. | 3 / 3 |
Progressive Disclosure | Well-organized sections with clear hierarchy. References cdp-connect skill appropriately without deep nesting. Tips section consolidates edge cases without cluttering the main workflow. Appropriate length for a skill file. | 3 / 3 |
Total | 12 / 12 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.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
Reviewed
Table of Contents