메뉴
Debug Tinker plugins with agent-browser. Use when the user needs to open, inspect, interact with, restart, or close a plugin in the running Tinker Electron app.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Tinker desktop toolbox CLI for AI agents. Use when the user needs to open a Tinker plugin, create a new Tinker plugin, list installed plugins, control plugin windows from the command line, call plugin MCP tools, debug a plugin UI, or integrate Tinker with an AI agent via MCP. Triggers include "open a Tinker plugin", "create a Tinker plugin", "list tinker plugins", "tinker open", "call a plugin tool", "tinker MCP", "automate JSON editor", or any task requiring programmatic control of the Tinker Electron app and its plugins. Prefer tinker CLI over guessing IPC or UI steps.
Core Tinker CLI usage guide. Read this before running any tinker commands. Covers discovering installed plugins, opening and closing plugin windows, listing running plugins, and controlling the Tinker desktop app from the command line. Use when the user asks to open a Tinker plugin, list plugins, check what is running, restart or close a plugin, or quit Tinker.
Implement or audit MCP tools for a Tinker plugin. Use when adding MCP support, writing src/mcp.ts, defining tinker.mcp.tools in package.json, reviewing plugin MCP conventions, or checking whether an MCP implementation follows project standards.
Tinker development CLI for working in the tinker repo. Use when developing Tinker itself or its plugins and you need to open plugins, list installed plugins, control plugin windows, or call plugin MCP tools via `./bin/tinker-dev`. Do not use the packaged `tinker` CLI in this repo. Triggers include tasks in the tinker-utm repo requiring programmatic control of the dev Tinker app. Prefer `./bin/tinker-dev` over the global `tinker` skill or guessing IPC/UI steps.
Debug Tinker plugins with agent-browser. Use when the user needs to open, inspect, interact with, restart, or close a plugin in the running Tinker Electron app.
Check code against Tinker plugin coding standards
| name | debug |
| description | Debug Tinker plugins with agent-browser. Use when the user needs to open, inspect, interact with, restart, or close a plugin in the running Tinker Electron app. |
| allowed-tools | Bash(agent-browser:*), Bash(npx agent-browser:*), Bash(tinker:*) |
Debug and interact with Tinker plugins at runtime using tinker CLI and agent-browser for visual inspection.
Tinker must be running with --remote-debugging-port=9222. The --inspect port is for Node.js main process debugging only and does NOT expose renderer pages.
If remote debugging is not enabled, open or restart the plugin with the flag (see Connection Recovery).
# Open a plugin
tinker open <plugin-name>
# Restart a plugin (also starts if not running)
tinker restart <plugin-name>
# Close a plugin
tinker close <plugin-name>
# Quit Tinker
tinker quit
After opening a plugin, connect to CDP port 9222:
agent-browser connect 9222
agent-browser tab
# Switch to the plugin://tinker-<name>/index.html tab
agent-browser tab t2
agent-browser snapshot -i
For agent-browser interaction commands (click, fill, screenshot, etc.), refer to the agent-browser skill documentation.
http://localhost:8080/?page=plugin (this is the outer shell, not the plugin content)plugin://tinker-<name>/index.html tabplugin:// tab before running snapshot or interact commandsIf agent-browser connect 9222 fails with "Connection refused", restart Tinker with remote debugging enabled:
tinker quit
tinker open <plugin-name> --remote-debugging-port=9222
Then retry connecting:
agent-browser connect 9222
tinker open/restart for the page to load