To install AI agent skills with Killer-Skills, run npx killer-skills add owner/repo. The CLI works without a global install, detects supported IDEs such as Cursor, Claude Code, VS Code, and Windsurf, writes the correct skill format for that environment, and gives you a clean validation path before you standardize a wider workflow stack.
Recommended Path: Zero-Install via npx
For most teams, npx is the safest way to start. It removes global version drift, keeps onboarding lightweight, and makes it easy to repeat the same install flow across local machines, review environments, and operator handoffs.
| Path | Best for | Command |
|---|
| Zero-install | First-time setup, testing, and team onboarding | npx killer-skills add owner/repo |
| Global CLI | Frequent operators who run the CLI every day | npm install -g killer-skills |
Install Your First Skill
- Open the project where your AI assistant should gain a new capability.
- Run the install command with the skill you want to add.
- Let the CLI detect your environment and write the IDE-native skill format.
npx killer-skills add owner/repo
The CLI is designed to bridge discovery and execution. If you are still deciding what to install, review the official trusted tools collection or the agent workflow building tools collection before you standardize a team stack.
Verify the Installation
Installation is only complete when you confirm the skill is present in the environment your team actually uses.
- Run
npx killer-skills list to confirm the skill is registered.
- Check that the CLI wrote the right format for your IDE instead of falling back to a generic output.
- Open your assistant and confirm the new skill is available in the current project.
# Verify the skill is installed
npx killer-skills list
# Optional: inspect available commands
npx killer-skills --help
What the CLI Writes
Killer-Skills does not install one generic blob everywhere. It writes the format each environment expects so setup can survive real developer workflows.
- Cursor: updates
.cursorrules
- Claude Code: installs into
.claude/skills/
- VS Code + Copilot: updates
.github/copilot-instructions.md
- Windsurf: writes skills into
.windsurf/rules/
If you need the operator view of sync behavior, file outputs, and command coverage, continue into the CLI overview.
Common Commands After Install
# Install a skill
npx killer-skills add owner/repo
# List installed skills
npx killer-skills list
# Search for skills
npx killer-skills search "image"
# Open interactive mode
npx killer-skills
When Global Installation Makes Sense
Use the global CLI only when you already know Killer-Skills is part of your daily operator workflow and you want a shorter command path.
npm install -g killer-skills
killer-skills --version
Even then, keep the zero-install path documented for teammates and contributors who should not depend on a preconfigured machine.
Next Steps After Installation
- Use the CLI overview to understand sync behavior and environment-specific outputs.
- Use the official trusted tools collection when you need higher-confidence installs for a shared stack.
- Use the agent workflows solution page when the next step is solving a concrete multi-tool workflow, not browsing more repositories.
Installation FAQ
Do I need a global install first?
No. The recommended path is npx, because it keeps setup lightweight and current.
How do I know the install really worked?
Check npx killer-skills list, confirm the IDE-native files were written, and verify the skill is available inside your assistant.
What should I do after the first successful install?
Move into the CLI overview, a trusted collection, or an agent workflow solution page so you can turn installation into a repeatable operating path.