Context Mode Doctor
mksglu/context-mode
Run context-mode diagnostics. Checks runtimes, hooks, FTS5, plugin registration, npm and marketplace versions. Trigger: /context-mode:ctx-doctor
Builds, installs and troubleshoots trusted local Paseo plugins, from lifecycle hooks and slash commands to screens, themes and timeline renderers.
Install Paseo Plugin Builder
$ npx skills add getpaseo/paseo --skill paseo-plugin -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install getpaseo/paseo paseo-plugin --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/getpaseo/paseo.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/paseo-plugin .claude/skills/paseo-plugin && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "paseo-plugin" agent skill from https://github.com/getpaseo/paseo/tree/main/skills/paseo-plugin into .claude/skills/paseo-plugin/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "paseo-plugin", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/getpaseo/paseo/tree/main/skills/paseo-pluginType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add getpaseo/paseo --skill paseo-plugin -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install getpaseo/paseo paseo-plugin --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/getpaseo/paseo.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/paseo-plugin .agents/skills/paseo-plugin && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "paseo-plugin" agent skill from https://github.com/getpaseo/paseo/tree/main/skills/paseo-plugin into .agents/skills/paseo-plugin/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "paseo-plugin", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add getpaseo/paseo --skill paseo-plugin -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install getpaseo/paseo paseo-plugin --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/getpaseo/paseo.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/paseo-plugin .cursor/skills/paseo-plugin && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "paseo-plugin" agent skill from https://github.com/getpaseo/paseo/tree/main/skills/paseo-plugin into .cursor/skills/paseo-plugin/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "paseo-plugin", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/getpaseo/paseo.git --path skills/paseo-plugin--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add getpaseo/paseo --skill paseo-plugin -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install getpaseo/paseo paseo-plugin --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/getpaseo/paseo.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/paseo-plugin .gemini/skills/paseo-plugin && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "paseo-plugin" agent skill from https://github.com/getpaseo/paseo/tree/main/skills/paseo-plugin into .gemini/skills/paseo-plugin/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "paseo-plugin", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install getpaseo/paseo paseo-pluginInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add getpaseo/paseo --skill paseo-plugin -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/getpaseo/paseo.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/paseo-plugin .github/skills/paseo-plugin && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "paseo-plugin" agent skill from https://github.com/getpaseo/paseo/tree/main/skills/paseo-plugin into .github/skills/paseo-plugin/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "paseo-plugin", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add getpaseo/paseo --skill paseo-plugin -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install getpaseo/paseo paseo-plugin --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/getpaseo/paseo.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/paseo-plugin .opencode/skills/paseo-plugin && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "paseo-plugin" agent skill from https://github.com/getpaseo/paseo/tree/main/skills/paseo-plugin into .opencode/skills/paseo-plugin/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "paseo-plugin", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
paseo-plugin- GitHub stars
- 20k
- Token cost
- ~9.4k tokens
- SKILL.md length
- 3,216 words
- Files
- 1
- Skills in repo
- 6
- Repo updated
- First seen
- Licence
- Custom licence
At a glance
Builds, installs and troubleshoots trusted local Paseo plugins, from lifecycle hooks and slash commands to screens, themes and timeline renderers.
- Works in 4 steps: Preserve the rest of config.json and set… → Run paseo reload --json against that… → Require pluginsEnabled in appliedPaths,… → …
- Creating a new Paseo plugin or editing an existing one
- SKILL.md covers Check current documentation, What a plugin can contribute, Create the project and Add a workspace panel, plus 13 more sections
- Calls npm and rg
What it does
The agent builds or manages the plugin you ask for instead of sending you off to read documentation. It starts by fetching the Paseo docs index at paseo.sh/llms.txt and then the current plugin quickstart, publishing guide and reference pages, preferring the deployed docs when they disagree with the skill, and it can keep working from the skill alone if the network is down. Inside the Paseo repository it reads `public-docs/plugins/reference.md` for the checkout's API, including unreleased changes.
A table in the skill maps each kind of contribution to its registration call and to the reference section that holds the full contract. Plugins can add screens and sidebar header or footer items, lifecycle hooks, transforms of agent configuration, environment, MCP servers or workspace creation, permission and follow-up automation, Command Center items and slash commands, composer pills and attachment sources, timeline items and their renderers, themes, and plugin RPCs. Most real plugins combine several, such as a slash command that calls an RPC, which appends a timeline row that a renderer draws. The publishing page covers npm packaging and private registries.
When your agent uses it
- Creating a new Paseo plugin or editing an existing one
- Installing, reloading, enabling, disabling or removing a plugin
- Adding a slash command, sidebar item, screen or composer pill
- Transforming or rendering agent timeline items from a plugin
Example prompts
- “Create a Paseo plugin that adds a slash command to summarize the current workspace.”
- “Add a sidebar footer item to my plugin that opens a settings screen.”
- “My Paseo plugin stopped loading after the last change; reload it and find the error.”
- “Write a plugin that adjusts the environment variables passed to agents when a workspace is created.”
Requirements
- Paseo with local plugin support
- Network access to paseo.sh for the current docs (optional)
Workflow steps
4 steps, taken from the first numbered list in SKILL.md.
- Preserve the rest of config.json and set the root pluginsEnabled field to true.
- Run paseo reload --json against that daemon.
- Require pluginsEnabled in appliedPaths, or accept an empty appliedPaths only after re-reading the file and confirming the live plugin…
- Run paseo plugin ls and verify the intended plugin reaches running after installation.
What it can do on your machine
Read from SKILL.md and the folder at commit 8f1091d. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
npmrg
From the folder's file list and the shell code blocks in SKILL.md.
Network
Links to these hosts (documentation or services it may open):
paseo.sh
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Paseo Plugin Builder loads about 9.4k tokens when it runs. Until then it costs about 146 tokens; SKILL.md has 3,216 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
Its licence (Custom licence) doesn't allow us to republish the file, so here is its outline and opening line. It has 3,216 words (~9,369 tokens).
“Build or manage the requested plugin directly. Use the current public docs to catch contract changes, but keep working from this skill if the network is unavailable.”
- name
- paseo-plugin
Files
Just SKILL.md in skills/paseo-plugin of getpaseo/paseo.
Open the folder on GitHubat commit 8f1091d
Compare with similar skills
Paseo Plugin Builder next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Paseo Plugin Builder this skillgetpaseo/paseo | 20k | — | ~9.4k | Automated safety check: Pass | Custom licence | |
| Context Mode Doctormksglu/context-mode | 26k | — | ~262 | Automated safety check: Pass | Custom licence | |
| Context Mode Upgrademksglu/context-mode | 26k | — | ~291 | Automated safety check: Pass | Custom licence | |
| Crush Configurationcharmbracelet/crush | 29k | — | ~3.7k | Automated safety check: Pass | Custom licence | |
| Agent Setup Health Audittw93/Waza | 7.2k | — | ~5.2k | Automated safety check: Notes | MIT | |
| Create Harnessruvnet/metaharness | 688 | — | ~777 | Automated safety check: Pass | MIT |
Similar skills
Context Mode Upgrade
mksglu/context-mode
Update context-mode from GitHub and fix hooks/settings. Pulls latest, builds, installs, updates npm global, configures hooks. Trigger: /context-mode:ctx-upgrade
Crush Configuration
charmbracelet/crush
Explains how to configure the Crush coding agent with crushrc or crush.json, covering providers, models, LSPs, MCP servers, hooks, permissions and config precedence.
Agent Setup Health Audit
tw93/Waza
Audits a project's agent configuration, instruction drift, hooks, MCP and AI maintainability, then reports prioritized findings with evidence and next actions.
Create Harness
ruvnet/metaharness
Scaffold your own focused AI agent harness — pick host (Claude Code, Codex, pi.dev, Hermes), template, agents, skills, and ship a npm-publishable harness with its own npx CLI.
Project Release
swimmwatch/cloakbrowser-mcp
Prepare, publish, verify, or recover a cloakbrowser-mcp release only when the user explicitly requests release work.
More from getpaseo/paseo
Paseo Advisor Second Opinion
getpaseo/paseo
Launches one separate agent through Paseo to give a second opinion on the current task, with a self-contained briefing and no permission to edit files.
Paseo Committee
getpaseo/paseo
Forms a two-agent committee with contrasting profiles to analyze a stuck problem in parallel, reconcile their views and return a consensus plan without editing files.
Paseo Agent Handoff
getpaseo/paseo
Hands off the current task, including context, decisions and failed attempts, to a fresh agent through Paseo by writing a self-contained briefing prompt and launching that agent.
Paseo Help
getpaseo/paseo
Answers questions about the Paseo app, such as setup, providers, connectivity, updates and logs, by checking the current public docs and working out which daemon is involved.
Paseo Agent Orchestration Reference
getpaseo/paseo
Reference for managing Paseo's projects, workspaces, workspace scripts and agents through its MCP tools or CLI, across a local or remote daemon.
Related
Works with
Categories
Questions about Paseo Plugin Builder
What does Paseo Plugin Builder do?
Builds, installs and troubleshoots trusted local Paseo plugins, from lifecycle hooks and slash commands to screens, themes and timeline renderers. The agent builds or manages the plugin you ask for instead of sending you off to read documentation.txt and then the current plugin quickstart, publishing guide and reference pages, preferring the deployed docs when they disagree with the skill, and it can keep working from the skill alone if the network is down.
When should I use Paseo Plugin Builder?
Paseo Plugin Builder fits situations like: creating a new Paseo plugin or editing an existing one; installing, reloading, enabling, disabling or removing a plugin; adding a slash command, sidebar item, screen or composer pill; transforming or rendering agent timeline items from a plugin.
How do I install Paseo Plugin Builder in Claude Code?
Run `npx skills add getpaseo/paseo --skill paseo-plugin -a claude-code`. Or copy the skill folder (skills/paseo-plugin in getpaseo/paseo) into .claude/skills/paseo-plugin in your project. Claude Code loads it when a task matches its description.
How do I install Paseo Plugin Builder in Codex?
Run `npx skills add getpaseo/paseo --skill paseo-plugin -a codex`. Or copy the skill folder (skills/paseo-plugin in getpaseo/paseo) into .agents/skills/paseo-plugin in your project. Codex loads it when a task matches its description.
Can I use Paseo Plugin Builder in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add getpaseo/paseo --skill paseo-plugin -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/paseo-plugin, .gemini/skills/paseo-plugin, .github/skills/paseo-plugin and .opencode/skills/paseo-plugin in your project.
What does Paseo Plugin Builder need to run?
Going by SKILL.md and its folder, Paseo Plugin Builder needs the command-line tools its instructions call (npm and rg). Our summary lists: Paseo with local plugin support; Network access to paseo.sh for the current docs (optional).
Does Paseo Plugin Builder access the network?
SKILL.md names 1 domain. As links in the text: paseo.sh. This is read from the text; nothing was executed.
Is Paseo Plugin Builder safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Paseo Plugin Builder use?
Paseo Plugin Builder has a licence file (the repository's licence) that doesn't match a standard licence. Read it on GitHub before reusing the skill.
How many tokens does Paseo Plugin Builder use?
About 9.4k tokens (SKILL.md is roughly 37k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Paseo Plugin Builder?
Skills that share tags, products or a category with Paseo Plugin Builder: Context Mode Doctor (mksglu/context-mode, 26k stars), Context Mode Upgrade (mksglu/context-mode, 26k stars), Crush Configuration (charmbracelet/crush, 29k stars) and Agent Setup Health Audit (tw93/Waza, 7.2k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Paseo Plugin Builder?
getpaseo (a GitHub organization) maintains it in getpaseo/paseo, which has 19,841 GitHub stars. The repository holds 6 skills in this directory. The repository was last updated on October 7, 2026.
Source: getpaseo/paseo on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.