research-task
Skill64 starsChanged 4 months agoMITView on GitHub
Execute a research task using compositional workflow planning. Characterizes the task, selects an approach from a library of research strategies, executes it, and self-evaluates output quality.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- ymatrix1/vantagetheir own version, first seen Oct 17, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- ymatrix1/vantage★ 17same name
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 repository102 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- assumptionsSkill
- capture-learningSkill
- Codex-opus-4-6-promptingSkill
- Codex-promptSkill
- mcp-code-modeSkill
- deploy-team-hubSkill
- diagramSkill
- distillSkill
- effect-tsSkill
- escalateSkill
- evalSkill
- experimentSkill
- hddSkill
- hub-auditSkill
- hub-collabSkill
- implementSkill
- knowledgeSkill
- peer-notebook-delivery-guardSkill
- session-reviewSkill
- source-command-hdd-decideSkill
- source-command-hdd-hddSkill
- source-command-hdd-researchSkill
- source-command-hdd-stage-adrSkill
- source-command-hdd-validateSkill
- statusSkill
- supabaseSkill
- synthesizeSkill
- tasteSkill
- teamSkill
- test-suiteSkill
- theseus-protocolSkill
- thoughtbox:debugSkill
- thoughtbox:decisionSkill
- thoughtbox:evolutionSkill
- thoughtbox:knowledge-querySkill
- thoughtbox:onboardSkill
- thoughtbox:refactorSkill
- thoughtbox:researchSkill
- thoughtbox:session-reviewSkill
- thoughtbox-teamSkill
- ulc-loopSkill
- ulysses-protocolSkill
- workflow-brainstormingSkill
- workflow-ideationSkill
- workflow-reflectionSkill
- workflow-revisionSkill
- workflows-compoundSkill
- workflowSkill
- workflows-planSkill
- workflows-reviewSkill
- workflows-workSkill
- workflow-tournamentSkill
- assumptionsSkill
- capture-learningSkill
- claude-opus-4-6-promptingSkill
- claude-promptSkill
- mcp-code-modeSkill
- deploy-team-hubSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 3 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
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 38
Use retrieved workflows to inform Phase 2 strategy selection.
- Distinctive: line 74
Don't just pick one strategy.
- Distinctive: line 113
If composite score exceeds the current occupant of this behavioral region, the composed workflow becomes a candidate for library insertion.
≈ “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
Research this topic: $ARGUMENTS
Workflow
Phase 1: Task Characterization
Rate the research task on each dimension (1-5):
| Dimension | 1 (Low) | 5 (High) |
| Scope | Point question (single fact) | Frontier mapping (state of entire field) |
| Domain structure | Single field, established methods | Distant cross-domain analogy |
| Evidence type | Empirical data, measurements | Theoretical arguments, first-principles |
| Time horizon | What's true right now | What could become true (speculative) |
| Fidelity | Ballpark / directional | Rigorous / publication-grade |
Phase 1b: Workflow Library Query
Query the MAP-Elites workflow library for strategies matching this task's coordinates:
sqlite3 research-workflows/workflows.db "SELECT id, name, archetype, fitness_score FROM workflows WHERE status IN ('active', 'seed') ORDER BY fitness_score DESC LIMIT 10;"For more targeted retrieval, filter by behavioral region:
sqlite3 research-workflows/workflows.db "SELECT w.id, w.name, ws.name as step_name, ws.description, ws.rationale FROM workflows w JOIN workflow_steps ws ON w.id = ws.workflow_id WHERE w.archetype = '<archetype>' AND w.status IN ('active', 'seed') ORDER BY w.fitness_score DESC, ws.step_order;"Use retrieved workflows to inform Phase 2 strategy selection. Prefer workflows with high fitness scores and usage counts.
Phase 2: Strategy Selection
Based on the characterization and library query, select the most appropriate research archetype:
Exploratory (high scope, moderate fidelity)
- Quick landscape scan — 15-minute overview of a new area
- Deep literature review — comprehensive survey of a mature field
- Trend detection — what's gaining momentum
- White space identification — what isn't being worked on that should be
Confirmatory (low scope, high fidelity)
- Fact-checking pipeline — verify specific claims with primary sources
- Consensus mapping — what do experts agree/disagree on
- Replication check — has this finding held up under scrutiny
Analytical (moderate scope, high evidence)
- Compare and contrast — systematic comparison of N approaches
- Root cause analysis — why did X happen / why doesn't X work
- Cost-benefit analysis — should we do X given tradeoffs
- Forecasting — given current trends, what's likely
Generative (high domain structure, moderate time horizon)
- Cross-domain transfer — find solutions from field B for problems in field A
- First-principles derivation — reason from fundamentals, not literature
- Synthesis — combine N existing ideas into a novel framework
- Adversarial stress-test — find the strongest objections to X
Applied (low time horizon, high fidelity)
- Technical feasibility assessment — can X be built with current tools
- Build-vs-buy analysis — build or use existing solution
- Implementation planning — how to execute X given constraints
Phase 3: Compositional Planning
Don't just pick one strategy. Identify which sub-techniques from multiple strategies suit this specific task:
- Select 2-3 relevant archetypes from Phase 2
- For each, identify the steps that apply to this task
- Note why each step exists (what it optimizes for)
- Compose a novel workflow combining the best elements
- Record which elements were borrowed from which archetype
Phase 4: Execution
Execute the composed workflow using available tools:
- WebSearch — broad web queries
- Exa (
web_search_exa,web_search_advanced_exa) — semantic/neural search, cross-domain retrieval - WebFetch — deep read of specific URLs
- Firecrawl (
firecrawl_scrape,firecrawl_search) — structured web scraping - GitHub — repository search, code search, trending
- Read/Glob/Grep — local codebase and documentation
Phase 5: Self-Evaluation
Score your output on each dimension (0-1):
- Coherence — Does it tell a consistent story? Internal contradictions?
- Grounding — Are claims supported by retrieved evidence?
- Compression — Can key findings be stated concisely? (If not, thesis may be unclear)
- Surprise — Did anything non-obvious surface? (Confirming the known has low value)
- Actionability — Does the output enable a decision or next step?
Report the scores honestly. Low scores on surprise or actionability are useful signals — they indicate the research question may need reframing.
Phase 5b: Library Update
Log this execution and update the workflow library:
# Log the execution
sqlite3 research-workflows/workflows.db "INSERT INTO executions (task_description, task_scope, task_domain_structure, task_evidence_type, task_time_horizon, task_fidelity, score_coherence, score_grounding, score_compression, score_surprise, score_actionability, score_composite) VALUES ('<description>', <scope>, <domain>, <evidence>, <horizon>, <fidelity>, <coherence>, <grounding>, <compression>, <surprise>, <actionability>, <composite>);"If composite score exceeds the current occupant of this behavioral region, the composed workflow becomes a candidate for library insertion.
Phase 6: Output
## Research: [Topic]
### Characterization
Scope: [1-5] | Domain: [1-5] | Evidence: [1-5] | Horizon: [1-5] | Fidelity: [1-5]
### Strategy
[Which archetypes were combined and why]
### Findings
[Structured findings — use headers, tables, or lists as appropriate]
### Quality Assessment
Coherence: [0-1] | Grounding: [0-1] | Compression: [0-1] | Surprise: [0-1] | Actionability: [0-1]
### Key Takeaway
[Single paragraph — the compressed thesis]
### Recommended Next Steps
[What to do with these findings]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.

