recursive-research

Conducts self-regulated recursive research loops with source tiering and disk checkpointing.

Updated Aug 12, 2026
One-click install
npx skills add https://github.com/Barbaros911/As-mine --skill recursive-research-barbaros911
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: recursive-research
Source: https://github.com/Barbaros911/As-mine/tree/main/.claude/skills/recursive-research
Command: npx skills add https://github.com/Barbaros911/As-mine --skill recursive-research-barbaros911

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Deep research on a new topic often stalls at shallow web searches, loses progress when a session ends, and lacks measurable criteria for knowing when you have reached expert-level understanding. This Skill runs an autonomous, self-regulated investigation loop that iterates on a research seed until PhD-level coverage criteria are met, checkpointing every cycle to disk so work survives context limits and session closures. ## Core Features & Use Cases - Self-regulated research loop: Iterates cycles of thread selection, source evaluation, and consolidation until five measurable closure criteria are met (coverage, Tier-1 sources, saturation, Munger inversion, cross-thread synthesis), with a configurable hard cycle cap. - Transparent source tiering: Classifies every consulted source into Tier 1/2/3 or auto-rejected, applying Weighted Decision Matrix (WDM) and Munger inversion to avoid bias and include dissenting voices. - Defensive checkpointing and resume: Writes per-cycle checkpoints, state, threads, findings, and gaps to memoria/investigaciones/<slug>/, with --resume and --list modes to continue across sessions. - Use Case: A researcher investigating episodic memory mechanisms in humans invokes the skill in mixed mode with a local papers folder, prioritizes authors like Tulving and Maguire, and receives a structured workspace with synthesis, action checklist, and documented knowledge gaps after the loop converges. ## Quick Start Ask the AI to run /recursive-research and answer its questions about your research topic, mode (web, local, or mixed), and preferred sources to begin the investigation.

Frequently Asked Questions about recursive-research

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run a deep recursive research session on a topic?▼

Invoke /recursive-research and answer the skill's questions: research seed, mode (web, local, or mixed), local paths if applicable, prioritized or excluded sources, and a cycle cap (default 20). The skill then generates seed threads, selects sources, and iterates until closure criteria are met.

How does recursive research decide when a topic is fully investigated?▼

Closure requires all five criteria: at least 80% coverage on every seed thread, three or more Tier-1 sources per thread, saturation at or below 5% for three consecutive cycles, a documented Munger inversion of knowledge gaps, and at least three explicit cross-thread connections.

Can I resume an interrupted research investigation in a new session?▼

Yes. Every cycle is checkpointed to memoria/investigaciones/<slug>/ on disk. Invoke /recursive-research --resume <slug> to reload state, threads, and the latest cycle, or use --list to see all saved investigations with their status.

What sources does the skill trust for academic research?▼

Sources are tiered transparently: Tier 1 includes peer-reviewed papers, academic publishers, and official standards bodies; Tier 2 covers official repositories and citable expert authors; Tier 3 is used with caution. Sources without identifiable authors or empirical data are automatically rejected.

What happens when the research session approaches the context limit?▼

When tool calls reach 150 or output tokens approach 80000, the skill writes a full checkpoint and recommends a preventive pause. You can continue briefly or pause and resume later in a fresh session without losing progress.