scout
Skill11 starsChanged 22 days agoNo licenceView on GitHub
Study open-source repos to improve the current repo — scan them by specific questions, deep-dive the notable features, compare against the target repo and stop at a ranked plan for approval. Use when the user wants to learn from, benchmark against or borrow ideas from other projects. Not for onboarding into one unfamiliar repo (use codebase-onboarding) and not for implementing the result.
47 other projects use a version of this.
Adopted by
Most recently taken up by
- 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
- eggs-gd/career-spacetheir own version, first seen Nov 8, 2026
- dirien/yet-another-agent-harnesstheir own version, first seen Nov 8, 2026
- oscout/scouttheir own version, first seen Nov 4, 2026
Used with
Projects with it also use expand, blueprint and 8 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.
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
WordPressSkillblueprint
Use when the deliverable is WordPress Playground Blueprint JSON or a Blueprint bundle, including creating, editing, reviewing, validating schema keys, choosing steps/resources, and debugging Blueprint files. For only running or sharing a Playground environment, use wp-playground.
Also in 3 projects that use this
AWSSkillissue
Implement a GitHub issue end-to-end — branch, code, test, docs, and commit.
Also in 3 projects that use this
bradtraversySkillfeature
Manage current feature workflow - start, review, explain or complete
Also in 3 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
Other versions47 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 47
- 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★ 96same name
- vaayne/agent-kit★ 54same name
- anton-abyzov/vskill★ 47same name
- baekenough/oh-my-customcode★ 42same name
37 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.
In this repository39 other files it gives its agents.
- brainstormSkill
- cavemanSkill
- codebase-onboardingSkill
- codexSkill
- context-budgetSkill
- diagnosing-bugsSkill
- docs-driftSkill
- ecc-code-reviewSkill
- explainSkill
- frontend-design-barSkill
- grillingSkill
- hand-offSkill
- impeccableSkill
- interview-meSkill
- kyant-intentSkill
- kyant-kanbanSkill
- livestream-to-shortSkill
- log-wikiSkill
- marketingSkill
- megacaveSkill
- planningSkill
- ponytail-auditSkill
- ponytail-debtSkill
- ponytail-reviewSkill
- ponytailSkill
- prototypeSkill
- quality-gatesSkill
- remotion-best-practicesSkill
- reverse-engineer-anythingSkill
- reviewSkill
- run-agentsSkill
- scaffold-projectSkill
- security-reviewSkill
- skill-candidatesSkill
- tidy-gitSkill
- ultracaveSkill
- web-perfSkill
- write-internals-docSkill
- write-ruleSkill
The file
We split this skill into the rules it gives an agent
2 rules. 0 are common, 2 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 43 edited versions we read keep these.
2
Distinctive
This author's own choices. Worth a look.
0
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 measured: kept by at least 6 in 10 of the 43 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.
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.