Using npx skills with PromptScript
Note: With PromptScript v1.8+, you can import skills directly using
@use— no need fornpx skillsorskills.sh. See Markdown Imports.
The skills CLI lets you install open-source skills from GitHub repositories directly into your project. PromptScript compiles these skills to all your AI coding agents automatically.
Quick Start
1. Browse available skills
# List all skills in the official Anthropic skills reponpx skills add anthropics/skills --list
# List skills from any GitHub reponpx skills add vercel-labs/agent-skills --list2. Install a skill
# Install to .promptscript/skills/ for PromptScript projectsnpx skills add anthropics/skills \ --skill frontend-design \ --dir .promptscript/skills
# Install multiple skillsnpx skills add anthropics/skills \ --skill commit \ --dir .promptscript/skills
npx skills add anthropics/skills \ --skill code-review \ --dir .promptscript/skillsThis creates the following structure:
.promptscript/└── skills/ ├── frontend-design/ │ ├── SKILL.md │ ├── data/ │ │ └── colors.csv │ └── scripts/ │ └── search.py ├── commit/ │ └── SKILL.md └── code-review/ └── SKILL.md3. Reference skills in your .prs file
@skills { frontend-design: { description: "UI/UX design with searchable databases" }
commit: { description: "Create git commits" userInvocable: true }
code-review: { description: "Review code changes" userInvocable: true }}You only need the skill name and optional metadata. PromptScript loads content from SKILL.md automatically.
4. Compile
prs compileEach skill, including its resource files, is copied to every configured target with native skill support:
.claude/skills/frontend-design/SKILL.md.claude/skills/frontend-design/data/colors.csv.claude/skills/frontend-design/scripts/search.py.factory/skills/frontend-design/SKILL.md.factory/skills/frontend-design/data/colors.csv.factory/skills/frontend-design/scripts/search.py.agents/skills/frontend-design/skill.md...Alternative: .agents/ directory
By default, npx skills add installs to .agents/skills/. PromptScript discovers this directory automatically without any extra configuration:
# Default install location (no --dir flag)npx skills add anthropics/skills --skill commit# Installs to .agents/skills/commit/SKILL.mdPromptScript checks skills in this order:
.promptscript/skills/<name>/(local, highest priority).agents/skills/<name>/(universal directory)- Registry (lowest priority)
If you prefer to keep npx skills defaults and not use --dir, everything works out of the box. To disable this behavior:
universalDir: falseSkill Sources
Official repositories
| Repository | Command |
|---|---|
| Anthropic Skills | npx skills add anthropics/skills --list |
| Vercel Agent Skills | npx skills add vercel-labs/agent-skills --list |
Community skills
Any GitHub repository that contains skill directories (with SKILL.md files) works:
npx skills add someone/their-skills \ --skill my-skill \ --dir .promptscript/skillsOpenSkills
OpenSkills is another skill installer:
npx openskills install frontend-design \ --dir .promptscript/skillsOverriding skill metadata
When a skill from npx skills doesn’t have the exact settings you need, override them in your .prs file:
@skills { commit: { description: "Create commits with conventional format" userInvocable: true # Override default disableModelInvocation: true # Override default }}The content always comes from SKILL.md and cannot be overridden in .prs. For other properties, the .prs file takes precedence - for example, description from .prs overrides description from SKILL.md frontmatter.
Parameterized skills
Some skills accept parameters via {{variable}} templates in their SKILL.md:
---name: code-reviewdescription: Review {{language}} codeparams: language: type: string default: typescript---
Review the provided {{language}} files.Pass parameter values in your .prs file:
@skills { code-review: { language: "python" }}Updating skills
To update an installed skill, reinstall it:
npx skills add anthropics/skills \ --skill frontend-design \ --dir .promptscript/skillsThis overwrites the existing skill directory with the latest version.
Security
Treat third-party skills as executable dependencies. Before installing or updating one:
- Review
SKILL.md, scripts, hooks, and bundled resources. - Pin the repository to a reviewed commit or release when the installer supports it.
- Inspect the resulting git diff before running any bundled script.
- Review updates independently instead of assuming a previously trusted repository is unchanged.
Version control
Commit installed skills to git. They are part of your project’s AI configuration:
git add .promptscript/skills/git commit -m "feat: add frontend-design and commit skills"See Also
- Local Skills - Full reference for local skills, resolution order, and resource files
- Building Skills - Create your own skills from scratch
- Skill Contracts - Define inputs and outputs for skills
- Shared Resources - Share files across all skills