skillshare
Manages and syncs AI CLI skills and agents across 50+ tools from a single source. Use this skill whenever the user mentions "skillshare", runs skillshare commands, manages skills or agents (install, update, uninstall, sync, commit, audit, analyze, check, diff, search), or troubleshoots skill/agent configuration (orphaned symlinks, broken targets, sync issues). Covers both global (~/.config/skillshare/) and project (.skillshare/) modes. Also use when: adding new AI tool targets (Claude, Cursor, Windsurf, etc.), setting target include/exclude filters or copy vs symlink mode, using backup/restore
npx skills add runkids/skillshare --skill skillshare --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Skillshare CLI Global: `~/.config/skillshare/skills/` → all AI CLIs. Project: `.skillshare/skills/` → repo-local. Auto-detects project mode when `.skillshare/config.yaml` exists. Force with `-p` or `-g`. ## Recipes ### Getting Started ```bash skillshare init --no-copy --all-targets --git --skill # Fresh global setup skillshare init -p --targets "claude,cursor" # Fresh project setup skillshare init --copy-from claude --all-targets --git # Import from existing CLI skillshare init --discover --select "windsurf" # Add new AI tool later ``` ### Installing Skills ```bash skillshare install user/repo -s pdf,commit # Select specific skills skillshare install user/repo --all # Install everything skillshare install user/repo --into frontend # Place in subdirectory skillshare install gitlab.com/team/repo # Any Git host skillshare install user/repo --track # Enable `update` later skillshare install user/repo -b develop --all # Install from branch skillshare install user/repo --track -b develop # Track specific branch skillshare install user/repo -s pdf -p # Install to project skillshare install # Rehydrate remote skills/tracked repos skillshare sync # Always sync after install ``` ### Extras
- Recipes
- Getting Started
- Installing Skills
- Extras (Rules, Commands, Prompts)
- Extensions (Content Transformation)
- Creating & Discovering Skills
- Removing Skills
- Enable / Disable Skills
- Team / Organization
- Skill Hubs
- Controlling Where Skills Go
- Updates & Maintenance
- Scripting & CI/CD
- Recovery & Troubleshooting
skillshare init --no-copy --all-targets --git --skill # Fresh global setup skillshare init -p --targets "claude,cursor" # Fresh project setup skillshare init --copy-from claude --all-targets --git # Import from existing CLI skillshare init --discover --select "windsurf" # Add new AI tool later skillshare install user/repo -s pdf,commit # Select specific skills skillshare install user/repo --all # Install everything skillshare install user/repo --into frontend # Place in subdirectory skillshare install gitlab.com/team/repo # Any Git host skillshare install user/repo --track # Enable `update` later skillshare install user/repo -b develop --all # Install from branch
What does the skillshare skill do?
Manages and syncs AI CLI skills and agents across 50+ tools from a single source. Use this skill whenever the user mentions "skillshare", runs skillshare commands, manages skills or agents (install, update, uninstall, sync, commit, audit, analyze, check, diff, search), or troubleshoots skill/agent configuration (orphaned symlinks, broken targets, sync issues). Covers both global (~/.config/skillshare/) and project (.skillshare/) modes. Also use when: adding new AI tool targets (Claude, Cursor, Windsurf, etc.), setting target include/exclude filters or copy vs symlink mode, using backup/restore
How do I install it?
Run `npx skills add runkids/skillshare --skill skillshare --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From runkids/skillshare, a repository with 2,519 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.