skill-installer
- Repo stars 604
- Author updated Live
- Author repo VTCode
- Domain
- AI
- Compatible agents
-
- Claude Code
- Cursor
- Cline
- Codex
- Windsurf
- Gemini CLI
- +20
- Trust score
- 88 / 100 · community maintained
- Author / version / license
- @vinhnx · no license declared
- Token usage
- Lean
- Setup complexity
- Guided setup
- External API key
- Required · GitHub
- Operating systems
- Unspecified (assume cross-platform)
- Runtime requirements
- No special requirements
- Permissions
-
- Read-only
- Env read
- Write / modify
- Network behavior
- External requests
- Install commands
- 26 variants
Profile is derived at build time from SKILL.md and install vectors. Subject to drift from author intent.
Heads up: 未限定 allowed-tools，默认拥有全部工具权限。
---
name: skill-installer
description: Install VT Code skills into ~/.agents/skills from a curated list or a GitHub repo path. Use when…
category: ai
runtime: no special runtime
---
# skill-installer output preview
## PART A: Task fit
- Use case: Install VT Code skills into ~/.agents/skills from a curated list or a GitHub repo path. Use when a user asks to list installable skills, install a curated skill, or install a skill from another repo, including private repos..
- Inputs: target material, constraints, expected output, and acceptance criteria.
- Evidence boundary: follow “Communication / Scripts / List Curated Skills” and do not present inference as author intent.
## PART B: Execution result
- **01** The card summarizes the use case; runtime output centers on “Install VT Code skills into ~/.agents/skills from a curated list or a GitHub repo path. Use when a user asks to list installable skills, install a curated skill, or install a skill from another repo, including private repos.”.
- **02** When the source has headings, the agent prioritizes “Communication / Scripts / List Curated Skills” so the result follows the author’s structure.
- **03** Typical output includes task judgment, concrete steps, required commands or file edits, validation, and follow-up options.
- **04** Risk context follows the fingerprint: read files, read environment variables, write/modify files; may access external network resources; requires GitHub API keys.
## Running Rules
- read files, read environment variables, write/modify files; may access external network resources; requires GitHub API keys.
- Validate with a small sample before expanding scope.
- Return the result, validation criteria, and next iteration options.The source mentions slash commands such as `/skills`; use them first when your agent supports command triggers.
Name target files or source material, expected output, forbidden changes, and whether network or shell access is allowed. Permission fingerprint: read files, read environment variables, write/modify files.
Start with a small task and check whether the result follows “Communication / Scripts / List Curated Skills”. Inspect diffs, logs, previews, or tests before expanding scope.
Confirm the final output includes a concrete result, evidence, and next action. If it stays generic, tighten inputs, boundaries, and acceptance criteria.
---
name: skill-installer
description: Install VT Code skills into ~/.agents/skills from a curated list or a GitHub repo path. Use when…
category: ai
source: vinhnx/VTCode
---
# skill-installer
## When to use
- Install VT Code skills into ~/.agents/skills from a curated list or a GitHub repo path. Use when a user asks to list i…
- Use it when the task has clear inputs, repeatable steps, and validation criteria.
## What to provide
- Target material, scope, expected result, and forbidden changes.
- Whether network, commands, file writes, or external services are allowed.
## Execution rules
- Organize steps around “Communication / Scripts / List Curated Skills” and keep inference separate from source facts.
- read files, read environment variables, write/modify files; may access external network resources; requires GitHub API keys.
- Validate with a small sample before expanding the task.
## Output requirements
- Return the deliverable, key evidence, validation method, and next action.
- Mark missing information as unknown; do not invent commands, platforms, or dependencies.The author source anchors workflow facts; repository files anchor sources and commands; Fluxly only adds fit, limitations, and quality judgment.
skill "skill-installer" {
input -> user goal + target files + boundaries + acceptance criteria
context -> Communication / Scripts / List Curated Skills
rules -> SKILL.md triggers / order / output contract
runtime -> no special runtime | read files, read environment variables, write/modify files | may access external network resources
guardrails -> requires GitHub API keys + small-sample validation + diff/log review
output -> copyable result + checklist + next iteration
}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
- Start by confirming the task and running the appropriate command.
- If something fails, report the exact error and ask what to do next.
- Say only what is necessary.
Scripts
List Curated Skills
Show available skills from the curated list:
scripts/list-curated-skills.pyOptional: specify a different repo or path:
scripts/list-curated-skills.py --repo owner/repo --path skills/path --ref branchOutput formats:
- Default: numbered list with installation status
- JSON:
--format jsonfor programmatic use
Install from Curated List
Install a skill by name from the curated list:
scripts/install-skill-from-github.py <skill-name>The skill will be installed to ~/.agents/skills/<skill-name>/.
Install from Any GitHub Repo
Install skills from any GitHub repository:
scripts/install-skill-from-github.py owner/repo path/to/skillFor private repos, ensure gh CLI is authenticated or GITHUB_TOKEN is set.
Install multiple skills from the same repo:
scripts/install-skill-from-github.py owner/repo path/to/skill1 path/to/skill2Behavior and Options
Installation Location
Skills are installed to ~/.agents/skills/ by default.
Private Repositories
For private repositories:
- Ensure GitHub CLI (
gh) is installed and authenticated:gh auth login - Or set the
GITHUB_TOKENenvironment variable
Overwriting Existing Skills
If a skill with the same name already exists, the installer will:
- Warn about the existing skill
- Ask for confirmation before overwriting
- Back up the existing skill before replacement
Validation
Before installing, the script validates:
- SKILL.md exists and has valid frontmatter
- Skill name follows naming conventions
- No invalid or dangerous file patterns
Notes
- Skills installed from GitHub are placed in the User scope.
- After installation, the skill is immediately available in the current session.
- Use
/skills listto verify installation. - Use
/skills load <skill-name>to activate the skill.
Decide Fit First
Design Intent
How To Use It
Boundaries And Review