Skip to main content
hc
Submit
skillsSource-backedReview first Safety ✓ Privacy ✓

Claude Code Chrome Browser QA Capability Pack Skill

Expert Claude Code Chrome browser QA capability pack applying documented Claude in Chrome enablement, browser automation boundaries, and web QA checkpoint workflows.

by kiannidev·added 2026-06-16·
Claude CodeCodexWindsurfGeminiCursorCLI
HarnessClaude CodeCodexWindsurfGeminiCursorCLI
Level:expertType:capability-packVerified:validated
Review first — review before installing

Open the source and read safety notes before installing.

Safety notes

  • Browser automation can access logged-in sessions—use staging accounts only.
  • Claude chooses Chrome before computer use for web tasks when configured.
  • Review permission prompts before approving navigation on sensitive pages.

Privacy notes

  • Browser QA sends page content to the model—avoid customer PII in test flows.
  • Screenshots and DOM snapshots may include session tokens in dev tools—close extras.

Prerequisites

  • Claude in Chrome extension installed per official Chrome documentation.
  • Staging web app URL and test credentials scoped to non-production.
  • Team policy for browser automation on authenticated sessions.

Schema details

Install type
package
Reading time
8 min
Difficulty score
72
Troubleshooting
Yes
Breaking changes
No
Source repository stats
Scope
Source repo
Package metadata
Skill and platform metadata
Skill type
capability-pack
Skill level
expert
Verification
validated
Verified at
2026-06-16
Retrieval sources
https://code.claude.com/docs/en/chromehttps://code.claude.com/docs/en/skillshttps://code.claude.com/docs/en/securityhttps://github.com/anthropics/claude-codehttps://developers.google.com/search/docs/fundamentals/creating-helpful-content
Tested platforms
Claude CodeClaudeCursorGeneric AGENTS
PlatformSupportInstall path
claude-codeNative.claude/skills/<skill-name>/SKILL.md
codexNative.agents/skills/<skill-name>/SKILL.md
windsurfNative.windsurf/skills/<skill-name>/SKILL.md
geminiNative.gemini/skills/<skill-name>/SKILL.md or .agents/skills/<skill-name>/SKILL.md
cursorAdapter.cursor/rules/<skill-name>.mdc
cliManualAGENTS.md or tool-specific context file
Full copyable content
# Trigger
"Apply the Claude Code Chrome browser QA capability pack for this web flow."

# Required output
1) Chrome integration enablement checklist
2) QA flow steps with URL checkpoints
3) Browser permission and data exposure review
4) Defect observations with evidence
5) Privacy-safe QA summary

About this resource

Knowledge Freshness

Grounded in Claude in Chrome documentation verified on 2026-06-16.

Retrieval Sources

Source Verification Notes

Official Chrome docs describe Claude in Chrome for browser-based tasks, extension setup, and choosing browser automation before broader computer use for web work.

Scope Note

Community QA workflow skill applying documented Chrome integration steps—not an official Anthropic test product.

Core Workflow

  1. Verify extension install and account linkage.
  2. Define QA flow with URL and assertion checkpoints.
  3. Run staging-only tests with scoped credentials.
  4. Capture defect notes with page references—not production data.
  5. Stop and escalate if unexpected auth or payment pages appear.

Capability Scope

  • Chrome extension enablement verification.
  • Web QA flow checkpoint design.
  • Browser permission and session exposure review.
  • Defect observation with page-level evidence.
  • Privacy-safe QA reporting.

Production Rules

  • Use staging credentials only; never production admin accounts.
  • Stop browser QA when payment or SSO pages appear unexpectedly.
  • Do not store session cookies in skill output or public tickets.
  • Prefer Claude in Chrome over computer use for standard web flows per docs.
  • Human sign-off required before filing external bug reports with screenshots.

Review Matrix

Flow Checkpoint Stop condition
Login Staging auth only Production SSO prompt
Checkout Cart total visible Real payment form
Form validation Error messages PII in error text

Output Contract

  1. Enablement checklist.
  2. Flow steps and checkpoints.
  3. Permission review.
  4. Defect observations.
  5. Privacy-safe summary.

Duplicate Check

Distinct from chrome-integration-for-web-app-debugging-with-claude-code guide.

Troubleshooting

Issue: Extension not controlling tab Fix: Re-link extension; confirm staging URL allowlist in team policy.

Editorial Disclosure

Independent entry by kiannidev from public docs.

#claude-code#chrome#browser-qa#web#capability-pack

Source citations

Add this badge to your README

Show that Claude Code Chrome Browser QA Capability Pack Skill is listed on HeyClaude. Paste this Markdown into your README — it renders the badge and links back to this page.

Listed on HeyClaude
[![Listed on HeyClaude](https://heyclau.de/badge/skills/claude-code-chrome-browser-qa-capability-pack.svg)](https://heyclau.de/entry/skills/claude-code-chrome-browser-qa-capability-pack)

How it compares

Claude Code Chrome Browser QA Capability Pack Skill side by side with 3 alternatives on trust, install, platform support, and disclosed safety notes — all from reviewed registry metadata.

FieldClaude Code Chrome Browser QA Capability Pack Skill

Expert Claude Code Chrome browser QA capability pack applying documented Claude in Chrome enablement, browser automation boundaries, and web QA checkpoint workflows.

Open dossier 		Claude Agent SDK Session Storage Capability Pack Skill

Expert Claude Agent SDK session storage capability pack for designing, reviewing, and rolling out Agent SDK session storage with source-backed checklists, production rules, and privacy-safe output contracts.

Open dossier 		Claude Code Computer Use GUI QA Capability Pack Skill

Expert Claude Code computer use GUI QA capability pack that applies documented computer-use MCP enablement, per-app session approval, screenshot checkpoints, and macOS permission workflows for native app validation—not an official Anthropic QA product.

Open dossier 		Claude Code Web Remote Environment Capability Pack Skill

Expert Claude Code web remote environment capability pack applying documented cloud session isolation, network controls, and credential proxy patterns from official Claude Code on the web documentation.

Open dossier
Trust
Install riskReview firstReview firstReview firstReview first
Notes Safety ✓ Privacy ✓ Safety ✓ Privacy ✓ Safety ✓ Privacy ✓ Safety ✓ Privacy ✓
Categoryskillsskillsskillsskills
Sourcesource-backedsource-backedsource-backedsource-backed
Authorkiannidevkiannidevkiannidevkiannidev
Added2026-06-162026-06-142026-06-162026-06-16
Platforms
Claude CodeCodexWindsurfGeminiCursorCLI
Claude CodeCodexWindsurfGeminiCursorCLI
Claude CodeCodexWindsurfGeminiCursorCLI
Claude CodeCodexWindsurfGeminiCursorCLI
Source repo————
Safety notes✓Browser automation can access logged-in sessions—use staging accounts only. Claude chooses Chrome before computer use for web tasks when configured. Review permission prompts before approving navigation on sensitive pages.✓This skill plans Agent SDK session storage; it must not execute destructive changes without explicit approval. Browser, computer-use, and remote surfaces can access sensitive UI state; scope tests carefully. MCP and SDK integrations may exfiltrate data if tool scopes are too broad. The public `anthropics/claude-code` repository ships documentation links to code.claude.com for settings, security, and integration surfaces. Scheduled or autonomous workflows compound risk; cap blast radius in staging first.✓Computer use controls real desktop apps with per-app session approval—not sandboxed Bash. Review sentinel warnings before approving Terminal, Finder, or System Settings access. Press Esc or Ctrl+C to stop computer use and release the machine-wide lock immediately. Only one Claude Code session can hold the computer-use lock at a time.✓Autonomous workflows can run shell commands without mid-run user input—scope paths and tools first. Do not enable destructive automation without explicit approval gates. Review outputs as draft until a human validates evidence.
Privacy notes✓Browser QA sends page content to the model—avoid customer PII in test flows. Screenshots and DOM snapshots may include session tokens in dev tools—close extras.✓Reviews may expose integration tokens, customer metadata, and internal URLs related to Agent SDK session storage. Telemetry and analytics configs can include account emails; redact before sharing externally. Keep troubleshooting logs in internal channels unless explicitly sanitized. Third-party vendors remain outside Anthropic retention policies; document separately.✓Screenshots are downscaled before model upload but may still capture sensitive UI content. Your terminal window is excluded from screenshots per official documentation. Redact customer or proprietary UI details before sharing screenshot evidence externally. Other visible apps are hidden while Claude works; still minimize sensitive windows before starting.✓Workflow and session output may contain proprietary code and credentials. Summaries for external channels require redaction.
Prerequisites
  • Claude in Chrome extension installed per official Chrome documentation.
  • Staging web app URL and test credentials scoped to non-production.
  • Team policy for browser automation on authenticated sessions.
  • Access to Claude Code or Agent SDK environment where Agent SDK session storage will run.
  • Ability to read project, user, and managed settings relevant to the workflow.
  • Staging repository or sandbox account for safe validation.
  • Platform or security stakeholder available for policy-bound rollouts.
  • Interactive Claude Code session on macOS v2.1.85+ with Pro or Max plan per computer-use docs.
  • computer-use MCP server enabled through /mcp for the project.
  • macOS Accessibility and Screen Recording permissions granted when prompted.
  • Disposable QA target app or simulator without live customer data on screen.
  • Claude Code version and plan eligibility per official documentation.
  • Team policy for autonomous or scheduled workflows.
  • Staging environment for safe validation.
  • Human owner for production rollout approval.
Install————
Config————
Citations
ClaimUnclaimedUnclaimedUnclaimedUnclaimed

Signals

Loading live community signals…

More like this, weekly

A short, calm digest of reviewed Claude resources. Unsubscribe any time.