Awesome-omni-skill reskill-usage
Teaches AI agents how to use reskill — a Git-based package manager for AI agent skills. Covers CLI commands, install formats, configuration, publishing, and common workflows.
git clone https://github.com/diegosouzapw/awesome-omni-skill
T=$(mktemp -d) && git clone --depth=1 https://github.com/diegosouzapw/awesome-omni-skill "$T" && mkdir -p ~/.claude/skills && cp -r "$T/skills/tools/reskill-usage" ~/.claude/skills/diegosouzapw-awesome-omni-skill-reskill-usage && rm -rf "$T"
skills/tools/reskill-usage/SKILL.mdreskill Usage Guide
reskill is a Git-based package manager for AI agent skills. It provides declarative configuration (
skills.json + skills.lock), flexible versioning, and multi-agent support for installing, managing, and sharing skills across projects and teams.
Requirements: Node.js >= 18.0.0
CLI usage: If
reskill is installed globally, use it directly. Otherwise use npx reskill@latest:
npm install -g reskill # Global install npx reskill@latest <command> # Or use npx directly (no install needed)
When to Use This Skill
Use this skill when the user:
- Wants to install, update, or manage AI agent skills
- Mentions
,skills.json
, or reskill-related conceptsskills.lock - Wants to publish a skill to a registry
- Asks about supported install formats (GitHub, GitLab, HTTP, OSS, registry, etc.)
- Encounters reskill-related errors or needs troubleshooting
- Wants to set up a project for skill management
- Asks about multi-agent skill installation (Cursor, Claude Code, Codex, etc.)
Quick Start
# Initialize a new project npx reskill@latest init # Install a skill npx reskill@latest install github:anthropics/skills/skills/frontend-design@latest # List installed skills npx reskill@latest list
Commands
| Command | Alias | Description |
|---|---|---|
| - | Initialize |
| - | Search for skills in the registry |
| | Install one or more skills |
| | List installed skills |
| - | Show skill details |
| | Update skills |
| - | Check for outdated skills |
| , , | Remove a skill |
| | Publish a skill to the registry ¹ |
| - | Authenticate with the registry ¹ |
| - | Remove stored authentication ¹ |
| - | Display current logged in user ¹ |
| - | Diagnose environment and check for issues |
| - | Install shell tab completion |
¹ Registry commands (
,publish,login,logout) require a private registry deployment. Not available for public use yet.whoami
Run
reskill <command> --help for complete options and detailed usage.
Common Options
| Option | Commands | Description |
|---|---|---|
| | Install without saving to (for personal skills) |
| , , | Install/manage skills globally (user directory) |
| | Specify target agents (e.g., , ) |
| | Installation mode: (default) or |
| | Install to all agents |
| , , | Skip confirmation prompts |
| | Force reinstall even if already installed |
| | Select specific skill(s) by name from a multi-skill repo |
| | List available skills in the repository without installing |
| | Registry URL override for registry-based installs |
| , , , | Output as JSON |
Source Formats
reskill supports installing skills from multiple sources:
# GitHub shorthand npx reskill@latest install github:user/skill@v1.0.0 # GitLab shorthand npx reskill@latest install gitlab:group/skill@latest # Full Git URL (HTTPS) npx reskill@latest install https://github.com/user/skill.git # Full Git URL (SSH) npx reskill@latest install git@github.com:user/skill.git # GitHub/GitLab web URL (with branch and subpath) npx reskill@latest install https://github.com/vercel-labs/agent-skills/tree/main/skills/web-design-guidelines # Custom registry (self-hosted GitLab, etc.) npx reskill@latest install gitlab.company.com:team/skill@v1.0.0 # HTTP/OSS archives npx reskill@latest install https://example.com/skills/my-skill-v1.0.0.tar.gz npx reskill@latest install oss://bucket/path/skill.tar.gz npx reskill@latest install s3://bucket/path/skill.zip # Registry-based (requires registry deployment) npx reskill@latest install @scope/skill-name@1.0.0 npx reskill@latest install skill-name # Install multiple skills at once npx reskill@latest install github:user/skill1 github:user/skill2@v1.0.0
Monorepo Support
For repositories containing multiple skills, specify the path to the skill directory:
# Shorthand format with subpath npx reskill@latest install github:org/monorepo/skills/planning@v1.0.0 npx reskill@latest install gitlab:company/skills/frontend/components@latest # URL format with subpath npx reskill@latest install https://github.com/org/monorepo.git/skills/planning@v1.0.0 npx reskill@latest install git@gitlab.company.com:team/skills.git/backend/apis@v2.0.0 # GitHub web URL automatically extracts subpath npx reskill@latest install https://github.com/org/monorepo/tree/main/skills/planning
Requirements: The specified directory must contain a valid
SKILL.md file following the Agent Skills Specification.
HTTP/OSS URL Support
Skills can be installed directly from HTTP/HTTPS URLs pointing to archive files:
| Format | Example | Description |
|---|---|---|
| HTTPS URL | | Direct download URL |
| Aliyun OSS | | Aliyun OSS URL |
| AWS S3 | | AWS S3 URL |
| OSS Protocol | | Shorthand for Aliyun OSS |
| S3 Protocol | | Shorthand for AWS S3 |
Supported archive formats:
.tar.gz, .tgz, .zip, .tar
Version Formats
| Format | Example | Description |
|---|---|---|
| Exact | | Lock to specific tag |
| Latest | | Get the latest tag |
| Range | | Semver compatible (>=2.0.0 <3.0.0) |
| Branch | | Specific branch |
| Commit | | Specific commit hash |
| (none) | - | Default branch (main) |
Configuration
skills.json
The project configuration file, created by
reskill init:
{ "skills": { "planning": "github:user/planning-skill@v1.0.0", "internal-tool": "internal:team/tool@latest" }, "registries": { "internal": "https://gitlab.company.com" }, "defaults": { "installDir": ".skills", "targetAgents": ["cursor", "claude-code"], "installMode": "symlink" } }
— Installed skill references (name → source ref)skills
— Custom Git registry aliasesregistries
— Where skills are stored (default:defaults.installDir
).skills
— Default agents to install todefaults.targetAgents
—defaults.installMode
(default, recommended) orsymlinkcopy
Environment Variables
| Variable | Description | Default |
|---|---|---|
| Global cache directory | |
| Auth token (takes precedence over ~/.reskillrc) | - |
| Default registry URL | |
| Enable debug logging | - |
| Disable colored output | - |
Multi-Agent Support
Skills are installed to
.skills/ by default and can be integrated with any agent:
| Agent | Path |
|---|---|
| Cursor | or |
| Claude Code | |
| Codex | |
| Windsurf | |
| GitHub Copilot | |
| OpenCode | |
Use
--agent to target specific agents, or --all to install to all detected agents:
# Install to specific agents reskill install github:user/skill -a cursor claude-code # Install to all detected agents reskill install github:user/skill --all
Publishing
Note: Publishing requires a private registry deployment.
Authentication
# Login with a token (obtain from the registry web UI) reskill login --registry <url> --token <token> # Check current login status reskill whoami # Logout reskill logout
Tokens are stored in
~/.reskillrc. You can also use the RESKILL_TOKEN environment variable (takes precedence, useful for CI/CD).
Registry URL resolution priority:
CLI option--registry
environment variableRESKILL_REGISTRY
indefaults.publishRegistryskills.json
Publishing a Skill
# Validate without publishing (recommended first step) reskill publish --dry-run # Publish the skill reskill publish # Publish from a specific directory reskill publish ./path/to/skill # Skip confirmation reskill publish -y
The skill directory must contain a valid
SKILL.md. A skill.json with name, version, and description is also required for publishing.
Common Workflows
First-Time Project Setup
# 1. Initialize the project reskill init -y # 2. Install skills your project needs reskill install github:user/skill1@v1.0.0 github:user/skill2@latest -y # 3. Verify installation reskill list # 4. Commit skills.json and skills.lock to version control # (These files ensure team members get the same skill versions)
Team Collaboration
When a teammate clones the project, they run:
# Reinstall all skills from skills.json (like npm install) reskill install
This reads
skills.json + skills.lock and installs the exact same versions.
Checking and Updating Skills
# Check which skills have newer versions reskill outdated # Update all skills reskill update # Update a specific skill reskill update skill-name
Global vs Project-Level Installation
| Scope | Flag | Directory | Use Case |
|---|---|---|---|
| Project | - | (in project) | Team-shared skills, committed to git |
| Global | | | Personal skills, available in all projects |
# Project-level (default) reskill install github:user/skill # Global (personal, all projects) reskill install github:user/skill -g # Personal project-level (not saved to skills.json) reskill install github:user/skill --no-save
Diagnosing Issues
# Run environment diagnostics reskill doctor # JSON output for programmatic use reskill doctor --json
The
doctor command checks: reskill version, Node.js version, Git availability, cache directory, skills.json validity, skills.lock sync, installed skills integrity, and network connectivity.
Troubleshooting
| Error Message | Cause | Solution |
|---|---|---|
| Project not initialized | Run |
| No registry configured for this scope | Check in or use full Git URL |
| Skill name doesn't exist in registry | Verify skill name; check |
| Requested version doesn't exist | Run to see available versions |
| Auth issue when publishing | Run ; check token scope |
| Stale authentication | Re-authenticate with |
| Cannot reach Git host or registry | Check network; run for diagnostics |
| Skill already installed | Use to reinstall |
Private Repositories
reskill uses your existing git credentials (SSH keys or credential helper). For CI/CD environments:
# GitLab CI git config --global url."https://gitlab-ci-token:${CI_JOB_TOKEN}@gitlab.company.com/".insteadOf "https://gitlab.company.com/"