laruss
UserThe browser that writes its own extensions.
Categories
Indexed Skills (12)
patcher-plugin-authoring
Write, build, and install Patcher plugins. Use whenever the task is to create a Patcher plugin, extend Patcher itself, or add a Patcher CLI command, agent tool, background service, settings, panel, mention provider, or other Patcher surface via a plugin. Covers the entire backend PatcherPluginApi and the frontend @patcher/plugin-sdk/app contract with working patterns.
skill-creator
Create new Patcher skills and improve existing ones. Use this whenever the user wants to make, write, author, draft, edit, refine, or optimize a skill — including turning the current conversation or workflow into a reusable skill, fixing a skill that is not triggering, or sharpening a skill's description. Skills live in ~/.patcher/skills/<name>/SKILL.md. Trigger on phrases like "create a skill", "make a skill for", "turn this into a skill", "write a SKILL.md", "my skill isn't triggering", or "improve this skill".
automations
Create and manage Patcher automations from the first-party automations plugin. Use when scheduling recurring or one-shot agent/script work with patcher automation commands.
docs
Access and update the user's Docs vaults. Use whenever the user asks to read, find, create, update, or store a note, document, plan, or HTML artifact; when a Docs @-mention appears in context; or when an answer should link to a document the user can open in Docs.
memory
Use durable Patcher memory when prior project knowledge or cross-project user preferences can improve the current task, and save durable new learning through the Patcher memory CLI.
tasks
Use when asked to work on or track a task in the Tasks plugin, when the prompt mentions a task key such as ABC-12, or when work needs task comments, attachments, delegation tracking, or status updates.
workflows
Execute a workflow script that orchestrates multiple subagents deterministically. Use for multi-agent orchestration, parallel or sequential agent pipelines, structured outputs, and durable background workflow runs.
patcher-browser
See and drive the browser inside Patcher — the page the user is looking at, their tabs, page text and selection, screenshots, clicks, typing and navigation. Use whenever you are asked whether you can see the user's page, browser, tab or site, what they are looking at, to read or screenshot a page, to click or type in one, or to open a URL for them. Works from inside a Patcher thread and from any other terminal on the machine; also covers the default case, where access is off and the user has to turn it on.
patcher-cli
Control Patcher itself from the command line. Use whenever the task is to inspect or orchestrate Patcher — spawn, steer, wait on, or read threads and subagents; delegate work to another agent; inspect projects, environments, machines, providers, or terminals; or manage skills, plugins, automations, themes, and app settings. Trigger on patcher status, patcher thread, patcher project, patcher environment, patcher terminal, patcher plugin, patcher skill, patcher automation, or any request to hand work to another Patcher thread.
inline-vis
Emit a sandboxed inline HTML visualization in an assistant message when a workspace .html file should render in-thread. Use after writing or updating a demo/chart/report HTML file the user should see without opening a panel.
secrets
Securely request API keys, access tokens, passwords, webhook secrets, or other credentials from the user and write them to a dotenv file without exposing their values to the agent.
repo-conventions
Conventions for working in this repository — commit style, branch naming, and testing expectations. Use when writing commits, opening PRs, or adding tests here.
Bio shown is the top-scored skill's repo description as a fallback — real GitHub bios land in a future update.