skill installer
- Repo stars 177
- Author repo OpenAgentd
- Domain
- AI
- Author-declared agents
- No explicit declaration found; this is not inferred or tested compatibility
- Static check
- 88 / 100 · heuristic scan, not runtime safety proof
- Runtime evidence
- Not run; no isolated runtime test evidence is currently recorded
- Author / version / license
- @lthoangg · no license declared
- Token usage
- Lean
- Setup complexity
- Plug-and-play
- External API key
- Not required
- Operating systems
- Unspecified (assume cross-platform)
- Runtime requirements
- No explicit requirements detected
- Detected file/system behavior
-
- Read-only
- Write / modify
- Network behavior
- External requests
- Install commands
- None (reference only)
Heads up: Tool permissions are not declared; actual access depends on the runtime.
# Skill Installer
## Discovery order
OpenAgentd discovers skills from five roots, in this order. The first skill
with a given name wins:
1. `{cwd}/.openagentd/skills/{skill-name}/SKILL.md` — project-specific OpenAgentd skill.
2. `{cwd}/.opencode/skills/{skill-name}/SKILL.md` — project opencode-compatible skill.
3. `{SKILLS_DIR}/{skill-name}/SKILL.md` — global OpenAgentd skill.
4. `~/.config/opencode/skills/{skill-name}/SKILL.md` — global opencode-compatible skill.
5. Bundled OpenAgentd operational skills — read-only fallback.
Default to `{SKILLS_DIR}` for user-global installs unless the user explicitly
asks for a project-local skill or an opencode-shared skill.
If the target name already exists only as a bundled skill, install an override
in `{SKILLS_DIR}` (or the requested project root); never edit bundled files.
## Skill file format
A skill is a directory at `{root}/{skill-name}/` containing at minimum a `SKILL.md` file. The `SKILL.md` has YAML frontmatter and a Markdown body:
```markdown
---
name: skill-name
description: One-sentence description shown in the system prompt.
---
# Skill Title
Full instructions the agent reads when it calls skill("skill-name").
```
## How to install
### From a URL
1. Fetch the raw content with `web_fetch`.
2. Parse out the frontmatter `name` field — that becomes the directory name.
3. Write the content to `{SKILLS_DIR}/{name}/SKILL.md`.
### From scratch
1. Ask the user what the skill should do if not already specified.
2. Write a `SKILL.md` following the format above to `{SKILLS_DIR}/{name}/SKILL.md`.
3. Create any supporting files (e.g. `reference.md`) in the same directory if useful.
## Rules
- Directory name must match the `name` field in frontmatter (lowercase, hyphens only).
- Never overwrite an existing skill without confirming with the user first — read it first and show what will change.
- After writing, confirm the path and name so the user can add it to an agent's `skills:` list.
- A new skill can be loaded by exact name immediately. It appears in generated "Available skills" sections after the affected agent rebuilds on its next turn; if a cached skill catalog is stale, use the Skills API/UI path or restart as a fallback.
Sections and files
Listed in source order.
sections -> Discovery order → Skill file format → How to install → From a URL → From scratch → Rules
terms -> OpenAgentd discovers skills from five roots, in this order. · 1. {cwd}/.openagentd/skills/{skill-name}/SKILL.md — project-specific OpenAgentd skill. · Default to {SKILLSDIR} for user-global installs unless the user explicitly asks for a project-local skill or an opencode-shared skill. · A skill is a directory at {root}/{skill-name}/ containing at minimum a SKILL.md file. · Full instructions the agent reads when it calls skill("skill-name"). · 1. Fetch the raw content with webfetch. · 1. Ask the user what the skill should do if not already specified. · - Directory name must match the name field in frontmatter (lowercase, hyphens only).
files/cmd -> {cwd}/.openagentd/skills/{skill-name}/SKILL.md · {cwd}/.opencode/skills/{skill-name}/SKILL.md · {SKILLS_DIR}/{skill-name}/SKILL.md · ~/.config/opencode/skills/{skill-name}/SKILL.md · {SKILLS_DIR} · {root}/{skill-name}/ · web_fetch · name
body sha256 -> 660a53a6da20
Discovery order
OpenAgentd discovers skills from five roots, in this order. The first skill with a given name wins:
{cwd}/.openagentd/skills/{skill-name}/SKILL.md— project-specific OpenAgentd skill.{cwd}/.opencode/skills/{skill-name}/SKILL.md— project opencode-compatible skill.{SKILLS_DIR}/{skill-name}/SKILL.md— global OpenAgentd skill.Skill file format
A skill is a directory at
{root}/{skill-name}/containing at minimum aSKILL.mdfile. TheSKILL.mdhas YAML frontmatter and a Markdown body:From a URL
Fetch the raw content with
web_fetch. Parse out the frontmatternamefield — that becomes the directory name. Write the content to{SKILLS_DIR}/{name}/SKILL.md.From scratch
Ask the user what the skill should do if not already specified. Write a
SKILL.mdfollowing the format above to{SKILLS_DIR}/{name}/SKILL.md. Create any supporting files (e.g.reference.md) in the same directory if useful.Rules
Directory name must match the
namefield in frontmatter (lowercase, hyphens only). Never overwrite an existing skill without confirming with the user first — read it first and show what will change. After writing, confirm the path and name so the user can add it to an agent'sskills:list. A new skill can be loaded by exact name immediately. It appears in generated "Available skills" sections after the affected agent rebuilds on its next turn; if a cached skill catalog is stale, use the Skills API/UI path or restart as a fallback.