explore-unknowns
Skill112 starsChanged 3 days agoNo licenceView on GitHub
Guide the user through a quadrant walk that maps the unknowns of a task — open by listing the known knowns, then work through known unknowns, unknown knowns, and unknown unknowns one stage at a time, ending with a complete four-quadrant map in the user's hands. Use when a request is ambiguous or underspecified, the codebase or domain is unfamiliar, the user will "know it when they see it", a reference implementation must be understood before porting, mid-build deviations from the plan need capturing, or a finished change needs buy-in or verified understanding before merge. Pairs with [write-spec](../write-spec/SKILL.md) — walk the quadrants to burn off fog before slicing, and feed the finished map into the spec.
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 5 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈5
Distinctive · estimate
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 an estimate: at least 1 in 5 of the 308,232 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.
Other versions5 projects use a version of this.
Word for word · 3
- dzhng/jevgrep★ 3.1k100% same
- dzhng/skills★ 1.4k100% same
- dzhng/duet-agent★ 55100% same
Edited · 2
- Buddhilive/buddhi-cli★ 1100% same
- rhnfzl/explore-unknowns★ 011% same
Wrote their own version · 0
None found.
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 repository33 other files it gives its agents.
- AGENTS.mdAGENTS.md
- audit-agentsSkill
- audit-decisionsSkill
- audit-performanceSkill
- audit-testsSkill
- auto-researchSkill
- claudeSkill
- close-specSkill
- code-reviewSkill
- codexSkill
- compare-screenshotsSkill
- design-with-imagesSkill
- eli5Skill
- eval-skillsSkill
- handoff-specSkill
- implement-specSkill
- implement-spec-with-codexSkill
- implement-spec-with-goalSkill
- launch-videoSkill
- marketing-pagesSkill
- preview-shotsSkill
- ratchet-filesSkill
- refactor-cleanSkill
- releaseSkill
- rendererSkill
- retroSkill
- reviewSkill
- screenshot-critiqueSkill
- write-docsSkill
- write-skillsSkill
- write-specSkill
- write-testsSkill
- yapSkill
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.