Skills
Skills are one of Sentinel's extension systems.
They let the app pull in extra capability packs without stuffing every specialized workflow into the core app.
What skills can target
The skills UI supports six install targets:
| Target | Global folder | Workspace folder |
|---|---|---|
sentinel | ~/.sentinel/skills | .sentinel/skills |
claude | ~/.claude/skills | .claude/skills |
codex | ~/.codex/skills | Global only |
copilot | ~/.copilot/skills | .github/skills |
cursor | ~/.cursor/skills | .cursor/skills |
opencode | ~/.config/opencode/skills | .opencode/skills |
That matters because a skill can live in different directories depending on the target runtime.
Scope
Installs can be global or workspace-scoped. Codex skills are global only.
When the engine instance you picked has its own home directory (CODEX_HOME, CLAUDE_CONFIG_DIR, or COPILOT_HOME), global skills go into skills inside that home instead of the default folder above.
Grok Build and Pi manage their own skills; Sentinel does not install skills for them.
Sources
Skills can come from:
- the curated registry
- a custom repository or path
The app keeps track of what is installed and where.
What you can do from the skills screen
- browse installed skills
- browse curated registry entries
- inspect skill details
- install a curated skill
- install a custom skill
- uninstall a skill
For Codex-targeted skills, the app also syncs enabled state through the Codex app server manager.
Why skills exist
Skills are the simpler way to add focused behavior without growing the main app every time.