Skip to main content
Install skills from the desktop app to add reusable capabilities to a gateway. Pioneer supports skills compatible with the Agent Skills specification. A compatible skill package should include a SKILL.md file and may include scripts, references, assets, templates, or other supporting files. If you are building the package yourself, start with Creating Skills. The archive you install should contain one top-level directory, and that directory should contain SKILL.md.

​
Before installing

Before installing, check:
  • 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 stay explicit-only, or is it trusted enough to make implicit later?
Skill tools are controlled by the turn permission mode. Use Supervised for first tests so Pioneer asks before commands, file changes, network actions, and other sensitive tool calls.

​
Install from an archive

1

Open Skills

In the desktop app, connect to the gateway and click the Skills icon in the bottom bar.
2

Choose install

Click the install action for a local skill archive or folder, depending on your build.
3

Select the source

Select the skill archive or source path.
4

Wait for upload

Large skill archives may upload in chunks.
5

Review validation

Check validation issues, dependency diagnostics, and security findings.
6

Confirm availability

Confirm the skill is enabled in the current workspace before using it in real work.
7

Review implicit mode

New installs start not implicit. Keep that default unless the skill is trusted and broadly useful.

​
Validation results

Pioneer may report:

​
Dependency checks

Some skills require commands or local tools. If dependency checks fail:
  1. Read the missing dependency message.
  2. Install the dependency on the gateway host.
  3. Restart the gateway if the dependency changes PATH.
  4. 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 keeps capabilities separate between:
  • work
  • home
  • study
  • sandbox testing
  • remote automation

​
First test after install

Attach the skill in a thread with the composer add button, then use a safe prompt:
Then test with a low-risk action.

​
Further reading

  • Skills Architecture explains install sources, validation, trust, dependency checks, and health.
  • Permission System explains permission modes, sandbox/resource policy, and approval requests for skill tools.
  • Secret Storage explains why credentials should live in gateway-managed secret storage, not skill prompts.