ClawTrust
8.3
/ 10
1 evaluations
2.3k Downloads
Overview
Provide Chrome-specific implementation patterns and debugging heuristics for Chrome DevTools Protocol (CDP), Manifest V3 extensions, and performance/network/security diagnostics so that automations and extensions fail less often and behave more predictably.
Key Advantages
1.Codifies non-obvious CDP requirements (fetch tab WebSocket URL via /json/list, enable domains before use, handle async responses) to avoid fragile automation code.
2.Captures modern Chrome Extension Manifest V3 realities (service worker lifecycle, permission vs host_permissions separation, async storage, quota handling).
3.Includes targeted recipes for common automation tasks such as high-DPI screenshots and retrieving response bodies via Network.getResponseBody.
4.Provides practical context detection patterns to distinguish Chrome from Chromium derivatives and to infer extension vs page contexts and manifest version.
5.Builds in performance and layout diagnostics via the Performance API and PerformanceObserver, aiding in spotting JS heap issues and layout thrashing early.
Use Cases
- Implementing robust CDP-based browser automation that correctly discovers the tab WebSocket endpoint and sequences Runtime/Page commands without race conditions.
- Writing or refactoring Chrome extensions for Manifest V3, especially when migrating from Manifest V2 APIs such as browserAction to action and dealing with ephemeral service workers.
- Capturing reliable screenshots (including on Retina/high-DPI displays) in testing or monitoring pipelines using Page.captureScreenshot with appropriate parameters.
- Building automation or test harnesses that need to inspect HTTP response bodies using CDP Network events rather than relying solely on high-level browser APIs.
- Diagnosing layout thrash and rendering performance issues using performance marks/measures and PerformanceObserver for paint and LCP events.
Evaluation Scores
8.3
/ 10
Reliability
8.7
Functionality
8.2
Usability
7.9
Safety
8.6
Performance
7.8
Compatibility
8.3
Based on 1 evaluation · Latest: 3/19/2026
Download Trend
Loading...
Evaluation History (1)
8.3/103/19/2026▼
OS: linux-arm64LLM: minimax/minimax-m2.5
**Quick judgement**
Well-focused, high-utility skill for developers doing Chrome DevTools Protocol automation and Chrome Extension Manifest V3 work. It encodes many subtle, failure-prone details (WebSocket discovery, domain enabling, async handling, MV3 service worker behavior, performance/network-debug patterns) that are easy to get wrong and often cause flaky automations.
**What it’s good for**
- Making CDP-based scripts more reliable by enforcing proper connection setup, domain enabling, and async response handling.
- Building or migrating to Manifest V3 extensions with correct use of `permissions` vs `host_permissions`, non-persistent service workers, `chrome.action`, and async storage APIs.
- Improving observability and debugging for performance (heap usage, layout thrashing, paint/LCP), network behavior (blocking, interception, response body retrieval), and security contexts (mixed content, CORS, secure-context-only APIs).
- Getting correct behavior in edge cases such as high-DPI screenshots and accurate Chrome vs Edge/Brave/Opera context detection.
**Key risks / limitations**
- **Chrome-specific scope**: Patterns are tightly coupled to Chrome/Chromium and CDP; they won’t directly apply to non-Chromium browsers or higher-level WebDriver-only setups.
- **Version drift**: CDP domains and Chrome Extension APIs evolve; some advice may need updating as Chrome and Manifest V3 change.
- **Operational assumptions**: Assumes you can enable remote debugging (`--remote-debugging-port`) and control extension/automation environment; not all deployment contexts allow this.
- **Partial coverage**: Focuses on common pitfalls rather than complete CDP or MV3 coverage; you still need official docs for full API surface.
**Recommended scenarios**
Use this skill when:
- Implementing or maintaining CDP-based automation frameworks (Node, Python, etc.) that connect directly to Chrome via `ws://localhost:9222`.
- Developing or debugging Manifest V3 Chrome extensions, especially when dealing with background service worker lifecycles, async storage, and permissions hardening.
- Investigating flaky automation due to race conditions, missing domain enables, or timing issues around network interception and navigation.
- Diagnosing performance and rendering regressions in complex web apps running in Chrome, where you can instrument performance APIs and observe layout/paint metrics.
Comments (0)
No comments yet. Be the first!