skill-installer

Name: skill-installer
Author: lthoangg

AI Community

Repo stars 177
Author repo OpenAgentd

Interpretation is structured for decision-making; original keeps the upstream SKILL.md unchanged.

Decide Fit First

Core job: >- OpenAgentd discovers skills from five roots, in this order. The first skill with a given name wins: Default to {SKILLS_DIR} f…
Best fit: Use it when the task has reusable inputs, steps, and validation criteria rather than a one-off answer.
Avoid forcing it: If the source lacks commands, platform support, or external-service evidence, keep those fields unknown instead of guessing.

Design Intent

Structure: The skill is organized around “Discovery order”, “Skill file format”, “How to install”, “From a URL”, showing how the author expects the agent to judge fit, collect context, and produce verifiable output.
Trigger evidence: Prioritize the author’s wording around when to use it, what context to collect, and what output shape to produce.
Evidence boundary: Author text states facts, repository files prove commands and paths, and Fluxly only adds fit, limits, and usage judgment.

How To Use It

Inputs: Provide target material, scope, expected result, forbidden changes, and validation method.
Invocation: Name skill-installer directly; if the source includes slash commands, start with the command and then add task context.
Validation: Start small and check whether the result follows “Discovery order / Skill file format / How to install” before expanding.

Boundaries And Review

Dependencies: It usually needs no extra API key, so start with a small validation task.
Permissions: Declared permissions include read / write; ask the agent to state file, command, and rollback boundaries before acting.
Quality bar: A useful result names the deliverable, evidence, and next action. Generic prose means the task needs tighter context.

Skill Installer

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.
~/.config/opencode/skills/{skill-name}/SKILL.md — global opencode-compatible skill.
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:

---
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

Fetch the raw content with web_fetch.
Parse out the frontmatter name field — 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.md following 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 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.

Fluxly profile Author and license come from source; runtime, permissions, and network are Fluxly detections or estimates

Fluxly category: 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
Author / version / license: @lthoangg · no license declared
Fluxly token estimate: Lean
Fluxly setup estimate: Plug-and-play
External API key: No requirement detected
Detected OS requirements: Unspecified
Runtime requirements: Unspecified
Detected file/system behavior: Read-only
Write / modify
Detected network behavior: External requests
Install commands: None (reference only)

Profile is derived at build time from SKILL.md and install vectors. Subject to drift from author intent.

Heads up: 未限定 allowed-tools，默认拥有全部工具权限。

Output preview skill-installer-lthoangg.preview

The current SKILL.md does not define a fixed output example.

SKILL.md SKILL.md

# 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).

…

Evidence boundary and execution chain

Author text anchors workflow facts; Fluxly only indexes current sections, terms, files, and commands.

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 · {SKILLSDIR}/{skill-name}/SKILL.md · ~/.config/opencode/skills/{skill-name}/SKILL.md · {SKILLSDIR} · {root}/{skill-name}/ · webfetch · name
body sha256 -> 660a53a6da20