### Global Skill Installation Examples

Source: https://github.com/runkids/skillshare/blob/main/skills/skillshare/references/install.md

Examples of installing skills globally using the 'skillshare install' command with different source formats and options.

```bash
# Global
skillshare install anthropics/skills              # Browse official skills
skillshare install anthropics/skills/skills/pdf   # Direct install
skillshare install ~/Downloads/my-skill           # Local
skillshare install github.com/team/repo --track   # Team repo
skillshare install                                # Install all remote skills from config
```

--------------------------------

### New Machine Setup with Config Install

Source: https://github.com/runkids/skillshare/blob/main/website/docs/reference/commands/install.md

Demonstrates setting up a new machine by installing all skills from the global config and syncing.

```bash
skillshare install       # Installs all skills from config
```

```bash
skillshare sync          # Sync to targets
```

--------------------------------

### Project-Based Skill Installation Examples

Source: https://github.com/runkids/skillshare/blob/main/skills/skillshare/references/install.md

Examples of installing skills within a project context using the '-p' flag with the 'skillshare install' command.

```bash
# Project
skillshare install anthropics/skills/skills/pdf -p    # Install to .skillshare/skills/
skillshare install github.com/team/repo --track -p    # Track in project
skillshare install -p                                 # Install all remote skills from config
```

--------------------------------

### Initial Setup on Machine A

Source: https://github.com/runkids/skillshare/blob/main/website/docs/how-to/recipes/cross-machine-sync-recipe.md

Initialize skillshare, install skills, and push the source directory to a git remote.

```bash
skillshare init

skillshare install your-org/team-skills
skillshare install another/repo --into tools

skillshare push
```

--------------------------------

### Install with a custom name (single skill)

Source: https://github.com/runkids/skillshare/blob/main/website/docs/reference/commands/install.md

This example shows a successful single-skill installation with a custom name.

```bash
skillshare install comeonzhj/Auto-Redbook-Skills --name haha
```

--------------------------------

### Global Init: Fresh Start

Source: https://github.com/runkids/skillshare/blob/main/skills/skillshare/references/init.md

Use this command to start with an empty skill source, set up all detected targets, initialize a git repository, and install the built-in skillshare skill.

```bash
skillshare init --no-copy --all-targets --git --skill
```

--------------------------------

### Setup Local Skill Source Directory

Source: https://github.com/runkids/skillshare/blob/main/ai_docs/tests/local_install_source_preservation_runbook.md

Creates a directory with a sample skill, including a SKILL.md and README.md file, to test local installation preservation.

```bash
rm -rf /tmp/ss-local-src /tmp/ss-local-multi
mkdir -p /tmp/ss-local-src/my-precious-skill
cat > /tmp/ss-local-src/my-precious-skill/SKILL.md << 'EOF'
---
name: my-precious-skill
description: Test skill that must not be deleted
---
# My Precious Skill
This file must survive installation.
EOF
echo "important data" > /tmp/ss-local-src/my-precious-skill/README.md
ls -la /tmp/ss-local-src/my-precious-skill/
```

--------------------------------

### Setup on New Machine B

Source: https://github.com/runkids/skillshare/blob/main/website/docs/how-to/recipes/cross-machine-sync-recipe.md

Install skillshare, initialize it, pull changes from the git remote, and sync to local targets.

```bash
curl -fsSL https://raw.githubusercontent.com/runkids/skillshare/main/install.sh | sh

skillshare init

pull

skillshare sync
```

--------------------------------

### Setup: Install multiple skills

Source: https://github.com/runkids/skillshare/blob/main/ai_docs/tests/uninstall_all_glob_runbook.md

Installs multiple skills from the same repository, including one with a `--into` flag for a specific project directory. Verifies installation by listing skills in configuration and Claude directories.

```bash
# Setup hook already ran ss init
# Batch install from same repo using -s
ss install sickn33/antigravity-awesome-skills -s pdf-official,tdd-workflow
ss install sickn33/antigravity-awesome-skills -s react-best-practices --into frontend --force
ss sync
```

```bash
ls ~/.config/skillshare/skills/
ls -la ~/.claude/skills/
```

--------------------------------

### CI/CD Example: Bitbucket Pipelines

Source: https://github.com/runkids/skillshare/blob/main/website/docs/reference/commands/install.md

Example of installing shared skills in Bitbucket Pipelines, using environment variables for authentication.

```yaml
- step:
    name: Install shared skills
    script:
      - skillshare install https://bitbucket.org/team/skills.git --track
    env:
      BITBUCKET_USERNAME: $BITBUCKET_USERNAME   # for app passwords
      BITBUCKET_TOKEN: $BITBUCKET_TOKEN
```

--------------------------------

### Cross-Machine Sync: Initial Setup (Non-Interactive)

Source: https://github.com/runkids/skillshare/blob/main/website/docs/getting-started/quick-reference.md

Initialize skillshare for cross-machine synchronization non-interactively, automatically detecting installed targets and skipping local copy.

```bash
skillshare init --remote git@github.com:you/my-skills.git --no-copy --all-targets --no-skill
```

--------------------------------

### Install skillshare CLI

Source: https://github.com/runkids/skillshare/blob/main/website/docs/intro.md

Installs the skillshare CLI tool using a curl script. This is the initial setup step.

```bash
# Install
curl -fsSL https://raw.githubusercontent.com/runkids/skillshare/main/install.sh | sh
```

--------------------------------

### Basic Install

Source: https://github.com/runkids/skillshare/blob/main/website/docs/reference/commands/install.md

Installs a skill from a given source URL.

```bash
skillshare install anthropics/skills/skills/pdf --update
```

--------------------------------

### New Team Member Setup

Source: https://github.com/runkids/skillshare/blob/main/website/docs/how-to/daily-tasks/project-workflow.md

When a new team member joins, they clone the project, install remote skills listed in the config, and sync to targets.

```bash
git clone github.com/team/project
cd project
skillshare install -p
skillshare sync
```

--------------------------------

### Typical Daily Workflow

Source: https://github.com/runkids/skillshare/blob/main/website/docs/reference/commands/pull.md

This example shows a common workflow for starting the day by pulling the latest skills and ending the day by collecting and pushing any new skills created.

```bash
skillshare pull
```

```bash
skillshare collect claude
```

```bash
skillshare push -m "Add new skill"
```

--------------------------------

### Install from Azure DevOps Server (With Config)

Source: https://github.com/runkids/skillshare/blob/main/website/docs/reference/targets/configuration.md

Example of installing a repository from a self-hosted Azure DevOps Server when `azure_hosts` is configured. The URL is correctly parsed, extracting the organization, project, and repository.

```bash
# Correctly parsed — clone URL is
# https://azuredevops.mycompany.com/Org/Project/_git/Repo
skillshare install https://azuredevops.mycompany.com/Org/Project/_git/Repo
```

--------------------------------

### Install, Initialize, and Sync Skillshare

Source: https://github.com/runkids/skillshare/blob/main/website/docs/getting-started/index.md

This sequence of commands installs skillshare, initializes it by detecting AI CLIs, and syncs your skills to all targets. Ensure you have curl installed for the installation step.

```bash
curl -fsSL https://raw.githubusercontent.com/runkids/skillshare/main/install.sh | sh
```

```bash
skillshare init
```

```bash
skillshare sync
```

--------------------------------

### Preview Skill Installation

Source: https://github.com/runkids/skillshare/blob/main/website/docs/how-to/daily-tasks/skill-discovery.md

Use the '--dry-run' flag to preview which files would be installed without actually installing them. This is useful for evaluation.

```bash
skillshare install anthropics/skills/skills/pdf --dry-run
```

--------------------------------

### Install Skills with Various Flags

Source: https://github.com/runkids/skillshare/blob/main/skills/skillshare/references/install.md

Use the `install` command with flags to control installation behavior, such as specifying the project, overriding names, forcing overwrites, updating existing skills, tracking repositories, selecting specific skills, installing into subdirectories, installing all skills, auto-accepting prompts, excluding skills, skipping audits, setting audit thresholds, and performing dry runs.

```bash
skillshare install user/repo --exclude debug --exclude experimental
```

--------------------------------

### Install Skill with Grouping

Source: https://github.com/runkids/skillshare/blob/main/website/docs/understand/declarative-manifest.md

Demonstrates installing a skill and automatically recording its group in the manifest.

```bash
skillshare install anthropics/skills/skills/pdf --into frontend -p
# config.yaml will contain: name: pdf, group: frontend
```

--------------------------------

### First Install to Populate .gitignore

Source: https://github.com/runkids/skillshare/blob/main/ai_docs/tests/gitignore_batch_perf_runbook.md

Performs the first installation of a feature, which populates the .gitignore file with managed entries. Verifies successful installation.

```bash
cd ~/test-project
ss install runkids/feature-radar -y -p
```

--------------------------------

### Basic Initialization

Source: https://github.com/runkids/skillshare/blob/main/website/docs/reference/commands/init.md

Run `skillshare init` for interactive setup. Use `--dry-run` to preview changes without applying them.

```bash
skillshare init              # Interactive setup
```

```bash
skillshare init --dry-run    # Preview without changes
```

--------------------------------

### Selective Skill Installation

Source: https://github.com/runkids/skillshare/blob/main/skills/skillshare/references/install.md

Examples of performing selective installs, including specifying skills by name, installing all skills, auto-accepting prompts, and skipping audits.

```bash
# Selective install (non-interactive)
skillshare install anthropics/skills -s pdf,commit    # Specific skills
skillshare install anthropics/skills --all            # All skills
skillshare install anthropics/skills -y               # Auto-accept
skillshare install anthropics/skills -s pdf -p        # Selective + project mode
skillshare install user/repo --skip-audit             # Skip security scan
```

--------------------------------

### Install Skills

Source: https://github.com/runkids/skillshare/blob/main/website/docs/reference/commands/index.md

Installs a skill from a GitHub repository or a local path. Use --track to monitor the installed skill for updates.

```bash
skillshare install anthropics/skills/skills/pdf
```

```bash
skillshare install github.com/team/skills --track
```

--------------------------------

### Install All Skills from Configuration

Source: https://github.com/runkids/skillshare/blob/main/website/docs/reference/commands/install.md

Installs all skills defined in the project's configuration file. This command is used when no specific arguments are provided, indicating a desire to install everything configured.

```bash
skillshare install
```

--------------------------------

### Setup: Initialize and Create Extras Source Directories

Source: https://github.com/runkids/skillshare/blob/main/ai_docs/tests/sync_extras_runbook.md

Cleans up existing extras and target directories, then creates new source directories for rules and commands with initial files. Use `ss` or `skillshare` as the command alias.

```bash
# Clean pre-existing extras and target dirs from ssenv --init
ss extras remove rules --force -g 2>/dev/null || true
rm -rf ~/.claude/rules ~/.continue/rules ~/.claude/commands 2>/dev/null || true
# Create extras source dirs using new layout
mkdir -p ~/.config/skillshare/extras/rules
mkdir -p ~/.config/skillshare/extras/commands
echo "# Always use TDD" > ~/.config/skillshare/extras/rules/tdd.md
echo "# Error handling" > ~/.config/skillshare/extras/rules/errors.md
echo "# Deploy command" > ~/.config/skillshare/extras/commands/deploy.md
```

--------------------------------

### Install skillshare in Dev Container

Source: https://github.com/runkids/skillshare/blob/main/website/docs/learn/with-devcontainer.md

Add this to your `.devcontainer/devcontainer.json` to install skillshare and initialize it when the container is created. It installs skillshare, runs `init` non-interactively, and syncs skills.

```json
{
  "postCreateCommand": "curl -fsSL https://raw.githubusercontent.com/runkids/skillshare/main/install.sh | sh && skillshare init --no-copy --all-targets --no-skill && skillshare sync"
}
```

--------------------------------

### Install Project Dependencies

Source: https://github.com/runkids/skillshare/blob/main/website/README.md

Run this command to install all necessary project dependencies.

```bash
npm install
```

--------------------------------

### Project Mode Install Mixed Repo

Source: https://github.com/runkids/skillshare/blob/main/ai_docs/tests/install_mixed_repo_agents_runbook.md

Initializes a project and then installs a mixed repository in project mode. This tests the installation of skills and agents into the project-specific directories.

```bash
rm -rf /tmp/test-project
mkdir -p /tmp/test-project
cd /tmp/test-project
ss init -p --targets claude 2>&1
ss install -p file:///tmp/mixed-repo --yes --force 2>&1
```

--------------------------------

### CI/CD Example: Azure Pipelines

Source: https://github.com/runkids/skillshare/blob/main/website/docs/reference/commands/install.md

Example of installing shared skills in Azure Pipelines, using a system access token for authentication.

```yaml
- script: skillshare install https://dev.azure.com/org/project/_git/skills --track
  env:
    AZURE_DEVOPS_TOKEN: $(System.AccessToken)
```

--------------------------------

### CI/CD Example: GitHub Actions

Source: https://github.com/runkids/skillshare/blob/main/website/docs/reference/commands/install.md

Example of installing shared skills in a GitHub Actions workflow, using a GitHub token for authentication.

```yaml
- name: Install shared skills
  env:
    GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
  run: skillshare install https://github.com/org/skills.git --track
```

--------------------------------

### Manual Clone and Initialize

Source: https://github.com/runkids/skillshare/blob/main/website/docs/how-to/sharing/cross-machine-sync.md

Alternative setup for a new machine: manually clone the repository and then initialize Skillshare with the existing source.

```bash
git clone git@github.com:you/my-skills.git ~/.config/skillshare/skills
skillshare init --source ~/.config/skillshare/skills
skillshare sync
```

--------------------------------

### Install and Sync a Skill

Source: https://github.com/runkids/skillshare/blob/main/website/docs/getting-started/quick-reference.md

Use these commands to install a new skill and then sync it to your targets.

```bash
skillshare install anthropics/skills/skills/pdf
skillshare sync
```

--------------------------------

### CI/CD Example: GitLab CI

Source: https://github.com/runkids/skillshare/blob/main/website/docs/reference/commands/install.md

Example of installing shared skills in a GitLab CI pipeline, using the CI job token for authentication.

```yaml
install-skills:
  script:
    - skillshare install https://gitlab.com/org/skills.git --track
  variables:
    GITLAB_TOKEN: $CI_JOB_TOKEN
```

--------------------------------

### Verbose output example

Source: https://github.com/runkids/skillshare/blob/main/website/docs/reference/commands/list.md

The `--verbose` flag provides a detailed, plain text view of installed skills, including their source, type, and installation date.

```bash
skillshare list --verbose
```

--------------------------------

### Install skillshare and Initialize

Source: https://github.com/runkids/skillshare/blob/main/website/blog/2026-02-26-migrate-from-vercel-skills.md

Installs the skillshare binary using a curl script and then initializes the tool in the current directory. This is the first step when migrating from vercel/skills.

```bash
curl -fsSL https://raw.githubusercontent.com/runkids/skillshare/main/install.sh | sh
skillshare init
```

--------------------------------

### Install Skills from Bare Repository

Source: https://github.com/runkids/skillshare/blob/main/ai_docs/tests/update_prune_check_stale_runbook.md

Installs two skills from a local file-based Git repository using the `ss install` command. Skips audit and applies global flags.

```bash
REMOTE=~/remote-multi.git
ss install "file://$REMOTE//skills/keep-skill" -g --skip-audit
ss install "file://$REMOTE//skills/doomed-skill" -g --skip-audit
echo "=== Installed ==="
ls ~/.config/skillshare/skills/
```

--------------------------------

### Example of Successful Completion Installation

Source: https://github.com/runkids/skillshare/blob/main/website/docs/reference/commands/completion.md

This output indicates that the completion script has been successfully installed to the standard path. It also provides a command to manually source the script if needed.

```bash
$ skillshare completion bash --install
✔ Completion script installed to /home/user/.local/share/bash-completion/completions/skillshare

ℹ Restart your shell or run:
  source /home/user/.local/share/bash-completion/completions/skillshare
```

--------------------------------

### Start the Skillshare Playground

Source: https://github.com/runkids/skillshare/blob/main/website/docs/learn/with-playground.md

Builds the sandbox, compiles the binary, initializes global mode, creates demo content, and drops you into an interactive shell.

```bash
cd skillshare
make playground
```

--------------------------------

### Install a skill and sync to targets

Source: https://github.com/runkids/skillshare/blob/main/website/docs/reference/commands/install.md

After installing a skill, it's crucial to run the `skillshare sync` command to distribute the installed skill to its designated targets. This ensures the skill is available where needed.

```bash
skillshare install anthropics/skills/skills/pdf
skillshare sync  # ← Don't forget!
```

--------------------------------

### Install and Initialize Skillshare

Source: https://github.com/runkids/skillshare/blob/main/website/docs/how-to/recipes/team-onboarding-recipe.md

This script installs the skillshare tool, initializes it, installs organization-wide skills, runs a security audit, and syncs skills to all AI tools. It's designed to be run by a new team member.

```bash
#!/bin/bash
set -e

echo "Installing skillshare..."
curl -fsSL https://raw.githubusercontent.com/runkids/skillshare/main/install.sh | sh

echo "Initializing..."
skillshare init

echo "Installing organization skills..."
skillshare install your-org/org-skills

echo "Running security audit..."
skillshare audit

echo "Syncing to all AI tools..."
skillshare sync

echo "Done! Run 'skillshare list' to see installed skills."
```

--------------------------------

### Onboarding with Skillshare

Source: https://github.com/runkids/skillshare/blob/main/website/docs/how-to/sharing/project-setup.md

New team members can quickly set up all project skills by cloning the repo and running `skillshare install -p && skillshare sync`. This command automatically installs all skills listed in `.skillshare/config.yaml`.

```bash
git clone github.com/team/my-project
cd my-project
skillshare install -p && skillshare sync
```

--------------------------------

### Install from GitLab with Nested Subgroups (With Config)

Source: https://github.com/runkids/skillshare/blob/main/website/docs/reference/targets/configuration.md

Example of installing a repository from a self-managed GitLab instance when `gitlab_hosts` is configured. The full path is correctly interpreted as the repository, supporting nested subgroups.

```bash
# git.company.com/team/frontend/ui → clones "team/frontend/ui" (full path)
skillshare install git.company.com/team/frontend/ui
```

--------------------------------

### Setup: Create Skill and Remove Target Directory

Source: https://github.com/runkids/skillshare/blob/main/ai_docs/tests/auto_create_target_dir_runbook.md

Creates a test skill directory and its markdown file, then verifies its existence. This step prepares the environment for subsequent sync operations.

```bash
mkdir -p ~/.config/skillshare/skills/test-skill
cat > ~/.config/skillshare/skills/test-skill/SKILL.md << 'SKILL'
---
name: test-skill
description: Test skill for auto-create
---
# Test Skill
SKILL
ls ~/.config/skillshare/skills/test-skill/SKILL.md
```

--------------------------------

### Setup Environment and Simulated Git Repo

Source: https://github.com/runkids/skillshare/blob/main/ai_docs/tests/collect_nested_git_repo_runbook.md

Initializes the environment, sets up source and target paths, and creates a simulated git-cloned repository with nested skill files and directories. This step is crucial for testing the `collect` functionality.

```bash
# Clean any stale state
ss extras remove rules --force -g 2>/dev/null || true
rm -rf ~/.claude/rules 2>/dev/null || true

# Init skillshare with claude target only
ss init --no-copy --all-targets --no-git --no-skill --force 2>/dev/null || true

# Get source and target paths
SOURCE=$(ss status --json | jq -r '.source.path')
TARGET=$(ss status --json | jq -r '.targets[] | select(.name == "claude") | .path')

echo "SOURCE=$SOURCE"
echo "TARGET=$TARGET"

# Ensure target dir exists
mkdir -p "$TARGET"

# Create a simulated git-cloned multi-skill repo in the target
REPO="$TARGET/superpowers"
mkdir -p "$REPO/.git/objects/pack"
mkdir -p "$REPO/.git/refs/heads"
mkdir -p "$REPO/skills/brainstorming"
mkdir -p "$REPO/skills/debugging/prompts"
mkdir -p "$REPO/skills/tdd/templates/go"
mkdir -p "$REPO/commands/commit"
mkdir -p "$REPO/docs"

# .git metadata files
echo "ref: refs/heads/main" > "$REPO/.git/HEAD"
echo "[core]\n\trepositoryformatversion = 0" > "$REPO/.git/config"
echo "pack-data" > "$REPO/.git/objects/pack/pack-abc.pack"

# Skill files (nested 2-3 levels deep)
echo "# Brainstorming Skill" > "$REPO/skills/brainstorming/SKILL.md"
echo "---\nname: brainstorming
---" > "$REPO/skills/brainstorming/SKILL.md"

echo "# Debugging Skill" > "$REPO/skills/debugging/SKILL.md"
echo "debug prompt" > "$REPO/skills/debugging/prompts/default.md"

echo "# TDD Skill" > "$REPO/skills/tdd/SKILL.md"
echo "go test template" > "$REPO/skills/tdd/templates/go/test.md"

echo "// commit command" > "$REPO/commands/commit/index.js"

echo "# Superpowers Docs" > "$REPO/docs/README.md"

# Root-level file
echo "// gemini extension" > "$REPO/gemini-extension.js"

# Verify structure
find "$REPO" -not -path '*/.git/*' -not -path '*/.git' | sort
```

--------------------------------

### Skillshare Metadata File Example

Source: https://github.com/runkids/skillshare/blob/main/website/docs/reference/appendix/file-structure.md

Example content for the Skillshare metadata file, which stores information about installed and tracked skills. This file is auto-managed and should not be edited manually. It's stored within the source directory for synchronization.

```json
{
  "skills": [
    {
      "name": "pdf",
      "source": "anthropics/skills/skills/pdf"
    },
    {
      "name": "_team-skills",
      "source": "github.com/team/skills",
      "tracked": true
    }
  ]
}
```

--------------------------------

### Initialize Skillshare

Source: https://github.com/runkids/skillshare/blob/main/website/docs/reference/commands/index.md

Sets up skillshare for the first time. Can optionally specify a remote repository for skills.

```bash
skillshare init
```

```bash
skillshare init --remote git@github.com:you/skills.git
```

--------------------------------

### Manual Skillshare Setup in GitHub Actions

Source: https://github.com/runkids/skillshare/blob/main/website/docs/how-to/recipes/ci-cd-skill-validation.md

Manually install and configure skillshare within a GitHub Actions job if you prefer not to use the dedicated action. This involves downloading the install script and running initialization commands.

```yaml
jobs:
  validate:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4
      - run: curl -fsSL https://raw.githubusercontent.com/runkids/skillshare/main/install.sh | sh
      - run: skillshare init --no-copy --all-targets --no-git --no-skill --source ./skills
      - run: skillshare audit --threshold high --format json
      - run: skillshare sync --dry-run
```

--------------------------------

### Setup Extras Source with New Path Layout

Source: https://github.com/runkids/skillshare/blob/main/ai_docs/tests/extras_refactor_json_runbook.md

Creates the directory structure and initial markdown files for extras using the new `extras/<name>/` layout.

```bash
rm -rf ~/.config/skillshare/extras/rules
mkdir -p ~/.config/skillshare/extras/rules
echo "# TDD rules" > ~/.config/skillshare/extras/rules/tdd.md
echo "# Error handling" > ~/.config/skillshare/extras/rules/errors.md
```

--------------------------------

### Build and Start Development Container

Source: https://github.com/runkids/skillshare/blob/main/website/docs/how-to/advanced/docker-sandbox.md

Use this command to build the Docker image, start the container, set up the environment, and enter the shell. The first run may take a few minutes.

```bash
make devc            # build image → start container → setup → enter shell
```

--------------------------------

### Skillignore File Example

Source: https://github.com/runkids/skillshare/blob/main/website/docs/how-to/daily-tasks/best-practices.md

Use a `.skillignore` file to prevent internal or work-in-progress skills from being publicly discovered or installed.

```text
# Hide from public discovery
_internal-scripts
test-*
wip-feature
```

--------------------------------

### Install from Azure DevOps Server (Without Config)

Source: https://github.com/runkids/skillshare/blob/main/website/docs/reference/targets/configuration.md

Example of installing a repository from a self-hosted Azure DevOps Server without `azure_hosts` configured. The URL falls through to generic HTTPS parsing, resulting in an incorrect clone URL.

```bash
# Falls through to generic HTTPS parsing — clone URL becomes
# https://azuredevops.mycompany.com/Org/Project.git (WRONG)
skillshare install https://azuredevops.mycompany.com/Org/Project/_git/Repo
```

--------------------------------

### Create Project with Skill and Sync

Source: https://github.com/runkids/skillshare/blob/main/ai_docs/tests/relative_symlinks_runbook.md

Initializes a project directory, creates a demo skill, configures sync targets, and performs a project-mode sync. Ensure the directory is clean before execution.

```bash
rm -rf /tmp/reltest 2>/dev/null
mkdir -p /tmp/reltest/.skillshare/skills/demo
printf '%s\n' '---' 'name: demo' '---' '# Demo skill' > /tmp/reltest/.skillshare/skills/demo/SKILL.md
printf '%s\n' 'targets:' '  - claude' > /tmp/reltest/.skillshare/config.yaml
cd /tmp/reltest && ss sync -p
```

--------------------------------

### Install from GitLab with Nested Subgroups (Without Config)

Source: https://github.com/runkids/skillshare/blob/main/website/docs/reference/targets/configuration.md

Example of installing a repository from a self-managed GitLab instance without `gitlab_hosts` configured. The path is parsed assuming a standard owner/repo split, potentially leading to incorrect repository cloning.

```bash
# git.company.com/team/frontend/ui → clones "team/frontend", subdir "ui"
skillshare install git.company.com/team/frontend/ui
```

--------------------------------

### New Team Member Onboarding with Project Config

Source: https://github.com/runkids/skillshare/blob/main/website/docs/reference/commands/install.md

Illustrates onboarding a new team member by cloning a project and installing project-specific skills from its config.

```bash
git clone github.com/team/project && cd project
```

```bash
skillshare install -p    # Install all remote skills from project config
```

```bash
skillshare sync
```

--------------------------------

### Direct Install from Local Path

Source: https://github.com/runkids/skillshare/blob/main/website/docs/reference/commands/install.md

Installs a skill from a local directory, using either a relative or absolute path.

```bash
skillshare install ~/Downloads/my-skill
```

```bash
skillshare install /absolute/path/to/skill
```

--------------------------------

### List installed skills

Source: https://github.com/runkids/skillshare/blob/main/website/docs/reference/commands/list.md

Use `skillshare list` to see all installed skills. This command defaults to an interactive TUI on a TTY, providing smart filtering and keyboard navigation. Use `--no-tui` to get plain text output.

```bash
skillshare list              # Interactive TUI (default on TTY)
```

```bash
skillshare list --verbose    # Detailed plain text view
```

```bash
skillshare list --json       # JSON output for CI/scripts
```

```bash
skillshare list --no-tui          # Plain text output
```

```bash
skillshare list --no-tui | less   # Pipe to pager manually
```

--------------------------------

### Setup: Create Symlinked Source Directory

Source: https://github.com/runkids/skillshare/blob/main/ai_docs/tests/symlinked_dir_sync_runbook.md

Creates a real skills directory with test skills and then creates a symlink to it, simulating a dotfiles manager setup. Verifies the symlink creation.

```bash
# Create the REAL skills directory in a "dotfiles" location
REAL_SOURCE="$HOME/dotfiles/skillshare-skills"
mkdir -p "$REAL_SOURCE"

# Create test skills in the REAL location
mkdir -p "$REAL_SOURCE/alpha"
cat > "$REAL_SOURCE/alpha/SKILL.md" << 'SKILLEOF'
---
name: alpha
description: Test skill alpha
---
# Alpha Skill
SKILLEOF

mkdir -p "$REAL_SOURCE/beta"
cat > "$REAL_SOURCE/beta/SKILL.md" << 'SKILLEOF'
---
name: beta
description: Test skill beta
---
# Beta Skill
SKILLEOF

mkdir -p "$REAL_SOURCE/group/nested"
cat > "$REAL_SOURCE/group/nested/SKILL.md" << 'SKILLEOF'
---
name: nested
description: Nested skill for flat-name test
---
# Nested Skill
SKILLEOF

# Symlink the config source dir to the real location
SYMLINK_SOURCE="$HOME/.config/skillshare/skills"
rm -rf "$SYMLINK_SOURCE"
ln -s "$REAL_SOURCE" "$SYMLINK_SOURCE"

# Verify symlink
ls -la "$SYMLINK_SOURCE"
readlink "$SYMLINK_SOURCE"
```

--------------------------------

### Force Upgrade Skillshare CLI

Source: https://github.com/runkids/skillshare/blob/main/website/docs/troubleshooting/common-errors.md

Use this command to force an upgrade of the Skillshare CLI. No specific setup is required beyond having the CLI installed.

```bash
skillshare upgrade --cli --force
```

--------------------------------

### Start Local Development Server

Source: https://github.com/runkids/skillshare/blob/main/website/README.md

Use this command to start the local development server for the website.

```bash
npm start
```

--------------------------------

### Custom Name for Tracked Repo

Source: https://github.com/runkids/skillshare/blob/main/website/docs/understand/tracked-repositories.md

Installs a tracked repository with a custom name, ensuring it starts with `_` and avoids path separators. Invalid names are rejected.

```bash
skillshare install github.com/team/skills --track --name acme-skills
# Installed as: _acme-skills/
```

--------------------------------

### Direct Install from Full URL

Source: https://github.com/runkids/skillshare/blob/main/website/docs/reference/commands/install.md

Installs a skill directly from a full URL, such as a GitHub repository URL.

```bash
skillshare install github.com/user/repo/path/to/skill
```

--------------------------------

### Initialize project mode extras

Source: https://github.com/runkids/skillshare/blob/main/ai_docs/tests/extras_commands_runbook.md

Set up a project directory and initialize project-specific extras using the '-p' flag. This involves creating a directory, changing into it, and then initializing the project rules.

```bash
rm -rf /tmp/extras-proj
mkdir -p /tmp/extras-proj
cd /tmp/extras-proj
ss init -p --targets claude
ss extras init proj-rules --target .claude/rules -p
```

--------------------------------

### Clean Environment Before Extras Setup

Source: https://github.com/runkids/skillshare/blob/main/ai_docs/tests/extras_commands_runbook.md

Cleans any pre-existing extras and configuration from the environment to ensure a fresh start. Redirects errors and ignores failures for robustness.

```bash
# Clean any pre-existing extras from ssenv --init
ss extras remove rules --force -g 2>/dev/null || true
rm -rf ~/.claude/rules 2>/dev/null || true
ss extras list -g --json
```

--------------------------------

### Setup Multi-Skill Local Repository

Source: https://github.com/runkids/skillshare/blob/main/ai_docs/tests/local_install_source_preservation_runbook.md

Creates a local repository containing multiple skills (alpha and beta) with their respective SKILL.md and data files for testing multi-skill discovery.

```bash
rm -rf /tmp/ss-local-multi
mkdir -p /tmp/ss-local-multi/alpha /tmp/ss-local-multi/beta
cat > /tmp/ss-local-multi/alpha/SKILL.md << 'EOF'
---
name: alpha
description: Alpha skill
---
# Alpha
EOF
cat > /tmp/ss-local-multi/beta/SKILL.md << 'EOF'
---
name: beta
description: Beta skill
---
# Beta
EOF
echo "alpha data" > /tmp/ss-local-multi/alpha/data.txt
echo "beta data" > /tmp/ss-local-multi/beta/data.txt
find /tmp/ss-local-multi -type f | sort
```

--------------------------------

### Install Repo3 and List Skills

Source: https://github.com/runkids/skillshare/blob/main/ai_docs/tests/discovery_skip_target_dotdirs_runbook.md

Installs skills from `repo3.git` and lists the discovered skills. This verifies that the `.skillshare/` directory is entirely skipped, and only the skill in the root is found.

```bash
ss install "file:///tmp/e2e-dotdir-test/repo3.git" --all --json 2>/dev/null | jq -r '.skills | sort | join(",")'
```

--------------------------------

### Install with JSON output

Source: https://github.com/runkids/skillshare/blob/main/website/docs/reference/commands/install.md

Use the `--json` flag to get machine-readable output. This implies `--force` and non-interactive selection when no specific filters are provided.

```bash
skillshare install anthropics/skills --json
```

--------------------------------

### Build and Serve Website

Source: https://github.com/runkids/skillshare/blob/main/website/README.md

Commands to build the website for production and serve it locally for preview.

```bash
npm run build
```

```bash
npm run serve
```

--------------------------------

### Run CI Image with Subcommands

Source: https://github.com/runkids/skillshare/blob/main/website/docs/how-to/advanced/docker-sandbox.md

Examples of running the CI image with different subcommands. The first audits skills with a threshold, and the second performs a dry-run installation of a repository.

```bash
# Audit with threshold
docker run --rm -v ./skills:/skills ghcr.io/runkids/skillshare-ci audit /skills --threshold HIGH

# Dry-run install to verify a repo
docker run --rm ghcr.io/runkids/skillshare-ci install org/repo --dry-run
```

--------------------------------

### Direct Install with Fuzzy Subdirectory Matching

Source: https://github.com/runkids/skillshare/blob/main/website/docs/reference/commands/install.md

Installs a skill using a subdirectory path. If the exact path doesn't exist, it matches by skill name.

```bash
skillshare install runkids/my-skills/vue-best-practices
```

--------------------------------

### Repository Skill Ignore File

Source: https://github.com/runkids/skillshare/blob/main/website/blog/2026-02-26-write-your-first-skill.md

Example of a `.skillignore` file used in a skill repository to exclude specific skills (e.g., internal testing or experimental ones) from being installed.

```text
# .skillignore — skills to exclude during install
internal-testing
experimental
debug-*

```

--------------------------------

### Install from Project Config

Source: https://github.com/runkids/skillshare/blob/main/website/docs/reference/commands/install.md

Installs all skills listed in the project's `.skillshare/config.yaml` file using the project mode flag.

```bash
skillshare install -p
```

--------------------------------

### Install to Project Mode

Source: https://github.com/runkids/skillshare/blob/main/website/docs/reference/commands/search.md

Install skills directly into the project configuration using the `--project` or `-p` flag. If the project is not initialized, `init -p` will be run automatically.

```bash
skillshare search pdf -p           # Search and install to project
skillshare search react --project  # Same thing, long flag
```

--------------------------------

### Discover and Add New AI CLIs

Source: https://github.com/runkids/skillshare/blob/main/website/docs/reference/commands/init.md

Initializes skillshare and then discovers and adds any newly installed AI CLIs to the existing configuration. This can be done for general initialization or project-level setup.

```bash
skillshare init --discover
skillshare init -p --discover
```

--------------------------------

### Verify init: config.yaml has no skills section

Source: https://github.com/runkids/skillshare/blob/main/ai_docs/tests/registry_yaml_split_runbook.md

Ensures that a fresh initialization of Skillshare results in an empty `config.yaml` and that `registry.yaml` is not yet created. This step confirms the starting state before any skills are installed.

```bash
# Cleanup /tmp/ from previous runs to ensure isolation
rm -rf /tmp/test-skill /tmp/proj-skill /tmp/project-test /tmp/remove-me /tmp/grouped-skill 2>/dev/null || true
# Setup hook already ran ss init; verify config is clean
cat ~/.config/skillshare/config.yaml
# registry.yaml may not exist yet (created on first install) — that is OK
ls ~/.config/skillshare/skills/registry.yaml 2>/dev/null || echo "registry not yet created (expected)"
```

--------------------------------

### Direct Install from GitHub with Subdirectory

Source: https://github.com/runkids/skillshare/blob/main/website/docs/reference/commands/install.md

Installs a skill from a GitHub repository, specifying a subdirectory within the repository.

```bash
skillshare install anthropics/skills/skills/pdf
```

```bash
skillshare install google-gemini/gemini-cli/packages/core/src/skills/builtin/skill-creator
```

--------------------------------

### JSON output for scripting

Source: https://github.com/runkids/skillshare/blob/main/website/docs/reference/commands/list.md

Use the `--json` flag to get output in JSON format, suitable for use in CI/CD pipelines or scripts. This example extracts the name, source, and type of each skill.

```bash
skillshare list --json | jq '.[].name'   # JSON for scripting
```

```bash
skillshare list --json | jq '.[] | {name, source, type}'
```

--------------------------------

### Generator SKILL.md Example

Source: https://github.com/runkids/skillshare/blob/main/website/docs/understand/philosophy/skill-design-patterns.md

Defines an 'rfc-writer' skill using the 'generator' pattern. It outlines the steps for generating RFC documents, including loading a style guide and template, gathering user input, and performing the generation.

```markdown
---
name: rfc-writer
description: >-
  Generates RFC documents following the team template. Use when user
  says "write an RFC", "new proposal", or "design doc".
pattern: generator
category: scaffold
---

# RFC Writer

## Steps

### Step 1: Load Style Guide

Read `references/style-guide.md` for formatting and naming rules.

### Step 2: Load Template

Read `assets/template.md` as the base structure.

### Step 3: Gather Input

Ask the user what they need generated. Collect all required variables.

### Step 4: Generate

Fill in the template following the style guide. Ensure all placeholders are replaced.

```

--------------------------------

### Configure include/exclude filters for a target

Source: https://github.com/runkids/skillshare/blob/main/website/docs/reference/commands/sync.md

Define 'include' and 'exclude' patterns in the target configuration to filter which skills are synced to a specific target. This example shows a 'codex' target that includes skills starting with 'codex-' or 'core-' and excludes none.

```yaml
targets:
  codex:
    path: ~/.codex/skills
    include: [codex-*, core-*]
```

--------------------------------

### Create a Simple Skill

Source: https://github.com/runkids/skillshare/blob/main/website/docs/reference/commands/new.md

This example demonstrates creating a basic skill named 'code-review' in the default global location. The output confirms the creation and provides next steps.

```bash
skillshare new code-review
```

--------------------------------

### Set Up Project with Flat Skill Paths

Source: https://github.com/runkids/skillshare/blob/main/ai_docs/tests/update_batch_subdir_path_runbook.md

Configures a local project to use skills from the monorepo, installing them at flat paths (e.g., `alpha/`) while `meta.Subdir` specifies the repository-internal path (e.g., `skills/alpha`). This setup is crucial for testing the path duplication bug.

```bash
PROJECT=~/test-project
REPO_URL="file://$HOME/monorepo-remote.git"
mkdir -p "$PROJECT/.skillshare/skills" "$PROJECT/.claude"
cat > "$PROJECT/.skillshare/config.yaml" <<CFG
targets:
  - claude
CFG
mkdir -p "$PROJECT/.claude/skills"

SKILLS_DIR="$PROJECT/.skillshare/skills"

for name in alpha beta gamma; do
  LOCAL="$SKILLS_DIR/$name"
  mkdir -p "$LOCAL"
  cp "$HOME/monorepo-work/skills/$name/SKILL.md" "$LOCAL/"

  cat > "$LOCAL/.skillshare-meta.json" <<META
{
  "source": "${REPO_URL}//skills/${name}",
  "type": "git",
  "repo_url": "$REPO_URL",
  "subdir": "skills/${name}",
  "installed_at": "2025-01-01T00:00:00Z"
}
META
done

echo "Installed skills:"
ls -1 "$SKILLS_DIR"
echo "---"
test ! -d "$SKILLS_DIR/skills" && echo "PASS: no skills/skills/ dir"
```

--------------------------------

### Upgrade examples

Source: https://github.com/runkids/skillshare/blob/main/website/docs/reference/commands/upgrade.md

Demonstrates various ways to use the `skillshare upgrade` command, including standard upgrades, dry runs, forced upgrades, and component-specific upgrades.

```bash
# Standard upgrade (both CLI and skill)
skillshare upgrade
```

```bash
# Preview what would be upgraded
skillshare upgrade --dry-run
```

```bash
# Force upgrade without prompts
skillshare upgrade --force
```

```bash
# Upgrade only the CLI binary
skillshare upgrade --cli
```

```bash
# Upgrade only the skillshare skill
skillshare upgrade --skill
```

--------------------------------

### Develop Frontend with Go Installed Locally

Source: https://github.com/runkids/skillshare/blob/main/website/docs/how-to/advanced/docker-sandbox.md

Starts both the Go API server and the Vite development server for frontend work. Changes in the UI will trigger hot module replacement (HMR). Note that Go code changes require manual server restarts.

```bash
make ui-dev              # starts Go API server + Vite dev server together
# Open http://localhost:5173
```

--------------------------------

### Install Skills into a Directory

Source: https://github.com/runkids/skillshare/blob/main/website/docs/reference/commands/list.md

Demonstrates how to use the `--into` flag during installation to organize skills into specific subdirectories. This affects how `skillshare list` groups them.

```bash
skillshare install owner/repo -s react-patterns --into frontend
skillshare install owner/repo -s vue-patterns --into frontend
```

--------------------------------

### Scripting and CI/CD with JSON Output

Source: https://github.com/runkids/skillshare/blob/main/skills/skillshare/SKILL.md

Utilize the `--json` flag for most commands to get structured output suitable for scripting and CI/CD pipelines. This includes status, check, sync, diff, install, update, uninstall, collect, target list, skill list, search, audit, and doctor commands.

```bash
skillshare status --json
skillshare check --json
skillshare sync --json
skillshare diff --json
skillshare install user/repo --json
skillshare update --all --json
skillshare uninstall my-skill --json
skillshare collect claude --json
skillshare target list --json
skillshare list --json
skillshare search react --json
skillshare audit --format json
skillshare doctor --json
```

--------------------------------

### Typical Skillshare Extras Workflow

Source: https://github.com/runkids/skillshare/blob/main/skills/skillshare/references/extras.md

A step-by-step example demonstrating the common workflow for creating, populating, syncing, and verifying extra resources.

```bash
# 1. Create an extra
skillshare extras init rules --target ~/.claude/rules --target ~/.cursor/rules

# 2. Add files to source
cp my-rule.md ~/.config/skillshare/extras/rules/

# 3. Sync to targets
skillshare sync extras

# 4. Verify
skillshare extras list
skillshare diff --extras

# 5. Or collect existing local files first
skillshare extras collect rules --from ~/.claude/rules
skillshare sync extras
```

--------------------------------

### Install Mixed Repo

Source: https://github.com/runkids/skillshare/blob/main/ai_docs/tests/install_mixed_repo_agents_runbook.md

Installs skills and agents from a local mixed repository using the `ss install` command. Ensures both skills and agents are detected and installed.

```bash
ss install -g file:///tmp/mixed-repo --yes --force
```

--------------------------------

### Skillshare Configuration File Example

Source: https://github.com/runkids/skillshare/blob/main/website/docs/reference/appendix/file-structure.md

Example content for the main Skillshare configuration file. Specifies source directories, targets, and ignore patterns. Use this to customize Skillshare's behavior and target deployments.

```yaml
# yaml-language-server: $schema=https://raw.githubusercontent.com/runkids/skillshare/main/schemas/config.schema.json
source: ~/.config/skillshare/skills
agents_source: ~/.config/skillshare/agents  # Optional; defaults to <source parent>/agents
mode: merge
targets:
  claude:
    path: ~/.claude/skills
    agents:                                 # Optional; enables agent sync for this target
      path: ~/.claude/agents
  cursor:
    path: ~/.cursor/skills
ignore:
  - "**/.DS_Store"
  - "**/.git/**"
```

--------------------------------

### Install an available skill

Source: https://github.com/runkids/skillshare/blob/main/website/docs/getting-started/first-sync.md

Browse and install skills from a repository. This command installs all skills from the 'anthropics/skills' repository.

```bash
skillshare install anthropics/skills
```

--------------------------------

### Create and Install Pure Agent Repo

Source: https://github.com/runkids/skillshare/blob/main/ai_docs/tests/install_mixed_repo_agents_runbook.md

Creates a new git repository containing only agents, then installs it using `ss install`. This tests the installation process for repositories exclusively containing agents.

```bash
rm -rf /tmp/agent-only-repo
mkdir -p /tmp/agent-only-repo/agents
cat > /tmp/agent-only-repo/agents/helper.md <<'EOF'
---
name: helper
description: A helper agent
---
# Helper Agent
EOF
cd /tmp/agent-only-repo && git init && git config user.email "test@test.com" && git config user.name "test" && git add -A && git commit -m "init" 2>&1
ss install -g file:///tmp/agent-only-repo --yes --force
```

--------------------------------

### Initialize Skillshare Configuration

Source: https://github.com/runkids/skillshare/blob/main/website/docs/troubleshooting/common-errors.md

Run this command when no configuration file exists. Use `--source` to specify a custom path for skills.

```bash
skillshare init
```

```bash
skillshare init --source ~/my-skills
```

--------------------------------

### Install GitHub subdir skill

Source: https://github.com/runkids/skillshare/blob/main/ai_docs/tests/issue46_install_update_optimization_runbook.md

Installs a skill from a GitHub subdirectory, verifying successful installation and metadata creation.

```bash
ss install -g https://github.com/runkids/claude-skill-registry/tree/main/skills/documents/atlassian-search
```

--------------------------------

### Full Skillshare Configuration Example

Source: https://github.com/runkids/skillshare/blob/main/website/docs/reference/targets/configuration.md

A comprehensive example of a skillshare config file, demonstrating various settings for source, mode, targets, skills, extras, and ignore patterns.

```yaml
# yaml-language-server: $schema=https://raw.githubusercontent.com/runkids/skillshare/main/schemas/config.schema.json
# Source directory (where you edit skills)
source: ~/.config/skillshare/skills

# Default sync mode for new targets
mode: merge

# Default target naming (flat or standard)
# target_naming: flat

# Targets (AI CLI skill directories)
targets:
  claude:
    path: ~/.claude/skills
    # mode: merge (inherits from default)

  codex:
    path: ~/.codex/skills
    mode: symlink  # Override default mode
    include: [codex-*] # merge/copy mode only

  cursor:
    path: ~/.cursor/skills
    mode: copy  # real files for Cursor
    exclude: [experimental-*] # merge/copy mode only

  # Custom target
  myapp:
    path: ~/apps/myapp/skills

# Remote skills — auto-managed by install/uninstall
skills:
  - name: pdf
    source: anthropics/skills/skills/pdf
  - name: _team-skills
    source: github.com/team/skills
    tracked: true

# Fold $HOME → ~ on save (dotfiles-friendly)
# preserve_tilde_on_save: true

# Custom agents source (optional, overrides default location)
agents_source: ~/my-agents

# Custom extras source (optional, overrides default location)
extras_source: ~/my-extras

# Non-skill resources to sync
extras:
  - name: rules
    source: ~/company-shared/rules   # optional per-extra override
    targets:
      - path: ~/.claude/rules
      - path: ~/.cursor/rules
        mode: copy

# Files to ignore during sync
ignore:
  - "**/.DS_Store"
  - "**/.git/**"
  - "**/node_modules/**"
  - "**/*.log"

```

--------------------------------

### Install a Subdir Skill

Source: https://github.com/runkids/skillshare/blob/main/ai_docs/tests/check_treehash_precision_runbook.md

Installs a specific skill from a monorepo using its GitHub path. Ensures the skill is installed globally.

```bash
ss install github.com/sickn33/antigravity-awesome-skills//skills/active-directory-attacks -g
```

--------------------------------

### Install Skills with Skillshare CLI

Source: https://github.com/runkids/skillshare/blob/main/skills/skillshare/SKILL.md

Install skills from a repository, with options to select specific skills (`-s`), install all (`--all`), place them in a subdirectory (`--into`), or install from a specific branch (`-b`). Use `--track` to enable future updates. Reinstall all tracked remotes with `skillshare install` and sync with `skillshare sync`.

```bash
skillshare install user/repo -s pdf,commit       # Select specific skills
```

```bash
skillshare install user/repo --all               # Install everything
```

```bash
skillshare install user/repo --into frontend     # Place in subdirectory
```

```bash
skillshare install gitlab.com/team/repo          # Any Git host
```

```bash
skillshare install user/repo --track             # Enable `update` later
```

```bash
skillshare install user/repo -b develop --all    # Install from branch
```

```bash
skillshare install user/repo --track -b develop  # Track specific branch
```

```bash
skillshare install user/repo -s pdf -p           # Install to project
```

```bash
skillshare install                               # Reinstall all tracked remotes from config
```

```bash
skillshare sync                                  # Always sync after install
```

--------------------------------

### Project Target List Example

Source: https://github.com/runkids/skillshare/blob/main/website/docs/reference/commands/target.md

This is an example output of the `skillshare target list -p` command, showing targets configured for the current project and their sync modes.

```text
Project Targets
  claude    .claude/skills (merge)
  cursor         .cursor/skills (merge)
  custom-tool    ./tools/ai/skills (merge)
```

--------------------------------

### Install agent with JSON output

Source: https://github.com/runkids/skillshare/blob/main/website/docs/reference/commands/install.md

For agent-only installs, the JSON output still uses the `skills` array to report installed names.

```bash
skillshare install github.com/user/agents --kind agent --json
```

--------------------------------

### Initialize with Custom Source Directory

Source: https://github.com/runkids/skillshare/blob/main/website/docs/reference/commands/init.md

Initializes skillshare using an existing directory as the source for skills, bypassing the default location.

```bash
skillshare init --source ~/.config/skillshare/skills
```

--------------------------------

### Build All Binaries

Source: https://github.com/runkids/skillshare/blob/main/website/docs/getting-started/quick-reference.md

Perform a full build of the skillshare CLI, including the frontend.

```bash
make build-all
```

--------------------------------

### Install a specific skill

Source: https://github.com/runkids/skillshare/blob/main/website/docs/getting-started/first-sync.md

Install a particular skill directly from its repository path. This command installs the 'pdf' skill from the 'anthropics/skills' repository.

```bash
skillshare install anthropics/skills/skills/pdf
```