liriliri

@liriliri source repo

14 skills
0 followers
5 hours ago last updated

▌
MCP 2 · liriliri
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.

0
installs
▌
Debug 2 · liriliri
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.

0
installs
▌
Tinker · liriliri
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 might already provide — even if they never say "plugin" or "Tinker". Prefer discovering and using an installed plugin over writing a one-off script. Also use for opening plugins, listing plugins, MCP tool calls, UI debug via agent-browser, scaffolding plugins, or controlling the Tinker app from the CLI.

0
installs
▌
UI · liriliri
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.

0
installs
▌
MCP · liriliri
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 snapshot/click/fill). Use when the user asks to call a plugin tool, automate a plugin programmatically, integrate a Tinker plugin with Cursor or Claude Code via MCP, use tinker tools, tinker call, or tinker mcp, or work with plugins tagged [mcp].

0
installs
▌
Core · liriliri
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 skill is loaded for any user goal that might map to a Tinker plugin, or when the user asks to open a Tinker plugin, list plugins, check what is running, restart or close a plugin, launch or quit Tinker.

0
installs
▌
Debug · liriliri
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 --remote-debugging-port, launch --http, Chrome DevTools, or an external CDP client.

0
installs
▌
Create · liriliri
Create and run a standalone Tinker plugin from the tinker-whois template. Use when the user asks to create a new Tinker plugin, scaffold a plugin project, npm link for local development, or get a plugin running in Tinker.

0
installs
▌
Tinker Dev · liriliri
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 treating it as unrelated. Controls plugins via `./bin/tinker-dev` (open, list, MCP tools). Do not use the packaged `tinker` CLI in this repo.

0
installs
▌
Marketplace · liriliri
Add a tinker plugin to the marketplace

0
installs
▌
New · liriliri
Create a new Tinker plugin from the template

0
installs
▌
Lint · liriliri
Check code against Tinker plugin coding standards

0
installs
▌
Simplify · liriliri
Review changed code for reuse, quality, and efficiency, then fix any issues found.

0
installs
▌
Vendor Dep · liriliri
Extract a npm dependency into the shared vendor bundle

0
installs

14 published skills