Install skills from the desktop app when you want to add reusable capabilities to a gateway. Pioneer supports skills compatible with the Agent Skills specification. A compatible skill package should include aDocumentation Index
Fetch the complete documentation index at: https://docs.getpioneer.dev/llms.txt
Use this file to discover all available pages before exploring further.
SKILL.md file and may include scripts, references, assets, templates, or other supporting files.
Before installing
Ask these questions:- Do you trust the source?
- Does the skill run shell commands?
- Does it make HTTP requests?
- Does it need local dependencies?
- Should it be installed on this gateway or a sandbox gateway first?
- Is it safe to use in the current workspace?
- Should it be implicit, or should users name it explicitly?
Install from an archive
Choose install
Click the install action for a local skill archive or folder, depending on your build.
Confirm availability
Confirm the skill is enabled in the current workspace before using it in real work.
Validation results
Pioneer may report:| Result | Meaning |
|---|---|
| Ready | The skill passed validation and dependency checks |
| Warning | The skill can be installed, but you should review a finding |
| Missing dependency | A required command or runtime dependency is not available |
| Blocked | Policy or validation prevents use |
| Unknown | Pioneer could not fully determine health |
Dependency checks
Some skills require commands or local tools. If dependency checks fail:- Read the missing dependency message.
- Install the dependency on the gateway host.
- Restart the gateway if the dependency changes
PATH. - Run skill health checks again.
Install location
Skills are part of the gateway runtime. If you install a skill on one gateway, it is not automatically installed on another gateway. This is intentional. It lets you keep different capabilities for:- work
- home
- study
- sandbox testing
- remote automation