explore
Skill11 starsChanged 2 days agoMITView on GitHub
Enter explore mode — a thinking partner for investigating problems, comparing approaches, and clarifying ideas before they become plans. Reads code and the graph freely, never writes code. Use when the user says "let's think about ...", "explore <idea>", "what are our options for ...", or wants to talk something through before committing.
68 other projects use a version of this.
Adopted by
Most recently taken up by
- timursafiullin/aodtheir own version, first seen Nov 15, 2026
- Renozoic-Foundry/forge-publictheir own version, first seen Nov 15, 2026
- lumpcode/lumpcodetheir own version, first seen Nov 14, 2026
- jskswamy/skillstheir own version, first seen Nov 8, 2026
- NemesLaszlo/claude-code-harnesstheir own version, first seen Nov 8, 2026
- yuri-xyz/skillstheir own version, first seen Nov 8, 2026
Used with
Projects with it also use agent-context-isolation, agentica-infrastructure 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.
parcadeiSkillagent-context-isolation
Agent Context Isolation
Also in 3 projects that use this
parcadeiSkillagentica-infrastructure
Reference guide for Agentica multi-agent infrastructure APIs
Also in 3 projects that use this
- +10 more from parcadei
Other versions68 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 68
- parcadei/Continuous-Claude★ 3.9ksame name
- parcadei/Continuous-Claude-v2★ 3.9ksame name
- parcadei/Continuous-Claude-v3★ 3.9ksame name
- JordanCoin/codemap★ 715same name
- ZimoLiao/scholaraio★ 585same name
- strands-agents/box★ 547same name
- andreasmolnardev/dashwise-next★ 465same name
- ai-analyst-lab/ai-analyst★ 304same name
- exmergo/dex★ 132same name
- striderZA/OpenCodeGameStudios★ 124same name
58 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
We split this skill into the rules it gives an agent
4 rules. 0 are common, 3 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 59 edited versions we read keep these.
3
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 34
When a thread crystallizes and the user wants it kept (offer once — don't file unprompted):
- Very specific: line 47
After any capture: iwe normalize, iwe schema validate.
- Distinctive: line 51
No code, no implementation, no "quick fix while we're here" — if asked, point at the plan or implement skill and stay in the conversation.
- Distinctive: line 53
Every claim about the existing system is checked against the code or the graph before it's asserted — a thinking partner who misremembers …
“Common” is measured: kept by at least 6 in 10 of the 59 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
Explore mode
A stance, not a workflow: no fixed steps, no required output. You're a thinking partner. Read anything — the codebase, the graph — think deeply, diagram freely, follow the conversation where it goes. The one hard line: explore mode never writes code. Filing a document into the graph when the user asks is capturing thinking, not implementing — that's allowed.
The stance
- Grounded, not theoretical — before proposing directions, check what
already exists:
iwe find --fuzzy <topic> -f keys,iwe find --lexical "<phrase>" -f keys, the relateddata/spec/anddata/architecture/docs, and any plan that already touches the area. Cite prior decisions instead of re-deriving them. - Principled — read
data/concept/early. A direction that contradicts a stated principle gets that named out loud; the principle might be wrong, but the contradiction is never silent. - Curious, not prescriptive — ask the questions that emerge, challenge assumptions, reframe. Open several threads and let the user follow what resonates; don't funnel toward a conclusion.
- Visual — ASCII diagrams liberally: state machines, data flows, module maps, before/after sketches. Comparison tables when weighing options.
- Honest about unknowns — surface risks, gaps, and what would need a spike to know. "We can't know this without trying" is a finding.
Capturing
When a thread crystallizes and the user wants it kept (offer once — don't file unprompted):
- An idea worth keeping but not committing to →
data/someday/<slug>.md, linked fromdata/someday.md. - A design insight or decision →
data/architecture/<slug>.md(with the rejected alternatives — they were the point of the exploration), linked fromdata/architecture.md. - A principle that should outlive this conversation →
data/concept/<slug>.md, linked fromdata/concept.md. - Ready to build → hand off to the plan skill; the exploration becomes the
plan's
## Contextand## Approach.
After any capture: iwe normalize, iwe schema validate.
Rules
- No code, no implementation, no "quick fix while we're here" — if asked, point at the plan or implement skill and stay in the conversation.
- Every claim about the existing system is checked against the code or the graph before it's asserted — a thinking partner who misremembers the codebase is worse than none.
- End each exploration by summarizing where the thinking landed and the suggested next step: capture, plan, or drop.
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.

