idea-scout
Skill6 starsChanged 8 months agoNo licenceView on GitHub
Deep, autonomous domain decomposition and landscape research for any idea or problem statement. Takes a raw idea (from one sentence to a paragraph) and runs a 6-phase research process: decomposes the idea into problem space, target users, domain, adjacent domains, and assumed solution direction; performs exhaustive parallel web research on current state of the art, key players, recent momentum, technical foundations, and user sentiment; synthesizes gaps, blind spots, friction points, challenges, and opportunities; maps 3-5 distinct solution directions with feasibility and differentiation analysis; runs contrarian and timing checks including cross-domain analogies; and scores all findings by confidence level with full source attribution. Outputs a structured research dossier to /docs/idea-scout/. Use this skill whenever the user has a raw idea they want explored before building, wants to understand a problem landscape, needs domain research, or wants to validate whether an idea is worth pursuing. Triggers on: 'scout this idea', 'research this idea', 'explore this concept', 'what's the landscape for', 'idea-scout', 'is this worth building', 'what exists for', 'explore the space of', 'I have an idea for', 'help me understand the landscape', 'what's out there for', 'domain research for', 'validate this idea'.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- ychampion/ystacktheir own version, first seen Nov 15, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- ychampion/ystack★ 4same name
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.
In this repository6 other files it gives its agents.
- api-database-scoutSkill
- design-scoutSkill
- investigateSkill
- prd-generatorSkill
- swarm-simulatorSkill
- ui-expertSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
13 rules. About 0 are common, 12 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈12
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
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.

