Marketing Foundation
Clarify positioning, then turn it into a lead-generation asset.
The tunnel uses the same cards as the catalogue. Browse only as deep as needed — or load a broad bundle immediately.
SEO, Sales, Agents or another broad area → one bundle call → work.
Read-only access to published skills. Default 8, maximum 10 skills / 120,000 characters.
Clarify positioning, then turn it into a lead-generation asset.
Build an evidence-led marketing plan from ICP and competition through positioning, campaigns, growth and measurement.
Diagnose architecture and context, then plan agent-team responsibilities. Memory and cost-runtime reviews are outside this pack.
Review the journey from landing page and lead capture through registration, first value and transparent upgrades.
Plan a campaign, draft its channel content and review the work against actual brand guidance.
Searches local and external skill sources for existing matches before a new skill is created.
--- name: skill-scout description: 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. metadata: origin: community --- # Skill Scout 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`. ## When to Use - The user says "create a skill", "build a skill", "make a skill", or "new skill". - The user asks "is there a skill for X?" or "does a skill exist that does Y?" - The user describes a workflow and you are about to suggest creating a new skill. - The user wants to fork or extend an existing skill. If the user explicitly says to skip search or create from scratch, acknowledge that and proceed with the requested creation workflow. ## How It Works ### Step 1 - Capture Intent Extract: - The task the skill should perform. - The trigger conditions for using it. - The domain, tools, frameworks, or data sources involved. - Three to five search keywords plus useful synonyms. ### Step 2 - Search Local Sources Search installed and marketplace skill names first. Local sources are preferred because they are already part of the user's environment. ```bash 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: ```bash grep -RilE "keyword|synonym" ~/.claude/skills ~/.claude/plugins/marketplaces 2>/dev/null ``` ### Step 3 - Search Remote Sources Use available GitHub and web search tools. Prefer concise queries: ```bash 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: ```text "claude code skill" keyword "SKILL.md" keyword "everything-claude-code" keyword ``` ### Step 4 - Vet External Matches Before recommending any external skill for adoption or forking: - Read the `SKILL.md` frontmatter and instructions. - Look for unexpected shell commands, file writes, network calls, credential handling, or package installs. - Check whether the repository appears maintained. - Prefer copying into a fresh local branch and reviewing the diff over editing marketplace originals. ### Step 5 - Rank Results Rank candidates by: 1. Exact keyword match in the skill name. 2. Keyword or synonym match in description. 3. Local installed or marketplace source. 4. Maintained GitHub source with recent activity. 5. Web-only mention. Cap the final list at 10 results. ### Step 6 - Present Decision Options 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. ## Examples ### Result Table ```markdown | # | 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 | ``` ### User-Facing Summary ```markdown 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. ``` ## Anti-Patterns - Do not jump directly to new skill creation when a search is reasonable. - Do not install external skills without reading them first. - Do not present a long unranked list of weak matches. - Do not treat web-only mentions as trusted sources. - Do not edit installed marketplace originals in place. ## Related - `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.
Use when someone wants to find, create, fork, or extend a skill for a workflow. If they explicitly request skipping the search, proceed according to that request.
• Ranked skill matches
• Match and gap summary
• Use, fork, or create options
1. Define the workflow and search terms.
2. Search local sources, then available external sources.
3. Review and rank matches and explain gaps.
Local discovery requires access to relevant skill directories; external discovery depends on available GitHub and web search tools. No specific runtime or mandatory reference files are specified.
Use the skill below to find an existing skill for [TASK]. Search only sources you can access, compare the actual instructions and explain the gaps. Do not install or adopt a candidate automatically.
Automatically installing or approving discovered third-party skills.
M11 added capability-gap routing, explicit no-auto-install boundaries, stable discovery metadata and source integrity around the unchanged scout skill.
MIT License Copyright (c) 2026 Affaan Mustafa Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
Copy the text below, then paste it into your chat.