home / skills / vdustr / vp-claude-code-marketplace / add-skill

add-skill skill

/plugins/vp-add-skill/skills/add-skill

This skill guides installing and tracking agent skills from git repositories, enabling easy registry management and updates across global and project scopes.

npx playbooks add skill vdustr/vp-claude-code-marketplace --skill add-skill

Review the files below or copy the command above to add this skill to your agents.

Files (4)
SKILL.md
3.5 KB
---
name: add-skill
description: This skill should be used when the user asks to "install a skill", "add skill from GitHub", "list available skills", "manage skills registry", or mentions "npx add-skill". Provides guidance for installing and tracking agent skills from git repositories.
---

# Add Skill

Install agent skills from any git repository using the `add-skill` CLI.

## When to Use

- Installing skills from GitHub or other git repositories
- Listing available skills from a repository before installation
- Managing skill installations across global and project scopes
- Tracking installed skills in a registry for updates

## Quick Start

### List Available Skills

```bash
npx add-skill vercel-labs/agent-skills --list
```

### Install a Skill

```bash
# Install globally (all projects)
npx add-skill vercel-labs/agent-browser --skill agent-browser --global

# Install to current project
npx add-skill vercel-labs/agent-browser --skill agent-browser
```

### Verify Installation

```bash
ls ~/.claude/skills/       # Global skills
ls .claude/skills/         # Project skills
```

## Source Formats

| Format | Example |
|--------|---------|
| GitHub shorthand | `vercel-labs/agent-skills` |
| Full GitHub URL | `https://github.com/vercel-labs/agent-skills` |
| Specific skill path | `vercel-labs/agent-skills/skills/skill-name` |
| GitLab URL | `https://gitlab.com/org/repo` |
| Any Git URL | `[email protected]:org/repo.git` |

## CLI Options

| Option | Description |
|--------|-------------|
| `-l, --list` | List available skills without installing |
| `-s, --skill <name>` | Install specific skill by name |
| `-g, --global` | Install to user directory (~/.claude/skills/) |
| `-a, --agent <agents...>` | Target specific agents (claude-code, cursor, etc.) |
| `-y, --yes` | Skip all confirmation prompts |
| `-h, --help` | Show help information |

## Installation Locations

| Scope | Path |
|-------|------|
| Project (default) | `.claude/skills/<name>/` |
| Global (`--global`) | `~/.claude/skills/<name>/` |

## Popular Skill Sources

| Source | Description |
|--------|-------------|
| `vercel-labs/agent-skills` | Vercel's curated skill collection |
| `vercel-labs/agent-browser` | Browser automation skill |

## Skill Registry

Track installed skills in a registry for long-term maintenance. After each installation, update the registry to enable batch updates later.

For detailed registry setup, format, and workflows, see **`references/registry.md`**.

### Quick Registry Update

```bash
# Set registry path
REGISTRY=~/.claude/skills/add-skill/registry.json  # Global

# Ensure directory exists
mkdir -p "$(dirname "$REGISTRY")"

# Initialize if needed
[ -f "$REGISTRY" ] || echo '{"$schema":"./registry.schema.json","version":"1.0","skills":{}}' > "$REGISTRY"

# Add skill entry
jq '.skills["agent-browser"] = {
  "source": "vercel-labs/agent-browser",
  "sourceUrl": "https://github.com/vercel-labs/agent-browser",
  "skillPath": "skills/agent-browser",
  "installedAt": "'$(date -u +%Y-%m-%dT%H:%M:%SZ)'"
} | .lastUpdated = "'$(date -u +%Y-%m-%dT%H:%M:%SZ)'"' \
"$REGISTRY" > tmp.json && mv tmp.json "$REGISTRY"
```

## Additional Resources

### Reference Files

- **`references/registry.md`** - Detailed registry setup, format, and maintenance workflows

### Schema Files

- **`registry.schema.json`** - JSON Schema for registry validation

## Notes

- The CLI auto-detects installed agents
- Skills are stored as `SKILL.md` files with YAML frontmatter
- Use `--global` for skills needed across all projects
- Use project-level for project-specific skills

Overview

This skill provides a CLI workflow to install and manage agent skills from any git repository. It handles listing available skills, installing to project or global scopes, and tracking installations in a registry for updates. Use it to quickly add capabilities to agents by pointing at GitHub, GitLab, or any git URL. The tool favors predictable locations so skills are easy to find and update.

How this skill works

The CLI inspects a repository (GitHub shorthand, full URL, or any git endpoint) to list discoverable skills and optionally install a named skill path. By default it installs into the current project's .claude/skills/ directory, or into ~/.claude/skills/ when --global is used. After installation you can update a JSON registry that records source, path, and timestamps to enable batch updates and maintenance. It also supports agent targeting so you can restrict installs to compatible agents.

When to use it

  • Add a skill from a GitHub repo or any git URL to a project
  • Install a skill globally for reuse across multiple projects
  • Preview available skills in a repository before installing
  • Register installed skills for future batch updates
  • Target installs to specific agents (e.g., claude-code, cursor)

Best practices

  • List available skills (--list) before installing to confirm paths and names
  • Prefer project-level installs for project-specific behavior and --global for shared utilities
  • Keep a registry file and update it after each install to enable consistent updates
  • Use --yes to script installations non-interactively in CI or automation
  • Pin a specific skill path or commit when reproducibility is required

Example use cases

  • Install a browser automation skill into a single project for testing
  • Globally install a shared utility skill so all projects can access it
  • Scan vercel-labs/agent-skills to pick a candidate skill and then install it
  • Automate onboarding by scripting npx add-skill ... --yes in a setup script
  • Maintain a registry of installed skills and run periodic batch updates

FAQ

How do I list skills in a repo without installing?

Run the CLI with --list to enumerate discoverable skills in the target repository.

Where are skills installed?

Project installs go to .claude/skills/<name>/ and global installs go to ~/.claude/skills/<name>/.

How can I keep track of installed skills?

Maintain a JSON registry that records the source, skillPath, and timestamps; update it after each install to enable batch updates.