mgiovani/ai-arsenal / skills/find-skills
find-skills
VerifiedSearch, install, update, and remove third-party Agent Skills from skills.sh or any GitHub/GitLab repo via the `npx skills` CLI. Use when the user wants to "find a skill", "install a skill from github", "search skills.sh", or add third-party capabilities to Claude Code/Cursor/other agents. Not for authoring new skills (see create-skill).
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 7.2 KB |
| evals/evals.json | config | 4.0 KB |
| evals/trigger-eval.json | config | 1.8 KB |
| references/commands.md | markdown | 6.6 KB |
| references/workflows.md | markdown | 6.4 KB |
references/workflows.md
View on GitHub# Workflows and best practices
Patterns for finding, evaluating, installing, and managing skills from outside this repo.
## Contents
- [Discovery patterns](#discovery-patterns)
- [Installation strategies](#installation-strategies)
- [Security review](#security-review)
- [Combining external skills with cc-arsenal](#combining-external-skills-with-cc-arsenal)
- [Managing updates and versions](#managing-updates-and-versions)
- [Publishing skills to skills.sh](#publishing-skills-to-skillssh)
---
## Discovery patterns
### By domain
```bash
# Frontend development
npx skills find react
npx skills find nextjs
npx skills find tailwind
npx skills find frontend
# Backend development
npx skills find api
npx skills find database
npx skills find authentication
# DevOps and infrastructure
npx skills find docker
npx skills find kubernetes
npx skills find ci-cd
# Testing
npx skills find testing
npx skills find playwright
npx skills find unit-test
```
### By task type
```bash
# Code quality
npx skills find "code review"
npx skills find linting
npx skills find refactoring
# Documentation
npx skills find documentation
npx skills find api-docs
# Security
npx skills find security
npx skills find vulnerability
```
### Browse known repositories
```bash
# Vercel's official collection (React, Next.js, design patterns)
npx skills add vercel-labs/agent-skills --list
# Anthropic's example skills
npx skills add anthropics/skills --list
# Any GitHub user's skills
npx skills add <username>/<repo> --list
```
---
## Installation strategies
### Global vs project scope
**Install globally** (`-g`) when the skill is:
- General-purpose (code review, testing patterns, git workflows)
- Applicable across all projects
- Personal productivity (not team-shared)
```bash
npx skills add owner/repo --skill code-review -a claude-code -g
```
**Install at project scope** (default) when the skill is:
- Framework-specific (React, Django, Rails patterns)
- Project-specific (custom API, internal tooling)
- Shared with team via version control
```bash
npx skills add owner/repo --skill nextjs-patterns -a claude-code
```
### Single agent vs multi-agent
Install to a single agent when only using one AI coding tool:
```bash
npx skills add owner/repo --skill my-skill -a claude-code
```
Install to multiple agents when using several tools:
```bash
npx skills add owner/repo --skill my-skill -a claude-code -a cursor -a codex
```
Install to all detected agents:
```bash
npx skills add owner/repo --skill my-skill
# The CLI auto-detects installed agents and prompts for selection
```
### Non-interactive installation (CI/CD)
For automated setups or scripts:
```bash
# Fully non-interactive
npx skills add owner/repo --skill my-skill -a claude-code -g -y
# Install everything
npx skills add owner/repo --all
```
---
## Security review
### Before installing an external skill
**Always review skill contents before installation.** Skills contain instructions that AI agents follow, which could include:
- Running arbitrary commands
- Modifying files
- Making network requests
- Installing dependencies
### Review checklist
1. Check the source repository: verify it's from a trusted author or organization.
2. List skills first: use `--list` to see what will be installed.
3. Read the SKILL.md: review the actual instructions before installing.
4. Check for scripts: look for `scripts/` directories that contain executable code.
5. Review references: check `references/` for any suspicious content.
```bash
# Step 1: List available skills
npx skills add owner/repo --list
# Step 2: Browse the repository on GitHub before installing
# https://github.com/owner/repo/tree/main/skills/
# Step 3: Install after review
npx skills add owner/repo --skill verified-skill -a claude-code
```
### Trust indicators
- Repository from a recognized organization (Vercel, Anthropic, etc.)
- High install count on skills.sh
- Active maintenance and recent commits
- Clear documentation and SKILL.md content
- Open source with visible code
---
## Combining external skills with cc-arsenal
### Avoiding redundancy
Run `ls skills/` in this repo before installing an external equivalent. cc-arsenal already has 20+ skills (browser automation, Jira, docs, git, review, testing, and more) and a hardcoded list here would only go stale as skills are added.
### Complementary skills
Good candidates to install alongside cc-arsenal:
- Framework-specific skills (React, Next.js, Django, Rails patterns)
- Language-specific skills (Rust, Go, Python best practices)
- Design system skills (Tailwind, Material UI)
- Cloud provider skills (AWS, GCP, Azure)
- Database skills (PostgreSQL, MongoDB, Redis)
### Conflict resolution
If an installed skill overlaps with cc-arsenal:
1. Prefer cc-arsenal's built-in skill (better integration, maintained by the same team)
2. Remove the duplicate: `npx skills remove <name>`
3. If the third-party skill is superior, consider contributing improvements to cc-arsenal instead
---
## Managing updates and versions
### Regular maintenance
```bash
# Check for available updates
npx skills check
# Update all installed skills
npx skills update
# List current installations to audit
npx skills list
```
### Cleaning up unused skills
```bash
# Interactive removal (shows installed skills)
npx skills remove
# Remove a specific skill
npx skills remove old-skill
# Remove all skills from a specific agent
npx skills rm --skill '*' -a cursor
# Nuclear option: remove everything
npx skills remove --all
```
### Version pinning
The skills CLI does not support version pinning. Skills always install from the latest commit on the default branch. To pin a version:
1. Fork the skill repository
2. Install from the fork: `npx skills add your-fork/repo`
3. Control updates by merging upstream changes manually
---
## Publishing skills to skills.sh
To make skills discoverable on skills.sh:
1. **Host skills in a public GitHub repository** with `SKILL.md` files in a `skills/` directory
2. **Follow the Agent Skills format**: YAML frontmatter with `name` and `description` fields
3. **Skills appear on skills.sh** when users install them via `npx skills add`
4. **Install counts** are tracked automatically on the skills.sh leaderboard
The skills.sh directory indexes skills from Git repositories. There is no separate publishing step: any public repository with properly structured skills is installable.
```bash
# Verify your repo's skills are discoverable
npx skills add your-username/your-repo --list
```
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 472k | Updated | Claude CodeCodex | Unverified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |