landscape-reconnaissance
Skill2 starsChanged 6 months agoApache-2.0View on GitHub
Broad, shallow exploration of candidate research fields. Understand what's out there before narrowing. Use when the user needs to discover which fields are available to them — especially in cold-start and warm-start scenarios.
In this repository32 other files it gives its agents.
- actor-profilingSkill
- and-or-decomposeSkill
- ask-constraintsSkill
- ask-decomposition-validationSkill
- ask-intentionalitySkill
- ask-obstacle-acceptanceSkill
- assess-obstacle-severitySkill
- broad-paper-searchSkill
- broad-web-searchSkill
- clarify-resourcesSkill
- cold-startSkill
- crystallize-north-starSkill
- deep-web-searchSkill
- direction-narrowingSkill
- explore-resumeSkill
- feasibility-checkSkill
- final-validationSkill
- formulate-top-goalSkill
- generate-candidate-fieldsSkill
- generate-research-briefSkill
- goal-decompositionSkill
- hot-startSkill
- identify-obstaclesSkill
- landscape-synthesisSkill
- north-star-crystallizationSkill
- north-star-synthesisSkill
- obstacle-analysisSkill
- present-and-askSkill
- present-candidatesSkill
- propose-mitigationsSkill
- validate-leavesSkill
- warm-startSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 21
If iteration is needed, expand breadth (more fields, more searches), never depth
≈ “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.
Files
Landscape Reconnaissance
Broad, shallow field exploration. Understand the landscape of possibilities before narrowing.
Available SOPs
| SOP | Purpose | Execution |
| generate-candidate-fields | Generate candidate fields from ActorProfile | subagent |
| broad-web-search | Scan web for each candidate field | import: web-search |
| landscape-synthesis | Synthesize search results into FieldPanorama | subagent |
| present-and-ask | Present panorama to user, get field selection | dialogue |
Methodology Guidance
- If iteration is needed, expand breadth (more fields, more searches), never depth
- Depth is direction-narrowing's job
- You decide when enough information exists to synthesize
Hard Constraints
broad-web-search: brave_web_search count=10 per call, at least 150 total results before synthesislandscape-synthesis: Don't only chase niche/novel combinations. Must also consider direct frontal competition in hot fields. The ambition to tackle hard problems head-on must be present.
Output (Tactic-Level Aggregation)
FieldPanorama[] + user's selected 1-2 fields of interest
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.