liriliri/debug
plugins/skills/debug/SKILL.md
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.
$ install --global
skillsauthnpx skillsauth add liriliri/tinker debugInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: May 29, 2026, 7:23 AM36.7s1 file scanned
SKILL.md
- 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(../bin/tinker-dev:*)
Tinker Plugin Debug
Debug and interact with Tinker plugins at runtime using tinker-dev CLI and agent-browser for visual inspection.
Prerequisites
Tinker must be running with --remote-debugging-port=9222 (configured in the root package.json start script). The --inspect=9229 port is for Node.js main process debugging only and does NOT expose renderer pages.
tinker-dev Commands
# Open a plugin
../bin/tinker-dev open <plugin-name>
# Restart a plugin (also starts if not running)
../bin/tinker-dev restart <plugin-name>
# Close a plugin
../bin/tinker-dev close <plugin-name>
Connecting agent-browser
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.
Tab Selection Tips
- The plugin hosting window tab shows
http://localhost:8080/?page=plugin(this is the outer shell, not the plugin content) - The actual plugin content is in the
plugin://tinker-<name>/index.htmltab - Always switch to the
plugin://tab before running snapshot or interact commands
Connection Recovery
If agent-browser connect 9222 fails with "Connection refused", restart Tinker with remote debugging enabled:
../bin/tinker-dev quit
../bin/tinker-dev open <plugin-name> --remote-debugging-port=9222
Then retry connecting:
agent-browser connect 9222
Notes
- If the plugin tab doesn't appear, wait a moment after
tinker-dev open/restartfor the page to load
Related Skills
liriliri/lint
tools
VerifiedTrustedCommunity
Check code against Tinker plugin coding standards
135SKILL.mdUpdated Apr 15, 2026
liriliri/new
tools
VerifiedTrustedCommunity
Create a new Tinker plugin from the template
132SKILL.mdUpdated May 23, 2026
liriliri/simplify
development
VerifiedTrustedCommunity
Review changed code for reuse, quality, and efficiency, then fix any issues found.
132SKILL.mdUpdated Apr 17, 2026
liriliri/vendor-dep
tools
VerifiedTrustedCommunity
Extract a npm dependency into the shared vendor bundle
131SKILL.mdUpdated Apr 19, 2026