What it does
Search existing local, marketplace, GitHub, and web skill sources before creating a new skill
Skills ZICQ category:Agent Workflows skill-scout
Search existing local, marketplace, GitHub, and web skill sources before creating a new skill. Use when the user wants to create, build, fork, or find a skill for a workflow.
Official URL:skills.sh
Intro in this page language first. The official description stays in its original wording; we do not rewrite SKILL.md.
Search existing local, marketplace, GitHub, and web skill sources before creating a new skill
- The user says "create a skill", "build a skill", "make a skill", or "new
Per Agent Skills progressive disclosure: name and description load at startup (~100 tokens); the full SKILL.md body loads when the skill activates; scripts/, references/, and assets/ load only as needed. This file's sections: Skill Scout; When to Use; How It Works; Step 1 - Capture Intent; Step 2 - Search Local Sources; Step 3 - Search Remote Sources. It includes spec-recommended sections: step-by-step instructions, input/output examples.
File analysis: instruction-only skill (SKILL.md). The agent loads the full body when activated.
Skill ScoutWhen to UseHow It WorksStep 1 - Capture IntentStep 2 - Search Local SourcesStep 3 - Search Remote SourcesStep 4 - Vet External MatchesStep 5 - Rank ResultsStep 6 - Present Decision OptionsExamplesResult TableUser-Facing Summary
Source category:skills.sh agent-skill
nameskill-scoutdescriptionInvocation syntax and available tools depend on your Agent client. Client integration guide ↗
Choose the target agent and installation scope, keep referenced package files, then verify the skill appears in the client's catalog.
Copy these instructions to a compatible agent and confirm the target directory matches your client.
Install the agent skill "skill-scout" into my project. The full SKILL.md and official description are at https://zicq.com/en/skills/skl-d349ab97868beaa9-Skill-Scout.html Save it as .cursor/skills/skill-scout/SKILL.md or .claude/skills/skill-scout/SKILL.md and keep the frontmatter name and description exactly as-is.
Requires Node.js and npx. First inspect the repository's skill list to confirm the name.
npx skills add 'https://github.com/affaan-m/ecc' --list
npx skills add 'https://github.com/affaan-m/ecc' --skill 'skill-scout'
The CLI lets you choose the agent interactively. The default scope is the project; use -g for user scope. Confirm package availability with the discovery command, then use npx skills list to inspect installed skills.
Use this skill before creating a new skill. The goal is to avoid duplicating existing community or marketplace work, while still vetting anything external before adoption.
Source: salvaged from stale community PR #1232 by redminwang.
If the user explicitly says to skip search or create from scratch, acknowledge that and proceed with the requested creation workflow.
Extract:
Search installed and marketplace skill names first. Local sources are preferred because they are already part of the user's environment.
find ~/.claude/skills -maxdepth 2 -name SKILL.md 2>/dev/null | grep -iE "keyword|synonym"
find ~/.claude/plugins/marketplaces -path '*/skills/*/SKILL.md' 2>/dev/null | grep -iE "keyword|synonym"
Then search frontmatter descriptions:
grep -RilE "keyword|synonym" ~/.claude/skills ~/.claude/plugins/marketplaces 2>/dev/null
Use available GitHub and web search tools. Prefer concise queries:
gh search repos "claude code skill keyword" --limit 10 --sort stars
gh search code "name: keyword" --filename SKILL.md --limit 10
For web search, use at most three targeted queries such as:
"claude code skill" keyword
"SKILL.md" keyword
"everything-claude-code" keyword
Before recommending any external skill for adoption or forking:
SKILL.md frontmatter and instructions.Rank candidates by:
Cap the final list at 10 results.
Give the user a short table:
| Option | Meaning | | --- | --- | | Use existing | Invoke or install a matching skill as-is. | | Fork or extend | Copy the closest skill and modify it. | | Create fresh | Build a new skill after confirming no close match exists. |
Only create a new skill after the user chooses that path or after the search finds no close match.
| # | Skill | Source | Why it matches | Gap |
| --- | --- | --- | --- | --- |
| 1 | article-writing | Local ECC | Drafts articles and guides | Not focused on release notes |
| 2 | content-engine | Local ECC | Multi-format content workflow | Heavier than needed |
| 3 | blog-writer | GitHub | Blog writing skill with recent commits | Needs security review |
I found two close local matches and one external candidate. The closest fit is
`article-writing`; it covers drafting and revision, but it does not include the
release-note checklist you asked for. I can either use it as-is, fork it into a
release-note variant, or create a fresh skill.
search-first - General search-before-building workflow.skill-stocktake - Audit installed skills for health, duplicates, and gaps.agent-sort - Categorize and organize existing agents and skills.Agent Workflows
Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that exte…
Agent Workflows
Use the ClawdHub CLI to search, install, update, and publish agent skills from clawdhub.com. Use when you need to fetch new skills on the fl…
Agent Workflows
Orchestrate multi-agent teams with defined roles, task lifecycles, handoff protocols, and review workflows. Use when: (1) Setting up a team …
Agent Workflows
Spec-first, TDD, subagent-driven software development workflow. Use when: (1) building any new feature or app — triggers brainstorm → plan →…