research-workflow
Skill1 starsChanged 7 months agoMITView on GitHub
Manage resumable research runs under `research/` and coordinate the collect, review, report, import, and archive steps.
14 other projects use a version of this.
Adopted by
Most recently taken up by
- ranveerankhira-gif/research-agent-skills-zhtheir own version, first seen Nov 15, 2026
- frontdesk-alhouse/alto-ostheir own version, first seen Nov 8, 2026
- GEUConn/research-idea-workflow-skilltheir own version, first seen Nov 1, 2026
- Bigsillymao/zotero-obsidian-ai-workflowtheir own version, first seen Oct 25, 2026
- crce-ux/research-workflowtheir own version, first seen Oct 20, 2026
- microsoft/ArgusAgenttheir own version, first seen Oct 16, 2026
Other versions14 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 14
- microsoft/ArgusAgent★ 140same name
- yoloshii/gigaxity-deep-research★ 61same name
- RipeMangoBox/BITE★ 60same name
- TenureAI/PhD-Zero★ 52same name
- sherifican/Agent-FleetOps★ 34same name
- GEUConn/research-idea-workflow-skill★ 17same name
- Bigsillymao/zotero-obsidian-ai-workflow★ 2same name
- frontdesk-alhouse/alto-os★ 1same name
- mageyuki/skills★ 1same name
- crce-ux/research-workflow★ 0same name
4 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.
In this repository9 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .codex/AGENTS.mdAGENTS.md
- .claude/CLAUDE.mdCLAUDE.md
- CLAUDE.mdCLAUDE.md
- compile-wikiSkill
- ingest-sourcesSkill
- lint-healSkill
- qa-agentSkill
- render-outputSkill
The file
We split this skill into the rules it gives an agent
3 rules. 0 are common, 2 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 8 edited versions we read keep these.
2
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 9
Run higher-stakes topics as resumable, tiered research threads outside the curated vault until they are ready to promote.
- Very specific: line 33
Keep active run files in research/, not in notes/.
- Distinctive: line 34
Treat imported model-generated reports as leads, not authority.
“Common” is measured: kept by at least 6 in 10 of the 8 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
Research Workflow
Goal
Run higher-stakes topics as resumable, tiered research threads outside the curated vault until they are ready to promote.
Use When
- The user wants a structured research run rather than an immediate vault answer.
- A topic needs source collection, contrarian review, and a final report.
- An external model report should be imported as a lead, not treated as authority.
Core Flow
- Start a run:
uv run kops research-start --topic "<text>" --tier <fast|standard|deep>. - Check status:
uv run kops research-status [topic|all]. - Collect sources:
uv run kops research-collect --agent <codex|claude|gemini> --topic "<topic>"(runs collect prompt). - Adversarial review:
uv run kops research-review --agent <codex|claude|gemini> --topic "<topic>"(runs review prompt). - Draft report:
uv run kops research-report --agent <codex|claude|gemini> --topic "<topic>"(runs report prompt). - Import external reports:
uv run kops research-import --topic "<topic>" --path <file> --provider <provider> --origin <origin>. - Archive completed run:
uv run kops research-archive --topic "<topic>"(after phase showsdone).
Phase Guidance
The research-collect, research-review, and research-report CLI subcommands render their own runtime prompts (from kops/templates/), so no separate skill is needed. When running or reviewing a phase by hand, hold to these contracts:
- Collect (
research-collect): populate the findings file with high-signal, sourced claims. Create/update source notes innotes/Sources/under the strict metadata schemas; prefer primary sources; mark imported model reportsauthority: lead_only+verification_state: needs_primary_sources. Distinguish evidence from inference; keep uncertainty explicit; append a progress log. - Review (
research-review): adversarial contrarian pass — try to break the thesis, not confirm it. Populate## Strongest Objections,## Missing Evidence,## Claims To Softenwith genuine gaps (never fabricated counter-evidence); name missing primary sources to consult before drafting. - Report (
research-report): synthesize brief + sources + findings + contrarian review into a bounded report. Build from collected evidence only, address the strongest objections, keep conclusions bounded by evidence, cite source summaries with wikilinks, and distinguish established from provisional findings.
Rules
- Keep active run files in
research/, not innotes/. - Treat imported model-generated reports as leads, not authority.
- Preserve the status/progress/review/report linkage across steps.
- Promote durable findings into the main vault only after verification.
Outputs
research/briefs/(brief files:type: research-brief)research/notes/(status:type: research-status, progress:type: research-progress, review:type: research-review)research/findings/(findings:type: research-findings)research/reports/(reports:type: research-report)research/imports/(manifest:type: research-import-manifest)research/archive/(manifest:type: research-archive-manifest)
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.

