菜单
Browser automation and UI validation via the capture CLI. Interact with pages using accessibility-driven click, type, screenshot, a11y tree, JS exec, and HAR recording over CDP. Use when validating UI state, testing features in the browser, or manipulating a running web app.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
Structure Claude prompts for clarity and better results using roles, explicit instructions, context, positive framing, and strategic organization. Use when crafting prompts for complex tasks, long documents, tool workflows, or code generation.
Pause agent execution to have the human validate decisions, choose between options, answer freetext, or comment on a document — via the `hl` CLI. Every interaction is a kickoff that returns a job handle immediately; collect the human's answer later with `hl job result`. Use for material design decisions, approval gates, picks between meaningful alternatives, and markdown doc review. Not for trivial yes/no confirmations the agent should decide itself.
Validate technical designs against requirements for coverage, feasibility, and architectural soundness. Use after creating a design.
Validate implementation plans against requirements and design. Use after creating a plan to ensure full coverage and no ambiguities.
Validate requirements documents for EARS compliance, completeness, and consistency. Use after creating requirements.
Design CLIs for humans and LLM agents — subcommand shape, output streams, exit codes, JSON modes, TTY-aware color, structured errors, mutation safety. Use when building or refactoring a CLI, adding machine-readable output, writing --help, deciding stdout vs stderr, or making a tool agent-friendly.
基于 SOC 职业分类
| name | capture |
| description | Browser automation and UI validation via the capture CLI. Interact with pages using accessibility-driven click, type, screenshot, a11y tree, JS exec, and HAR recording over CDP. Use when validating UI state, testing features in the browser, or manipulating a running web app. |
| allowed-tools | Bash(capture:*), Read, Glob, Grep |
Browser automation via CDP for UI validation. For the full command reference, see cli-reference.md.
capture session start --url <url> — open a tab and start recordingscreenshot, click, type, a11y, exec, navigatecapture session stop <id> — bundle artifacts; capture session view <id> to inspectSession context auto-fills --target and --har — no manual flag threading needed.
Target selection: If the user hasn't specified which app or browser to target, ask before starting. Don't assume Chrome, a specific port, or a running tab — run capture detect to see what's available and confirm with the user when ambiguous.
When validating a UI feature:
a11y --interactive to understand what's on the pageclick and type using accessible names (not selectors)exec to check DOM or JS state when a11y isn't sufficienthar read to verify network requests if relevant (supports --filter-url, --filter-status, --filter-method, --limit; ID optional in an active session)HAR caveat: the session HAR is populated by the commands that run — most reliably navigate. click/type capture the traffic that fires inside their settle window, but cross-navigation traffic after the frame changes is lossy. For continuous "click around" capture, run capture record --duration N in parallel.
click "Name" over exec with selectors — a11y names are stableclick reports multiple matches, add --role to disambiguatea11y --interactive before interacting to see available elementstype --into "Field Name" clicks the field first, then types — no separate click needed