Menu
Control the user's real browser (Quicker Connector) via user_browser / qkrpc_chrome_control RPC, or author sys:chromecontrol steps in actions.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Routes Quicker headless action editing (P0–P7): pick workflow topic, then schema/step-runner refs. Use when creating or editing Quicker actions, subprograms, steps, or data.json on disk.
After quicker-rpc source changes, run pwsh ./build.ps1 -t (hot-reload plugin + qkrpc CLI/serve) without restarting agent-gui. Use when editing Plugin, Console, Contracts, AgentModel, build scripts, or RPC/CLI; when the user asks to build, test build, build -t, hot update, /hot-update, reload plugin, or restart qkrpc serve. For official getquicker release use quicker-rpc-publish + quicker-qkbuild-version-publish (third field +1).
Guides action designer (action-editor) UI work in agent-gui. UI originates from ../Quicker/Quicker.Designer; step double-click popup and per-field editing behavior must match ../Quicker/QuickerPc/Quicker ActionDesignerWindow and StepEditor components. Use when editing agent-gui/lib/action-editor, StepEditorPopup, param editors, step field visibility, or aligning web step editing with desktop Quicker.
Guides agents to find Quicker.exe internal types and methods for quicker-rpc plugin work. Use when implementing or debugging reflection against Quicker.exe, locating internal Quicker APIs, handling obfuscated Release builds, qkref references, or service access from QuickerRpc.Plugin.
Analyze QuickerAgent chat exports (quicker-agent-chat-export JSON) to score authoring flow, detect tool/schema issues, and recommend prompt/tool/skill optimizations. Use when the user provides an exported thread JSON or asks to improve agent-gui behavior from real sessions.
getquicker User/Actions 分页 HTML 抓取：汇总获赞 totalLikes 与动作数 actionCount。写分页 HTTP 抓取、HTML 解析聚合类动作时加载。
| name | quicker-chromecontrol |
| description | Control the user's real browser (Quicker Connector) via user_browser / qkrpc_chrome_control RPC, or author sys:chromecontrol steps in actions. |
Route for browser automation against the user's logged-in browser.
See also: docs/browser-automation.md — unified boundary table (Playwright / embedded / extension).
QuickerAgent browser | user_browser / qkrpc_chrome_control | sys:chromecontrol steps | |
|---|---|---|---|
| Who runs | Agent Playwright session | Agent via RPC → Quicker extension | User's action at runtime |
| Login state | None (clean profile) | User's cookies / login | User's cookies / login |
| Needs extension | No | Yes (Quicker Connector) | Yes |
| Use for | Agent reads arbitrary URL while designing | Agent operates user's open browser in chat | Production automation in saved actions |
user_browser({ action: "tabs" }) or MCP qkrpc_chrome_tabs — list connected tabsuser_browser({ action: "run", operation: "OpenUrl", parameters: { url, windowId: "New", waitComplete: true } })sessionId; tabId from OpenUrl is auto-carried when omitted on next runqkrpc chrome run --operation RunScript --params '{"script":"document.title"}' --jsonParameter schema: qkrpc_step_runner_get with key=sys:chromecontrol and controlField = operation.
qkrpc_step_runner_search → sys:chromecontrolqkrpc_step_runner_get with controlField = operationdocs({ action: "get", topic: "chromecontrol-authoring" })reference: "examples/chromecontrol"tabId.var in actions; literal tabId or session in RPC)inputParams keys — always step_runner_get firstquicker-browser-script (page script + trigger auto-run pipeline) · quicker-authoring · qkrpc · browser (Playwright, no login)