Menu
Use when deciding whether behavior belongs in an instruction file, durable doc, reusable skill, tool, or extension.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Use when deciding between follow-up queues, scheduled callbacks, automation-owned attention, wakeups, and async follow-up surfaces.
Use when a task benefits from JavaScript orchestration, explicit phases, structured progress logs, parallel fanout, or multiple daemon-backed subagents coordinated through the workflow tool.
Use when starting, inspecting, rerunning, following up, or cancelling durable background commands or subagents.
Use when designing, creating, editing, building, validating, installing, or debugging Neon Pilot extensions, application pages, contributions to existing applications, or complete first-class applications from the bundled desktop app. This skill is self-contained and must be used without a Neon Pilot source checkout.
Use when working with the built-in desktop Workbench Browser, browser comments, browser snapshots, CDP actions, screenshots, or the browser versus agent-browser boundary.
Use the unified Neon Pilot CLI/control plane for self-administration, delegated agent control, conversations, workspace/sidebar state, runs, automations, extensions, settings, and extension-contributed administration surfaces.
| name | skills-and-capabilities |
| description | Use when deciding whether behavior belongs in an instruction file, durable doc, reusable skill, tool, or extension. |
| metadata | {"id":"skills-and-capabilities","title":"Skills and Extension Capabilities","summary":"Built-in guidance for distinguishing reusable workflow skills from extension features.","status":"active"} |
Use this doc when you need to decide whether something should be a skill, a doc, an instruction file, an imported plugin package, or an extension.
Skills are reusable workflow packages.
Shared contract:
<knowledge-root>/skills/<skill>/SKILL.md
Use a skill when you want:
Extensions change what Neon Pilot can do.
Examples in this repo:
knowledge-baseweb-toolsdaemon-run-orchestration-promptcodex-profileUse an extension when the change requires code and runtime integration, not just new instructions.
Use an imported plugin/package wrapper when the capability already exists in another agent ecosystem, such as Codex, Claude, or MCP, and should be managed through Neon Pilot's extension registry.
AGENTS.md or selected instruction files for policy and standing behaviorIf markdown is enough, do not start with an extension.
Reach for an extension only when you need new tools, UI, event handling, runtime hooks, or permission behavior.