scout
Skill25 starsChanged 8 months agoMITView on GitHub
Research a domain before building products. Tests Claude's baseline knowledge, identifies gaps, scans the marketplace, runs deep research, and recommends the optimal product setup. Use when: 'scout', 'research domain', 'what should I build for', 'analyze domain', or before /create for any non-trivial product.
48 other projects use a version of this.
Adopted by
Most recently taken up by
- david33137/claude-skillstheir own version, first seen Nov 16, 2026
- baekenough/oh-my-customcodetheir own version, first seen Nov 14, 2026
- oscout/scouttheir own version, first seen Nov 10, 2026
- venhdev/skillstheir own version, first seen Nov 8, 2026
- dfirmin/compasstheir own version, first seen Nov 8, 2026
- apattichis/agentic-research-toolkittheir own version, first seen Nov 8, 2026
Used with
Projects with it also use markdown-novel-viewer, expand and 10 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.
OpenAnalystIncSkillmarkdown-novel-viewer
Also in 3 projects that use this
andrewclark88Skillexpand
Expand a project's scope by updating its foundation documents. Reads existing north-star.md (or north-star-<project>.md), architecture.md, and roadmap.md, understands the codebase state, then interviews the user about the expansion. Updates foundation docs and roadmap so design can consume them in the next phase. Use when adding a major capability, new subsystem, or architectural shift — not for small one-offs (use feature for those).
Also in 3 projects that use this
mrgoonieSkillweb-testing
Web testing with Playwright, Vitest, k6. E2E/unit/integration/load/security/visual/a11y testing. Use for test automation, flakiness, Core Web Vitals, mobile gestures, cross-browser.
Also in 3 projects that use this
mrgoonieSkillweb-frameworks
Build modern full-stack web applications with Next.js (App Router, Server Components, RSC, PPR, SSR, SSG, ISR), Turborepo (monorepo management, task pipelines, remote caching, parallel execution), and RemixIcon (3100+ SVG icons in outlined/filled styles). Use when creating React applications, implementing server-side rendering, setting up monorepos with multiple packages, optimizing build performance and caching strategies, adding icon libraries, managing shared dependencies, or working with TypeScript full-stack projects.
Also in 3 projects that use this
PJuniszewskiSkillcook
Feature development with guardrails. Plan → Review → Code → Ship.
Also in 3 projects that use this
sunnyclinches44Skillexplain
Explains code using real-world analogies and ASCII diagrams
Also in 5 projects that use this
- +5 more from mrgoonie
Other versions48 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 48
- huytieu/COG-second-brain★ 1.3ksame name
- HazAT/pi-config★ 451same name
- OneWave-AI/claude-skills★ 378same name
- typv/nest-turbo-starter★ 224same name
- QinghongLin/data2story-skill★ 155same name
- andrew-yangy/gru-ai★ 153same name
- simota/agent-skills★ 99same name
- vaayne/agent-kit★ 54same name
- anton-abyzov/vskill★ 47same name
- baekenough/oh-my-customcode★ 42same name
38 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.
The file
Show its rules and text
We split this skill into the rules it gives an agent
25 rules. 0 are common, 12 are distinctive, and 13 are very specific to this project.
0
Common
Most of the 44 edited versions we read keep these.
12
Distinctive
This author's own choices. Worth a look.
13
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 25
When to use: Before /create for any serious product.
- Very specific: line 38
Creator profile guard: Read creator.yaml from project root.
- Very specific: line 48
Parse arguments: Read $ARGUMENTS for domain query.
- Distinctive: line 49
If no arguments → ask via AskUserQuestion: "What domain do you want me to research?"
- Distinctive: line 50
Intent check: Ask via AskUserQuestion (single select): "What's your goal for this domain?"
- Very specific: line 60
Use §INTELLIGENCE_GRADIENT to explain WHY a type is recommended: "This domain needs judgment in routing, so squad is better than workflow."
- Distinctive: line 61
Use §COMPOSITION to suggest how recommended products compose: "The skill handles execution while the mind advises."
- Distinctive: line 62
Use §HEURISTICS to guard against over-recommendation: if a single skill suffices, don't recommend a squad
- Distinctive: line 63
Use §ISOMORPHIC for creator-friendly explanations: "You need an advisor (minds) for thinking and a skill for doing."
- Very specific: line 64
Use §COMPOSITION_PRINCIPLES to suggest how recommended products compose: convergence-by-independence for squads, symbiosis for mind+skill …
- Very specific: line 65
Use §TRANSVERSAL_AXES to calibrate Nature and Depth per recommended product
- Very specific: line 67
Gate check: Read config.yaml → gates.confirm_create (default: true).
- Distinctive: line 68
If true → "I'll research '{domain}'.
- Distinctive: line 83
After gap analysis completes, PAUSE and show the creator:
- Distinctive: line 97
Only proceed to Steps 3-6 after creator confirms.
- Distinctive: line 103
After the protocol completes:
- Very specific: line 104
Verify workspace/scout-{slug}.md was written (Glob check)
- Distinctive: line 110
market: Use Section 3 market position (blue_ocean → 2, moderate → 1, saturated → 0)
- Very specific: line 122
Read STATE.yaml → workspace.products[] AND STATE.yaml → mcs_results.
- Distinctive: line 123
Check if any existing product is in the same domain or has overlapping capability.
- Very specific: line 124
If existing product has mcs_results with overall_score: "Your {slug} covers {domain} at {score}%.
- Very specific: line 125
If existing product has baseline_delta: "Your {slug} addressed {delta}% of known gaps.
- Very specific: line 126
If found: "This connects to your existing {existing_slug} ({existing_type}).
- Very specific: line 127
If the recommended products would bring the domain product count to >= bundle_suggestion_threshold (from config.yaml → …
- Very specific: line 143
Update STATE.yaml last_scout field (not current_task — scout reports are not products)
“Common” is measured: kept by at least 6 in 10 of the 44 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 — Domain Intelligence & Setup Recommendation
Before you build, understand the territory. This skill researches what Claude already knows, what's missing, what exists in the marketplace, and recommends exactly what to build.
When to use: Before /create for any serious product. When exploring a new domain. When the creator says "what should I build for X?" or "scout X".
When NOT to use: For marketplace browsing without building intent (use /explore). For building products (use /create→/fill). For mapping YOUR expertise (use /map).
CLI contract: This skill declares Bash(myclaude *) permission but delegates all marketplace queries to /explore. No direct CLI invocations here. See references/cli-contract.md for unified error handling when /explore is invoked as a sub-step.
Activation Protocol
- Shared preamble: Load
references/quality/activation-preamble.md— context assembly, persona adaptation, deterministic routing rules. - Creator profile guard: Read
creator.yamlfrom project root. If missing → respond: "Profile not found. Run/onboardfirst (~3 min)." and stop. 1b. Load UX vocabulary: Loadreferences/ux-vocabulary.md— translate all internal terms (MCS, DNA, scaffold, forge) before any creator-facing output. Vocabulary guard applies to all output in this skill. 1c. Load proactives: Loadreferences/engine-proactive.md— wire #1 (pipeline guidance: after scout, suggest /create), #15 (research injection triggers), #16 (scout intelligence reuse). - Maintain creator persona: Adapt language, depth, and examples to
profile.typeandtechnical_levelthroughout. Loadreferences/quality/engine-voice-core.mdat the start of every /scout invocation — every user-facing line honors the ✦ signature, three tones, and six anti-patterns. Load the fullreferences/quality/engine-voice.mdonly when rendering the final report delivery (a peak moment — the Creator just watched 2-5 minutes of research consolidate into a concrete recommendation). - Parse arguments: Read
$ARGUMENTSfor domain query. If no arguments → ask via AskUserQuestion: "What domain do you want me to research?" - Intent check: Ask via AskUserQuestion (single select):
"What's your goal for this domain?"
- "Build products for myself" → personal setup, skip pricing
- "Build products for the marketplace" → include pricing + market scan emphasis
- "Just explore — not sure yet" → lighter report, skip recommendation details
- Sanitize slug: lowercase, alphanumeric + hyphens, 3-40 chars.
- Brownfield check: Glob
workspace/scout-{slug}.md. If exists → ask: "A scout report for '{domain}' already exists ({date}). Refresh it or reuse?" 7b. Load entity ontology for type recommendation: Readreferences/entity-ontology.md§SCOUT_INTELLIGENCE, §INTELLIGENCE_GRADIENT, §COMPOSITION, §HEURISTICS, §ISOMORPHIC. Use these to inform the setup recommendation:- Map domain signals to recommended product types per §SCOUT_INTELLIGENCE (single task→skill, advisory→minds, distinct specialties→squad, etc.)
- Use §INTELLIGENCE_GRADIENT to explain WHY a type is recommended: "This domain needs judgment in routing, so squad is better than workflow."
- Use §COMPOSITION to suggest how recommended products compose: "The skill handles execution while the mind advises."
- Use §HEURISTICS to guard against over-recommendation: if a single skill suffices, don't recommend a squad
- Use §ISOMORPHIC for creator-friendly explanations: "You need an advisor (minds) for thinking and a skill for doing."
- Use §COMPOSITION_PRINCIPLES to suggest how recommended products compose: convergence-by-independence for squads, symbiosis for mind+skill pairs
- Use §TRANSVERSAL_AXES to calibrate Nature and Depth per recommended product
- For MCS-3 targets, consider §INTELLIGENCE_PIPELINE hermeneutic spiral as pre-forge method
- Gate check: Read
config.yaml→gates.confirm_create(default: true). If true → "I'll research '{domain}'. This involves generating a baseline, analyzing gaps, searching the marketplace, and running web research. Takes 2-5 minutes. Continue?"
Execution — 6-Step Intelligence Protocol
Load and execute the full protocol from .claude/agents/scout-agent.md with:
domain: the parsed domain queryslug: the sanitized slugcreator: the loaded creator.yaml profilelanguage: creator's language (from creator.yaml or detected from input)intent: personal / marketplace / explore (from step 4)
Critical gate between Steps 2→3: After gap analysis completes, PAUSE and show the creator:
Gap Analysis Complete — {domain}
{critical_count} critical gaps | {significant_count} significant | {minor_count} minor
Top gaps:
1. {gap_1_summary} (critical)
2. {gap_2_summary} (significant)
3. {gap_3_summary} (significant)
Next: marketplace scan + web research on these gaps (~{N} searches).
Continue, adjust focus, or stop here?Only proceed to Steps 3-6 after creator confirms.
Post-Execution
After the protocol completes:
- Verify
workspace/scout-{slug}.mdwas written (Glob check) Compute value estimates for each recommended product: For each product in the setup recommendation (Section 5), estimate a preliminary value score using the Intelligence Layer formula (
config.yaml → intelligence.pricing):- depth: Infer from MCS target in the recommendation (MCS-2 → 2, MCS-3 → 3, cognitive mind → +1)
- uniqueness: Estimate from gap severity coverage (all critical gaps → 3, mixed → 2, minor only → 1)
- coverage: Count gaps the product addresses from Section 2
- market: Use Section 3 market position (blue_ocean → 2, moderate → 1, saturated → 0)
Map the estimated
VALUE_SCOREto a price range usingconfig.yaml → intelligence.pricing.price_map.Append to each recommended product in the report output:
Value estimate: {value_score}/12 → ${range[0]}-${range[1]} ({strategy})Epistemic caveat (always shown): "Value estimates are preliminary — based on gap coverage and market position. Actual value_score is computed by /validate Stage 8 after content is filled."
- Portfolio connection check (back-reference from /validate):
Read
STATE.yaml → workspace.products[]ANDSTATE.yaml → mcs_results. For each recommended product:- Check if any existing product is in the same domain or has overlapping capability.
- If existing product has
mcs_resultswithoverall_score: "Your {slug} covers {domain} at {score}%. New product should focus on gaps {slug} doesn't cover — zero overlap = maximum delta." - If existing product has
baseline_delta: "Your {slug} addressed {delta}% of known gaps. Scout for complementary coverage." If found: "This connects to your existing {existing_slug} ({existing_type}). Building here extends your {domain} coverage." If the recommended products would bring the domain product count to>= bundle_suggestion_threshold(fromconfig.yaml → intelligence.portfolio): "With these additions, you'd have {N} products in {domain} — consider bundling them for complete coverage."
- Vocabulary guard (mandatory before rendering): Before emitting any creator-facing text in step 4, translate internal terms per ux-vocabulary.md. Specifically: "gap severity" → "how much is missing", "baseline delta" → "what Claude already knows vs. what's needed", "market saturation" → "how crowded this space is", "blue_ocean" → "wide-open opportunity". For non-developer creators (profile.type != "developer" and != "hybrid"), these plain-language substitutions are required. For developer/hybrid creators, technical terms may appear but must include a brief inline gloss on first use.
- Show the setup recommendation summary using engine voice:
Scout complete. {N} gaps found, {M} researched, {P} products recommended. Recommended setup: {product_list_with_types_and_value_estimates} {portfolio_connection_note if applicable} Your expertise goes in next — accept this setup? /create {first_type} to start building. - Update STATE.yaml
last_scoutfield (not current_task — scout reports are not products)
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.

