Skip to main content

Use My Browser

Skill Verified Active

Use when work depends on the user's live browser session or visible rendered state rather than static fetches, especially for browser debugging contexts or DevTools-selected elements or requests, logged-in dashboards or CMS flows, localhost apps, forms, uploads, downloads, media inspection, DOM or iframe inspection, Shadow DOM, or browser failures that look like soft 404s, auth walls, anti-bot checks, or rate limits.

Purpose

To enable agents to gather evidence from live browser sessions, especially for authenticated dashboards, localhost apps, or when rendered state and interaction are crucial, going beyond static fetches.

Features

  • Goal-first routing: static vs. browser-required classification
  • Live-session browser work, including session reuse
  • DevTools context handoff from selected elements/requests
  • Control-plane safety with enhanced confirmation discipline
  • Deep DOM, media inspection, and selector bridging

Use Cases

  • Debugging authenticated dashboards or CMS flows
  • Interacting with localhost applications or local fixtures
  • Inspecting rendered UI, lazy-loaded content, or Shadow DOM
  • Leveraging active DevTools debugging contexts for analysis

Non-Goals

  • Acting as a generic default for all web fetching
  • Replacing static retrieval when it is sufficient
  • Performing brute-force retries on anti-automation measures
  • Silently downgrading browser-required tasks to static paths

Workflow

  1. Classify task as static-capable or browser-required.
  2. If browser-required, prove live browser capability.
  3. Execute base page-action protocol or specialized reference (e.g., debug-handoff, deep-dom).
  4. Apply control-plane safety or anti-automation friction protocols as needed.
  5. Review run for reusable site knowledge and update/create site-pattern notes.
  6. Clean up task-owned pages before exiting.

Prerequisites

  • Live browser session (e.g., Chrome >=144)
  • Remote debugging enabled in Chrome (`chrome://inspect/#remote-debugging`)
  • Chrome DevTools MCP server configured and running (e.g., with `--autoConnect`)

Installation

npx skills add xixu-me/skills

Runs the Vercel skills CLI (skills.sh) via npx — needs Node.js locally and at least one installed skills-compatible agent (Claude Code, Cursor, Codex, …). Assumes the repo follows the agentskills.io format.

Quality Score

Verified
100 /100
Analyzed about 24 hours ago

Trust Signals

Last commitabout 1 month ago
Stars52
LicenseMIT
Status
View Source

© 2025 SkillRepo · Find the right skill, skip the noise.