scout
Skill48 starsChanged 6 months agoMITView on GitHub
START HERE — Skill discovery and installation assistant. The recommended first skill when you don't know which skills you need. Searches verified-skill.com, recommends plugin bundles, and installs skills. Triggers on: find skill, search skills, what skills available, discover, install a skill, recommend skills, browse registry, explore skills, which skill should I use, help me find.
- Installs packages
We split this skill into the rules it gives an agent
25 rules. 0 are common, 14 are distinctive, and 11 are very specific to this project.
0
Common
Most of the 40 edited versions we read keep these.
14
Distinctive
This author's own choices. Worth a look.
11
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 40
Before recommending new skills, check what the user already has:
- Distinctive: line 59
When the user says "I don't know" or "what should I install?", analyze their project:
- Distinctive: line 61
Check for tech stack indicators:
- Distinctive: line 77
Run the search command using the terminal:
- Distinctive: line 91
If the search returns no results, try:
- Distinctive: line 110
Note tier differences: if results span multiple tiers (CERTIFIED > VERIFIED)
- Distinctive: line 114
When the query matches a known plugin category, suggest the full plugin bundle instead of individual skills.
- Distinctive: line 131
After the user selects what to install, execute the appropriate command:
- Very specific: line 183
Only recommend --force for the official anton-abyzov/vskill plugins.
- Distinctive: line 187
After running the install command:
- Very specific: line 237
Check the project's tech stack (package.json, go.mod, etc.)
- Distinctive: line 248
Ask if they want individual skills or a full bundle
- Very specific: line 254
Run npx vskill find "nextjs" --json to confirm availability
- Very specific: line 256
Run npx vskill install <owner>/<repo> --skill <skill-name> using the actual result from the search
- Distinctive: line 263
Ask which domain interests them
- Distinctive: line 264
Search that domain and present specific skills
- Very specific: line 270
Run npx vskill list to check what's already installed
- Very specific: line 271
Look at the project's tech stack (package.json, Cargo.toml, go.mod, etc.)
- Distinctive: line 273
Search for skills matching each domain
- Very specific: line 287
Run npx vskill info <owner>/<repo>/<skill-name> to check tier and score
- Very specific: line 290
If VERIFIED or CERTIFIED, confirm it's safe.
- Distinctive: line 294
When presenting results, explain trust tiers to help users make informed decisions:
- Very specific: line 303
Always use --json flag when searching programmatically to get structured output
- Very specific: line 309
Use --all with --repo to install all 5 plugin bundles in one command
- Very specific: line 310
Run npx vskill list before recommending to avoid suggesting already-installed skills
“Common” is measured: kept by at least 6 in 10 of the 40 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Scout — Skill Discovery & Installation
You are the go-to skill for helping users discover, evaluate, and install AI skills from the verified-skill.com registry. You are the recommended starting point when users don't know which skill they need — guide them to the right tools.
When to Activate
Activate this skill when the user:
- Doesn't know which skill they need ("what should I install?", "help me get started")
- Asks to find, search, or discover skills ("find me a skill for Kubernetes")
- Wants to know what skills are available for a technology or domain
- Asks to install a skill by name or topic
- Wants recommendations for skills relevant to their project
- Mentions "skill registry", "verified-skill.com", or "vskill"
- Asks "what skills can help me with X?"
- Just installed vskill and wants to explore what's available
- Wants to check, list, update, or remove installed skills
- Asks for detailed info about a specific skill before installing
Quick Start
For new users or "what's available?" queries, start with this overview:
5 plugin bundles are available from the official vskill collection, covering mobile, marketing, google-workspace, productivity, and discovery (scout).
Each bundle contains focused, high-value skills. For example, the
mobilebundle includes the app store automation skill.Install a bundle:
npx vskill install --repo anton-abyzov/vskill --plugin <name> --forceInstall everything:npx vskill install --repo anton-abyzov/vskill --all --forceSearch the registry:npx vskill find "<query>"
Workflow
Step 0: Check What's Already Installed
Before recommending new skills, check what the user already has:
npx vskill listThis shows all installed skills with their versions and sources. Use npx vskill list --agents to see which AI agents are detected on the system. Avoid recommending skills that are already installed.
Step 1: Parse the User's Intent
Determine what the user is looking for:
- New user / don't know: Analyze their project and recommend bundles (see Step 1b)
- Technology/domain: e.g., "React", "Kubernetes", "payments", "testing"
- Specific skill: e.g., "nextjs", "stripe-integration", "helm-charts"
- Broad exploration: e.g., "what's available?", "show me everything"
- Manage installed skills: list, update, remove, or inspect existing skills
Step 1b: Project-Aware Recommendations (when user doesn't know)
When the user says "I don't know" or "what should I install?", analyze their project:
- Check for tech stack indicators:
package.jsonwith React Native/Expo → mobile bundleios/orandroid/directories → mobile bundle- Social media or marketing context → marketing bundle
- Google Workspace integrations → google-workspace bundle
- General skill discovery → skills bundle (this skill)
- Based on findings, recommend specific bundles with reasoning:
"Based on your project, I recommend these bundles:
- mobile — you have React Native and Expo in package.json
- marketing — you mentioned social media posting needs"
- Offer to install all recommended bundles at once.
Step 2: Search the Registry
Run the search command using the terminal:
npx vskill find "<query>" --jsonThe --json flag returns structured results. Each result contains:
name— skill identifier (e.g., "mobile:appstore")author— skill authortier— certification tier: CERTIFIED or VERIFIEDscore— trust score (0-100)installs— number of installationsdescription— what the skill does
If the search returns no results, try:
- Broader terms (e.g., "react" instead of "react server components")
- Related terms (e.g., "frontend" instead of "nextjs")
- Suggest the user visit https://verified-skill.com directly
Step 3: Present Results
Format search results as a clear table:
| Name | Author | Tier | Score | Installs | Description |
|-------------------|---------------|-----------|-------|----------|--------------------------------|
| mobile:appstore | Anton Abyzov | CERTIFIED | 95 | 340 | App Store Connect automation |
| marketing:social | Anton Abyzov | VERIFIED | 88 | 280 | Social media posting |After the table:
- Highlight the best match based on the user's query context
- Explain why it's relevant (mention specific capabilities)
- Note tier differences if results span multiple tiers (CERTIFIED > VERIFIED)
Step 4: Recommend Plugin Bundles
When the query matches a known plugin category, suggest the full plugin bundle instead of individual skills. Plugin bundles install multiple related skills at once.
Available plugin bundles (from anton-abyzov/vskill):
| Plugin | Domain | Skills Included |
mobile | Mobile development | App Store Connect automation (appstore) |
marketing | Marketing & comms | Social media posting, Slack messaging |
google-workspace | Google Workspace | Google Workspace CLI (gws) |
productivity | Personal productivity | Expert network survey completion |
skills | Discovery | This skill — search verified-skill.com and install skills |
Example recommendation:
"Your query matches the mobile plugin bundle, which includes the App Store Connect automation skill. Instead of installing individual skills, you can install the entire bundle."
Step 5: Install
After the user selects what to install, execute the appropriate command:
Install a single skill by name (from registry):
npx vskill install <skill-name>Install a plugin bundle (all skills in a domain):
npx vskill install --repo anton-abyzov/vskill --plugin <plugin-name> --forceInstall ALL plugin bundles at once:
npx vskill install --repo anton-abyzov/vskill --all --forceThe --force flag bypasses the interactive security scan prompt (the scan still runs, but auto-accepts PASS/CONCERNS verdicts). This is appropriate for the official vskill plugins which are pre-verified.
Install from a third-party GitHub repo:
npx vskill install <owner>/<repo>Install a specific skill from a repo:
npx vskill install <owner>/<repo> --skill <skill-name>Advanced install flags (use when needed):
| Flag | Purpose |
--global | Install to global agent directories (available across all projects) |
--select | Interactive picker to choose specific skills and agents |
--only-skills <names> | Cherry-pick specific skills from a plugin (comma-separated) |
--agent <id> | Target a specific AI agent (e.g., claude-code, cursor) |
--copy | Force file copy instead of symlink (useful in CI/containers) |
--yes / -y | Skip confirmation prompts |
Step 5b: Inspect Before Installing (Third-Party Skills)
For skills NOT from the official anton-abyzov/vskill collection, always inspect before installing:
# Get detailed info (trust tier, score, provenance, installs)
npx vskill info <owner>/<repo>/<skill-name>
# Run a local security scan on a skill file
npx vskill scan <path-to-SKILL.md>Only recommend --force for the official anton-abyzov/vskill plugins. For third-party skills, let the user review the scan results and decide.
Step 6: Confirm Installation
After running the install command:
- Report the installation result (success/failure)
- List which agents received the skill (Claude Code, Cursor, etc.)
- Mention the skill's namespace for invocation (e.g.,
mobile:appstore) - Suggest restarting the AI agent if needed to pick up new skills
Step 7: Manage Installed Skills
Help users manage their installed skills when asked:
Update skills (checks for newer versions with diff scanning):
npx vskill update <skill-name> # Update a specific skill
npx vskill update --all # Update all installed skillsRemove skills:
npx vskill remove <skill-name> # Remove from current project
npx vskill remove <skill-name> --global # Remove from global installAudit a project for security issues:
npx vskill audit # Full project audit
npx vskill audit --ci # CI-friendly output (exits non-zero on issues)Error Handling
| Scenario | Action |
npx vskill not found | Tell user to install: npm install -g vskill or use npx |
npm error code E401 with npx | A project .npmrc with a private registry is interfering. Use: npx --registry https://registry.npmjs.org vskill <command> or install globally: npm i -g vskill --registry https://registry.npmjs.org |
| Network error on search | Suggest checking internet connection; offer to try again |
| No results found | Try broader search terms; suggest visiting verified-skill.com |
| Scan FAIL on install | Explain the security concern; recommend npx vskill scan first to review details; suggest --force only if user understands the risk |
| Scan CONCERNS on install | Explain findings; --force is safer here than with FAIL |
| Blocked skill (blocklist) | Warn user strongly; this skill has known security issues |
| No agents detected | User needs to install Claude Code, Cursor, or another supported agent first |
| Rate limit (HTTP 429 or GitHub 403) | Wait a minute and retry; suggest using --json to reduce API calls |
| Partial install failure | Some skills in a bundle may fail (permissions, symlinks). Check npx vskill list to see what succeeded; retry individual failures |
| Lockfile out of sync | Run npx vskill init to resync the lockfile with actual installed skills |
| Already installed (version conflict) | Run npx vskill update <skill> to update, or npx vskill remove then reinstall |
Examples
Example 1: New User Onboarding
User: "I just installed vskill. What should I install?" Action:
- Check the project's tech stack (package.json, go.mod, etc.)
- Present project-aware bundle recommendations
- Offer
--allto install everything, or let them pick specific bundles - Install their choices
Example 2: Technology Search
User: "I need help with Kubernetes deployments" Action:
- Run
npx vskill find "kubernetes" --json - Present results table
- Recommend relevant skills from the registry
- Ask if they want individual skills or a full bundle
- Install their choice
Example 3: Specific Skill Install
User: "Install the Next.js skill" Action:
- Run
npx vskill find "nextjs" --jsonto confirm availability - Show the result with tier and score
- Run
npx vskill install <owner>/<repo> --skill <skill-name>using the actual result from the search - Confirm which agents received the skill
Example 4: Broad Exploration
User: "What skills are available?" Action:
- List the 5 available plugin bundles with descriptions
- Ask which domain interests them
- Search that domain and present specific skills
- Install based on selection
Example 5: Project-Aware Recommendation
User: "What skills would help with my project?" Action:
- Run
npx vskill listto check what's already installed - Look at the project's tech stack (package.json, Cargo.toml, go.mod, etc.)
- Identify relevant domains (mobile, marketing, google-workspace, productivity)
- Search for skills matching each domain
- Present a curated recommendation list (excluding already-installed skills)
- Offer to install matching bundles
Example 6: Manage Installed Skills
User: "Update all my skills" / "Remove the appstore skill" Action:
- For updates: run
npx vskill update --alland report what changed - For removal: run
npx vskill remove <skill-name>and confirm - For inspection: run
npx vskill info <skill-name>to show details
Example 7: Inspect Before Installing
User: "Is this kubernetes skill safe to install?" Action:
- Run
npx vskill info <owner>/<repo>/<skill-name>to check tier and score - Present the trust tier, security score, provenance, and install count
- Explain what the tier means (see Trust Tiers section)
- If VERIFIED or CERTIFIED, confirm it's safe; if UNSCANNED, suggest running
npx vskill scanfirst
Trust Tiers
When presenting results, explain trust tiers to help users make informed decisions:
- CERTIFIED — Highest trust. Manually reviewed and certified by the platform team. Safe to install.
- VERIFIED — Basic trust and above. Automated scans passed, author identity verified. Safe to install.
- UNSCANNED — No scan data. Use
--forceto install, but review the skill content first. - BLOCKED — Known malicious. Do NOT install unless you have a very specific reason and understand the risks.
Important Notes
- Always use
--jsonflag when searching programmatically to get structured output - The
--forceflag on install bypasses scan prompts but does NOT skip the scan itself - Only use
--forcefor officialanton-abyzov/vskillplugins — for third-party skills, runnpx vskill infoand review the scan results first - Plugin bundles from
anton-abyzov/vskillare the official curated collection - Third-party skills should be evaluated based on their trust tier and score — use
npx vskill info <skill>to check - Skills are installed per-agent (Claude Code, Cursor, etc.) — the CLI handles multi-agent installs
- Use
--allwith--repoto install all 5 plugin bundles in one command - Run
npx vskill listbefore recommending to avoid suggesting already-installed skills vskill searchis an alias forvskill find— both work identically
Other versions44 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 44
- huytieu/COG-second-brain★ 1.3ksame name
- HazAT/pi-config★ 451same name
- OneWave-AI/claude-skills★ 378same name
- typv/nest-turbo-starter★ 224same name
- 3x-haust/oh-my-design★ 203same name
- QinghongLin/data2story-skill★ 155same name
- andrew-yangy/gru-ai★ 153same name
- simota/agent-skills★ 96same name
- vaayne/agent-kit★ 53same name
- baekenough/oh-my-customcode★ 42same name
34 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
Used alongsideProjects with it also use feature, explain and 9 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
EffortlessMetricsSkillfeature
Also in 3 projects that use this
sunnyclinches44Skillexplain
Explains code using real-world analogies and ASCII diagrams
Also in 4 projects that use this
HK-hubSkilldistill
Strip designs to their essence by removing unnecessary complexity. Great design is simple, powerful, and clean. Use when the user asks to simplify, declutter, reduce noise, remove elements, or make a UI cleaner and more focused.
Also in 3 projects that use this
Microsoft AzureSkilltest
Also in 4 projects that use this
Microsoft AzureSkilldesign
Design rules and conventions for the API Center Portal. Use when editing detail pages, card components, badges, layout, navigation, sidebars, or headers. Covers badge styling, metadata placement, page navigation patterns, and layout alignment.
Also in 4 projects that use this
NVIDIASkillresearch
Before designing a feature, research how comparable libraries solve the problem, check best practices, known pitfalls, and upstream changes. Use when starting a new feature, investigating an unfamiliar area, or the user asks to research something.
Also in 6 projects that use this
In this repository30 other files it gives its agents.
- obsidian-brainSkill
- animejsSkill
- css-animationsSkill
- greet-anton-abyzovSkill
- gsapSkill
- higgsfield-seedanceSkill
- hyperframes-cliSkill
- hyperframes-mediaSkill
- hyperframes-registrySkill
- hyperframesSkill
- lottieSkill
- obsidian-brainSkill
- private-skillSkill
- remotion-to-hyperframesSkill
- slack-messagingSkill
- stub-skill-76f6713eSkill
- tailwindSkill
- threeSkill
- waapiSkill
- website-to-hyperframesSkill
- excalidraw-mcpSkill
- greet-anton-abyzovSkill
- greet-elenaSkill
- handoffSkill
- hi-atlantisSkill
- html-reportSkill
- hyperframes-best-practicesSkill
- motion-graphics-promoSkill
- reaSkill
- remotion-best-practicesSkill
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

