Skills & Plugins
Junior combines instructions with configured capabilities.
Components
Section titled “Components”| Component | Purpose |
|---|---|
| Skill | Instructions for a type of work |
| Tool | An action Junior can take |
| Plugin | An integration enabled by the app operator |
| Sandbox | Isolated command execution |
Skills
Section titled “Skills”Skills are focused playbooks loaded when they match the request.
- Local skills live in
app/skills/<skill-name>/SKILL.md. - Plugins can include their own skills.
- Skills do not install packages, configure OAuth, or grant access.
If a skill needs a CLI, system package, MCP server, or credential flow, declare it in the plugin instead.
Invoke a skill
Section titled “Invoke a skill”Write $skill-name in a message or an automation instruction to run that skill, for example $weekly-report getsentry/junior. One message can invoke up to six skills. The model loads each invoked skill before it acts. An automation in skill mode works the same way: its run names the skill, and the model loads it. Junior still accepts the older /skill-name form. Only a person’s own message or an automation’s instructions invoke a skill. A reference in other text, such as event text, a child agent’s task, or a child agent’s result, does not. Do not describe invocation syntax inside a skill. Junior handles invocation.
Set disable-model-invocation: true in the skill frontmatter when only a person should start the skill. Junior also reads policy.allow_implicit_invocation: false in a Codex agents/openai.yaml file the same way. Junior then loads the skill only after a person’s message invokes it with $skill-name, or when a skill that the model can load references it as $skill-name in its SKILL.md. After Junior loads the skill once, it stays available for the rest of the conversation. Other mentions of the name, and references in references/ files, do not count.
Plugins
Section titled “Plugins”Junior loads plugins only from explicit app configuration. A plugin can register:
- tools and skills
- provider credentials and domains
- MCP servers
- runtime dependencies
- routes and events
Plugins run as trusted application code. The host still owns credential handling, validation, action review, and durable execution.
Core tools are part of Junior. Plugins and MCP servers can add more tools. Every tool has an input contract, and actions may require review before they run.
Tool output is treated as data. It cannot change the active user, destination, or credential authority.
Validate Configuration
Section titled “Validate Configuration”pnpm exec junior checkKeep package installs, CLIs, MCP servers, and API-key configuration in plugin.yaml or the plugin definition.
Next Step
Section titled “Next Step”Browse Plugins for available integrations. Read Security & Authority for capability and review boundaries.