internal/embed/claude/skills/explore/SKILL.md
Use when user wants to explore a topic, find papers, map a field, or understand the research landscape. Not for explaining concepts — use learn for that.
npx skillsauth add moralespanitz/research-loop exploreInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Before anything else, create the session directory and open the lab notebook:
mkdir -p .research-loop/sessions/<slug>/
Where <slug> = topic lowercased, spaces to dashes, e.g. policy-compression-ai-agents.
Create .research-loop/sessions/<slug>/lab_notebook.md with:
# Lab Notebook — <topic>
Started: <date>
Status: exploring
---
## Session log
This file is the single source of truth for the entire research session. Every phase appends to it.
Say:
"I'll explore [topic]. Is this the right framing, or do you want to adjust it first?"
Wait for confirmation. Then append to lab_notebook.md:
## Framing
Topic: <confirmed topic>
Date: <date>
Researcher notes: <anything they said about prior knowledge>
Dispatch ALL four researcher subagents simultaneously. Each task references the researcher agent definition (.claude/agents/researcher.md) and must follow its integrity commandments (no fabricated sources, URL-or-it-didn't-happen, read-before-summarize), use the numbered evidence table format (ID, Source, URL, Key claim, Type, Confidence), and apply the source quality tiers (A = peer-reviewed papers/official docs, B = reputable secondary, C = accept with caveats).
Agent 1 (researcher):
Task: Find the top 10 most important papers on [topic].
Use web search. For each paper return: title, year, authors, 1-sentence contribution.
Prioritize foundational and recent (2020–2025) papers. Return a clean numbered list.
Use the numbered evidence table format from the researcher agent definition.
Save findings to .research-loop/sessions/<slug>/findings-papers.md.
Agent 2 (researcher):
Task: Find active GitHub repos and benchmarks for [topic].
Use web search. For each repo return: name, URL, stars (if available), 1-sentence description.
Return 5–10 actively maintained repos. Use cited evidence table format.
Save findings to .research-loop/sessions/<slug>/findings-repos.md.
Agent 3 (researcher):
Task: Find 3 places where experts in [topic] fundamentally disagree.
Use web search. For each debate: name it, state Side A's strongest argument, state Side B's strongest argument, explain why it matters.
Use evidence table format with numbered sources.
Save findings to .research-loop/sessions/<slug>/findings-debates.md.
Agent 4 (researcher):
Task: Find explicit open problems stated in the [topic] literature.
Use web search. Look for "future work" sections, unsolved challenges, gaps mentioned by field leaders.
For each gap: state the problem, cite where it appears, explain why it's hard.
Return 5–8 specific open problems. Use numbered evidence table format.
Save findings to .research-loop/sessions/<slug>/findings-gaps.md.
Tell the user: Searching papers, repos, debates, and open problems in parallel using researcher agents...
IMPORTANT: Each dispatched subagent must follow the researcher agent's 6 integrity commandments and output format defined in .claude/agents/researcher.md. Key rules: every entry needs a URL, no fabricated sources, mark status honestly, triage before fetching full content, write findings to file progressively.
When all 4 return, append the full results to lab_notebook.md:
## Literature (Phase 1)
<full list of papers with title, year, contribution>
## Active Repos
<list of repos>
## Field Debates
<3 debates with both sides and strongest arguments>
## Stated Open Problems
<list of gaps found in literature>
Then show the user a synthesis (not the raw dump):
"Here's the landscape in 3 sentences: [synthesis]
The 3 most interesting angles I see: A) [angle] — [why interesting] B) [angle] — [why interesting] C) [angle] — [why interesting]
Which direction do you want to go deeper on?"
Wait for response. Append their choice to lab_notebook.md:
## Researcher direction choice
Chose: <their answer>
Reasoning they gave: <anything they said>
Now spawn 1 focused search:
Agent: What are the 5 core mental models every expert in [chosen direction] carries?
Not facts — the intuitions and ways of thinking that take years to develop.
Show the models conversationally, one at a time:
"Here's the first mental model experts in this space share: [model 1 + explanation]. Does this match your intuition?"
Append all 5 to lab_notebook.md:
## Mental Models
1. [name]: [description]
2. ...
Say:
"Let me give you 3 questions that would expose whether someone truly understands this vs. memorized it. Try answering them — every wrong answer tells us something."
Show questions one at a time. Wait for answers. For each wrong answer:
"Here's what you're missing: [explanation]"
Append to lab_notebook.md:
## Diagnostic Q&A
Q1: [question]
Researcher answer: [their answer]
Expert answer: [correct answer]
Gap identified: [what they didn't know]
...
Say:
"Exploration complete. Lab notebook saved to
.research-loop/sessions/<slug>/lab_notebook.mdReady to find the gaps and run the Carlini gate? →
/gapor just tell me which open problem interests you most."
This skill dispatches the researcher subagent (.claude/agents/researcher.md) for parallel evidence gathering. The researcher agent definition encodes:
testing
Plan and execute a structured replication workflow for a paper, claim, or benchmark with environment selection and integrity checks.
testing
End-to-end paper generation pipeline ported from AutoResearchClaw (Aiming Lab). 14 phases covering topic initiation through export/publish, with human- in-the-loop gates and quality gating at each handoff. Use this when the user wants a full paper pipeline run — topic to submission-ready manuscript. Delegates to researcher/reviewer/writer/verifier subagents for stage execution and to autonomous-iteration for experiment optimization loops.
testing
Run a structured literature review on a topic using parallel search, evidence tables with quality scoring, and primary-source synthesis.
development
Publication-quality figure generation for research papers. Decision agent selects figure type (code plot vs architecture diagram). Generates Matplotlib/Seaborn code for quantitative figures with iterative improvement loop. Style-matches conference templates (NeurIPS, ICML, ICLR). Use when the paper-pipeline reaches the figure generation phase, or when a user requests figures for an existing draft.