菜单
Browser automation for c11 browser surfaces (WKWebView-backed). Use to open sites, interact with pages, wait for state changes, extract data, save/load auth state, and validate UI changes without leaving c11. Prefer this over Chrome MCP whenever c11 is running.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
c11 is a native macOS terminal multiplexer. Load this skill anytime any of the following attributes are hit: (1) session is inside c11 (`C11_SHELL_INTEGRATION=1`), (2) working with panes, surfaces, workspaces, splits, or tabs, (3) sending text or commands to another surface, (4) launching or orchestrating sub-agents, (5) declaring agent identity, setting title/description, or reporting sidebar status, (6) using the embedded browser or markdown surfaces, (7) any c11-specific command or troubleshooting question. When in doubt, load it.
Stage 4 of the Tone workflow and Stage 11's build engine — takes a complete build contract (SPEC.md, EVALUATION.md, BUILDPLAN.md, and where one exists a binding prototype + DESIGN.md), turns it into Lattice tickets, dispatches a delegator fleet that produces open PRs, and terminally audits the result against a spec its builders did not write. No planning interview — if contract artifacts are missing, run the Tone stage that produces them (tone-architect for spec/plan, tone-initiation for a raw idea). Invoke when the operator says "orchestrate this," "kick off the orchestration," "run the orchestrator," "set up an overnight run," or hands over a finished build contract.
The idea-generation sequence upstream of the Tone/Chord workflows — the operator brings a direction (a market, a hunch, a theme); Sounding arms it with evidence and explores it in dialogue, producing reads — concrete, carded takes on the direction — each ending in a try/not-try call. Where Tone begins with "a raw idea and a client," Sounding is where raw ideas come from. Invoke on "sounding," "take soundings," "sound this," "let's explore ideas," "what should we build next," or whenever the operator brings a direction that isn't yet an idea. Standalone; "try" reads feed venture-partner and the Tone/Chord commissions; composes with Scanner (/scan) for app-level evidence.
Stage 11's marketing-capability program — a working session that turns marketing intent into budgeted, pre-registered experiments and accumulates the verdicts into a playbook of plays with real numbers. Demand generation is the unsolved half of the autonomous-business loop; Resonance reps it daily the way agentic coding was repped in 2023–24. Invoke on "resonance," "make this resonate," "marketing," "get users for this," "demand probe," "test demand," or whenever marketing needs to produce a verdict, not a vibe. Standalone; its probe instruments serve Sounding "try" reads; its playbook feeds the distribution skill (per-project channel planning), which feeds every channel result back.
Stage 3 of the Chord workflow (chord-initiation → chord-prototype → chord-architect → lattice-orchestrator ×K) — codifies K loved designs into K build contracts under one shared rulebook, authors the pre-registered resolution book, then conducts the ×K build (fresh lattice-orchestrator run per candidate) through to the handoff of K live, instrumented probes. Inherits tone-architect by reference. Invoke when the operator says "chord architect," "codify the portfolio," "spec the candidates," or when a portfolio of loved prototypes needs its build contracts — and stay seated: this skill also owns the conductor's build-and-handoff playbook.
Stage 1 of the Chord workflow (chord-initiation → chord-prototype → chord-architect → lattice-orchestrator ×K) — Tone in plural: the portfolio initiation of one problem with several complete answers. Commission a portfolio, research to enumerate, generate ~N candidate bets, voice K uncorrelated ones with a champion each, and write the two-tier philosophy & stories. Inherits tone-initiation by reference. Invoke when the operator says "chord," "chord this," "portfolio this," "build several answers," or when a keystone fork resists resolution by research and dialogue.
| name | c11-browser |
| version | 1 |
| description | Browser automation for c11 browser surfaces (WKWebView-backed). Use to open sites, interact with pages, wait for state changes, extract data, save/load auth state, and validate UI changes without leaving c11. Prefer this over Chrome MCP whenever c11 is running. |
Use this skill for browser tasks inside c11 webviews. Browser surfaces are a native surface type, scriptable alongside terminals and markdown viewers from the same c11 CLI. Prefer this over Chrome MCP whenever c11 is running: lighter, integrated, no stray Chrome windows.
get url before waiting or snapshotting.--interactive) to get fresh element refs.click, fill, type, select, press).c11 --json browser open https://example.com
# use returned surface ref, for example: surface:7
c11 browser surface:7 get url
c11 browser surface:7 wait --load-state complete --timeout-ms 15000
c11 browser surface:7 snapshot --interactive
c11 browser surface:7 fill e1 "hello"
c11 --json browser surface:7 click e2 --snapshot-after
c11 browser surface:7 snapshot --interactive
# identify current context
c11 identify --json
# open routed to a specific topology target
c11 browser open https://example.com --workspace workspace:2 --window window:1 --json
Notes:
surface:N, pane:N, workspace:N, window:N).--id-format uuids|both).surface:N per task unless you intentionally switch.c11 tree --json and add the tab with c11 new-surface --type browser --url <url> --pane <browser-pane-ref>. Open a new browser pane (c11 new-pane --type browser) only when none exists yet, or when the operator explicitly wants pages side by side. c11 browser open reuses an existing browser surface when one is available.c11 supports wait patterns similar to agent-browser:
c11 browser <surface> wait --selector "#ready" --timeout-ms 10000
c11 browser <surface> wait --text "Success" --timeout-ms 10000
c11 browser <surface> wait --url-contains "/dashboard" --timeout-ms 10000
c11 browser <surface> wait --load-state complete --timeout-ms 15000
c11 browser <surface> wait --function "document.readyState === 'complete'" --timeout-ms 10000
c11 --json browser open https://example.com/signup
c11 browser surface:7 get url
c11 browser surface:7 wait --load-state complete --timeout-ms 15000
c11 browser surface:7 snapshot --interactive
c11 browser surface:7 fill e1 "Jane Doe"
c11 browser surface:7 fill e2 "jane@example.com"
c11 --json browser surface:7 click e3 --snapshot-after
c11 browser surface:7 wait --url-contains "/welcome" --timeout-ms 15000
c11 browser surface:7 snapshot --interactive
c11 browser surface:7 fill e11 "" --snapshot-after --json
c11 browser surface:7 get value e11 --json
# navigate -> verify -> wait -> snapshot -> action -> snapshot
c11 browser surface:7 get url
c11 browser surface:7 wait --load-state complete --timeout-ms 15000
c11 browser surface:7 snapshot --interactive
c11 --json browser surface:7 click e5 --snapshot-after
c11 browser surface:7 snapshot --interactive
If get url is empty or about:blank, navigate first instead of waiting on load state.
| Reference | When to Use |
|---|---|
| references/commands.md | Full browser command mapping and quick syntax |
| references/snapshot-refs.md | Ref lifecycle and stale-ref troubleshooting |
| references/authentication.md | Login/OAuth/2FA patterns and state save/load |
| references/authentication.md#saving-authentication-state | Save authenticated state right after login |
| references/session-management.md | Multi-surface isolation and state persistence patterns |
| references/video-recording.md | Current recording status and practical alternatives |
| references/proxy-support.md | Proxy behavior in WKWebView and workarounds |
| Template | Description |
|---|---|
| templates/form-automation.sh | Snapshot/ref form fill loop |
| templates/authenticated-session.sh | Login once, save/load state |
| templates/capture-workflow.sh | Navigate + capture snapshots/screenshots |
These commands currently return not_supported because they rely on Chrome/CDP-only APIs not exposed by WKWebView:
Use supported high-level commands (click, fill, press, scroll, wait, snapshot) instead.
js_error on snapshot --interactive or evalSome complex pages can reject or break the JavaScript used for rich snapshots and ad-hoc evaluation.
Prefer get text body / get html body for reading page content; reserve eval for interaction and computed checks. eval and snapshot --interactive run injected JavaScript that strict-CSP or framebusting sites (Hacker News is a known case) reject with js_error — even for something as trivial as eval "1+1" — whereas get text/get html read the already-rendered DOM and keep working. Reach for eval when you genuinely need to run script on the page, not as the default way to extract content.
Recovery steps:
c11 browser surface:7 get url
c11 browser surface:7 get text body
c11 browser surface:7 get html body
get url first so you know whether the page actually navigated.get text body or get html body when snapshot --interactive or eval returns js_error.