skill-installer

Name: skill-installer
Author: ComposioHQ

Engineering Community

Repo stars 11,183
Author repo awesome-codex-skills

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

Decide Fit First

Core job: Install Codex skills into $CODEX_HOME/skills from a curated list or a GitHub repo path. Use when a user asks to list installable…
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 “Communication”, “Scripts”, “Behavior and Options”, “Notes”, 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 “Communication / Scripts / Behavior and Options” before expanding.

Boundaries And Review

Dependencies: Prepare GitHub API keys before running a full 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

Helps install skills. By default these are from https://github.com/openai/skills/tree/main/skills/.curated, but users can also provide other locations.

Use the helper scripts based on the task:

List curated skills when the user asks what is available, or if the user uses this skill without specifying what to do.
Install from the curated list when the user provides a skill name.
Install from another repo when the user provides a GitHub repo/path (including private repos).

Install skills with the helper scripts.

Communication

When listing curated skills, output approximately as follows, depending on the context of the user's request: """ Skills from {repo}:

skill-1
skill-2 (already installed)
... Which ones would you like installed? """

After installing a skill, tell the user: "Restart Codex to pick up new skills."

Scripts

All of these scripts use network, so when running in the sandbox, request escalation when running them.

scripts/list-curated-skills.py (prints curated list with installed annotations)
scripts/list-curated-skills.py --format json
scripts/install-skill-from-github.py --repo <owner>/<repo> --path <path/to/skill> [<path/to/skill> ...]
scripts/install-skill-from-github.py --url https://github.com/<owner>/<repo>/tree/<ref>/<path>

Behavior and Options

Defaults to direct download for public GitHub repos.
If download fails with auth/permission errors, falls back to git sparse checkout.
Aborts if the destination skill directory already exists.
Installs into $CODEX_HOME/skills/<skill-name> (defaults to ~/.codex/skills).
Multiple --path values install multiple skills in one run, each named from the path basename unless --name is supplied.
Options: --ref <ref> (default main), --dest <path>, --method auto|download|git.

Notes

Curated listing is fetched from https://github.com/openai/skills/tree/main/skills/.curated via the GitHub API. If it is unavailable, explain the error and exit.
Private GitHub repos can be accessed via existing git credentials or optional GITHUB_TOKEN/GH_TOKEN for download.
Git fallback tries HTTPS first, then SSH.
The skills at https://github.com/openai/skills/tree/main/skills/.system are preinstalled, so no need to help users install those. If they ask, just explain this. If they insist, you can download and overwrite.
Installed annotations come from $CODEX_HOME/skills.

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

Fluxly category: Engineering
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: @ComposioHQ · no license declared
Fluxly token estimate: Lean
Fluxly setup estimate: Guided setup
External API key: Required · GitHub
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-composiohq.preview

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

SKILL.md SKILL.md

# Skill Installer

Helps install skills. By default these are from https://github.com/openai/skills/tree/main/skills/.curated, but users can also provide other locations.

Use the helper scripts based on the task:
- List curated skills when the user asks what is available, or if the user uses this skill without specifying what to do.
- Install from the curated list when the user provides a skill name.
- Install from another repo when the user provides a GitHub repo/path (including private repos).

Install skills with the helper scripts.

## Communication

When listing curated skills, output approximately as follows, depending on the context of the user's request:
"""
Skills from {repo}:
1. skill-1
2. skill-2 (already installed)
3. ...
Which ones would you like installed?
"""

After installing a skill, tell the user: "Restart Codex to pick up new skills."

## Scripts

All of these scripts use network, so when running in the sandbox, request escalation when running them.

- `scripts/list-curated-skills.py` (prints curated list with installed annotations)
- `scripts/list-curated-skills.py --format json`
- `scripts/install-skill-from-github.py --repo <owner>/<repo> --path <path/to/skill> [<path/to/skill> ...]`
- `scripts/install-skill-from-github.py --url https://github.com/<owner>/<repo>/tree/<ref>/<path>`

## Behavior and Options

- Defaults to direct download for public GitHub repos.
- If download fails with auth/permission errors, falls back to git sparse checkout.
- Aborts if the destination skill directory already exists.
- Installs into `$CODEX_HOME/skills/<skill-name>` (defaults to `~/.codex/skills`).
- Multiple `--path` values install multiple skills in one run, each named from the path basename unless `--name` is supplied.

…

Evidence boundary and execution chain

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

sections -> Communication → Scripts → Behavior and Options → Notes
terms    -> Helps install skills. · Install skills with the helper scripts. · When listing curated skills, output approximately as follows, depending on the context of the user's request: """ Skills from {repo}: 1. · All of these scripts use network, so when running in the sandbox, request escalation when running them. · - Defaults to direct download for public GitHub repos. · - Curated listing is fetched from https://github.com/openai/skills/tree/main/skills/.curated via the GitHub API.
files/cmd -> scripts/list-curated-skills.py · scripts/list-curated-skills.py --format json · scripts/install-skill-from-github.py --url https://github.com/<owner>/<repo>/tree/<ref>/<path> · $CODEXHOME/skills/<skill-name> · ~/.codex/skills · --path · --name · --ref <ref>
body sha256 -> c8922427b536