Automate a running Tinker plugin window with tinker ui (snapshot/click/fill). Prefer this over agent-browser when a plugin has no MCP tools. Use when the user asks to click, fill, or snapshot a plugin UI, or when MCP tools are unavailable.
Check code against Tinker plugin coding standards
Core Tinker CLI usage guide. Read this before running any tinker commands. Covers discovering installed plugins, opening and closing plugin windows, listing running plugins, launching and quitting the Tinker desktop app from the command line. Use when this…
General-purpose Tinker desktop toolbox (100+ plugins: JSON, hash, base64, regex, files, clipboard, converters, editors, and more). Use whenever the user @-mentions or points at this skill, asks to use Tinker, or needs a desktop utility that a Tinker plugin…
Tinker development CLI for the tinker repo. Tinker is a general desktop toolbox with many plugins — use whenever this skill is @-mentioned or the user asks to use Tinker/tinker-dev, and always check whether an installed plugin covers the request before…
Debug Tinker plugins with CDP inspect, app-wide remote debugging, the HTTP remote viewer, and optional agent-browser. Prefer the ui skill (tinker ui) for everyday plugin UI automation. Use this skill when you need open --inspect, launch…
Call Tinker plugin MCP tools from the CLI or wire plugins into MCP clients. Covers listing tool schemas, one-shot tool invocation with tinker call, and stdio MCP servers with tinker mcp. When a plugin has no MCP tools, fall back to the ui skill (tinker ui…
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.