Loading...
Loading...
Found 96 Skills
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.
mParticle platform help — hybrid CDP with real-time event streaming, identity resolution, audience activation, 300+ integrations. Use when mParticle SDK not sending events, identity resolution merging wrong profiles, audience not syncing to destination, connection setup taking too long, Events API returning errors, data plan validation failing, or comparing mParticle pricing tiers. Do NOT use for choosing between CDPs (use /sales-cdp) or CRM data cleanup (use /sales-data-hygiene).
Use when an agent needs to operate the user's real Chrome session — listing tabs, reading the page, clicking, filling, typing into rich editors, pressing keys, evaluating JS, capturing screenshots, and reading console/network buffers. All actions go through CDP and run on backgrounded tabs without stealing focus.
Daytona development environment overview. Use when the user asks about Daytona setup, Daytona toolbox, dev environment, noVNC, CDP, server sandbox, secrets volume, Electron sandbox, standalone Chrome, validation, or artifacts volume.
Connect Claude Code to an existing Chrome browser via CDP (Chrome DevTools Protocol). Zero dependencies — uses Node 22 built-in WebSocket. Attach to any Chrome running with --remote-debugging-port, then navigate, click, type, screenshot, evaluate JS, read accessibility tree, and monitor console/network. Use when you need to interact with a browser the agent already started, control an existing Chrome instance, or drive browser automation without Playwright MCP. Triggers on: cdp connect, connect to browser, connect to chrome, attach to browser, interact with browser, drive browser, browser automation, control chrome, connect 9222.
Compose and post to X.com using Chrome CDP automation. Use when user asks to "post to X", "tweet", "draft a tweet", "share on X", or "write a thread". Handles Chrome launch, text input with emoji/unicode support, and multi-paragraph formatting via real browser automation (no API costs, bypasses anti-bot detection).
Deploys smart contracts to Base using Foundry. Covers forge create commands, contract verification, testnet faucet setup via CDP, and BaseScan API key configuration. Use when deploying Solidity contracts to Base Mainnet or Sepolia testnet. Covers phrases like "deploy contract to Base", "forge create on Base", "verify contract on BaseScan", "get testnet ETH", "Base Sepolia faucet", "how do I deploy to Base", or "publish my contract".
Treasure Data platform help — enterprise AI-native CDP with profile unification, audience segmentation, journey orchestration, 400+ connectors, AI Marketing Cloud suites. Use when setting up Treasure Data CDP, unifying customer profiles across channels, building audience segments in Treasure Data, activating audiences to ad platforms or CRMs, configuring Treasure Data connectors or integrations, writing SQL queries in Treasure Data, troubleshooting Treasure Data workflows or jobs, or working with the TD API. Do NOT use for general CRM data quality without Treasure Data context — use /sales-data-hygiene instead.
Build local constrained-browser agents with a safe_browser tool that owns CDP, enforces a domain allowlist with Fetch interception, and lets a runtime Claude Agent SDK agent complete browsing tasks without raw browser, shell, or CDP access. Use when the user wants an agent to browse or scrape while staying on approved domains, demo blocked off-domain navigation, or generate a safe browser client.
macOS automation skill for AppleScript actions and Chrome browser control via MCP CDP tools.
Drive the real Chrome on Iliyas's Windows PC over CDP — the same browser he uses himself, signed in to his accounts (Vercel, Google Cloud, Heroku, and others). Use it to fetch data that sits behind his logins, open and debug a page live, watch a flow together, intercept requests, or set the browser's proxy / exit country. Use it only when Iliyas explicitly asks for his real / host / Windows browser — everything it does is visible on his screen.
Direct browser control via CDP. Use when the user wants to automate, scrape, test, or interact with web pages. Connects to the user's already-running Chrome.