Agent skill

Deep Research

by Abilityai in Abilityai/cornelius

Autonomous research pipeline - discover, extract, and integrate cutting-edge insights into knowledge base

MITAuto-check: notesResearch & Science

Install Deep Research

skills CLI
$ npx skills add Abilityai/cornelius --skill deep-research -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install Abilityai/cornelius deep-research --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/Abilityai/cornelius.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/deep-research .claude/skills/deep-research && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
deep-research
GitHub stars
109
Token cost
~5.6k tokens
SKILL.md length
1,345 words
Files
1
Skills in repo
56
Repo updated
First seen
Licence
MIT

At a glance

Autonomous research pipeline - discover, extract, and integrate cutting-edge insights into knowledge base

  • Works in 6 steps: Topic Selection & Research Planning → Execute Research → Extract Insights → …
  • Tasks that involve Deep research
  • SKILL.md covers Input Processing, Mission, Phase 1: Topic Selection &… and Phase 2: Execute Research, plus 5 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Deep Research is an agent skill from Abilityai/cornelius. Autonomous research pipeline - discover, extract, and integrate cutting-edge insights into knowledge base

Its SKILL.md is about 5.6k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Research & Science, covering Deep research and Knowledge bases. The repository describes itself as: AI-powered second brain template for Claude Code + Obsidian. The licence is MIT.

When your agent uses it

  • Tasks that involve Deep research
  • Tasks that involve Knowledge bases

Example prompts

  • “/deep-research”

Requirements

  • Pre-approved tools (allowed-tools): Task, Read, Bash, Glob, Grep

Workflow steps

6 steps, taken from the step headings in SKILL.md.

  1. Topic Selection & Research Planning
  2. Execute Research
  3. Extract Insights
  4. Insight Interview (Optional)
  5. Connection Discovery
  6. Final Summary & Recommendations

What it can do on your machine

Read from SKILL.md and the folder at commit fd5e9a4. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves these tools, so the agent can use them without asking each time:

    • Task
    • Read
    • Bash
    • Glob
    • Grep

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are bash and markdown).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Deep Research loads about 5.6k tokens when it runs. Until then it costs about 30 tokens; SKILL.md has 1,345 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~30
When it runs · the whole SKILL.md, loaded when a task matches
~5.6k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check: notes

The automated check noted patterns worth knowing about, such as sudo or a known installer.

  • NotePre-approves every shell command (allowed-tools: Bash)SKILL.md
    allowed-tools: Task, Read, Bash, Glob, Grep

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from Abilityai/cornelius at commit fd5e9a4, republished under its MIT licence (© Abilityai). 1,345 words, ~5,586 tokens.

Download SKILL.mdSave it as .claude/skills/deep-research/SKILL.md (or your agent's skills folder).
name
deep-research
description
Autonomous research pipeline - discover, extract, and integrate cutting-edge insights into knowledge base
allowed-tools
Task, Read, Bash, Glob, Grep
argument-hint
optional topic or "auto" for autonomous selection
automation
gated

Deep Research & Knowledge Integration Pipeline

You are orchestrating a fully autonomous research → extraction → connection discovery workflow to expand the knowledge base with cutting-edge insights.

Input Processing

User Input: $ARGUMENTS

Execution Modes:

  1. Directed Mode - User specifies topic(s): $ARGUMENTS = "neuroscience of habits" or $ARGUMENTS = "multi-agent systems, safety alignment"
  2. Autonomous Mode - You select topics: $ARGUMENTS = "" or $ARGUMENTS = "auto"

Mission

Execute a complete 3-phase autonomous research pipeline:

  1. RESEARCH - Gather cutting-edge papers and developments
  2. EXTRACT - Pull unique insights from research findings
  3. CONNECT - Map connections to existing knowledge base

Critical Requirement: ALL extracted insights MUST be stored in Document Insights folder structure to keep separate from main Brain.


Phase 1: Topic Selection & Research Planning

A. If User Provided Topic(s) (Directed Mode)
  • Parse $ARGUMENTS for topic(s)
  • Validate topics are research-worthy
  • Plan research scope for each topic
B. If Autonomous Mode

Analyze knowledge base to identify research opportunities:

  1. Read knowledge base analysis:

    bash
    cat knowledge-base-analysis.md
  2. Check recent activity:

    bash
    ls -lt Brain/Document\ Insights/ | head -10
  3. Identify gaps based on:

    • Underrepresented domains in knowledge-base-analysis.md
    • Missing connections flagged in recent changelogs
    • Emerging themes from existing insights
    • User's recent work patterns
    • CLAUDE.md priorities and future directions
  4. Select 1-3 research topics that would:

    • Fill identified gaps
    • Build on existing strengths (e.g., Buddhism-Neuroscience-AI triangle)
    • Connect underexplored domains
    • Add empirical validation to intuitive frameworks
    • Challenge or extend current thinking

Examples of Good Topic Selection:

  • "Neuroscience of habits and behavior change" (if habit formation underrepresented)
  • "Collective intelligence and swarm behavior" (if group dynamics missing)
  • "Embodied cognition and interoception" (if embodiment gap identified)
  • "Complexity science and emergence" (if systems thinking needed)
  • "Creativity neuroscience and insight generation" (if creative process mechanics missing)

Phase 2: Execute Research

Get Current Timestamp
bash
date '+%Y-%m-%d %H:%M:%S %Z'

Save this for session folder naming: YYYY-MM-DD Topic Description

Launch Research Specialist Agent(s)

For Each Topic:

Use Task tool with subagent_type='research-specialist':

TOPIC: [Selected topic]

Conduct comprehensive research on [topic] focusing EXCLUSIVELY on the most recent research and developments.

⚠️ CRITICAL RECENCY REQUIREMENT:
Your training data may be outdated. The world changes rapidly, especially in fast-moving fields like AI, neuroscience, and technology. You MUST prioritize the most recent information available through web search, even if it contradicts what you think you know from training data.

⚠️ SOURCE QUALITY REQUIREMENT (recency is NOT enough):
Recent does not mean credible. Prefer the PRIMARY source over anyone summarizing it - the actual paper, lab page, or official doc, not a content-farm writeup, an AI-generated summary, a single-tweet leak, or an SEO explainer. Reject machine-generated and regurgitated material. For each finding, record which source it came from so downstream extraction can tier it. (The per-domain source diet is the canonical `resources/SOURCE-AUTHORITY.md`; the document-insight-extractor applies it at extraction time.)

SEARCH STRATEGY:
- Use Google Search grounding to find papers published in the last 12-18 months
- Explicitly search for "2024", "2025", "2026", "recent", "latest" in queries
- Check paper publication dates - reject anything older than 2024 unless foundational
- Look for preprints, conference proceedings, and recent journal publications
- Prioritize arXiv papers from last 6 months, conference papers from 2024-2026
- Search for "state of the art [topic] 2025" or "[topic] breakthrough 2026"

RESEARCH REQUIREMENTS:

1. **Target Sources (RECENT ONLY):**
   - arXiv preprints (2024-2026, prioritize last 6 months)
   - Major conferences 2024-2026 (NeurIPS, ICML, ICLR, AAAI, ACL, EMNLP, etc.)
   - Leading AI labs recent publications (OpenAI, Anthropic, Google DeepMind, Microsoft Research)
   - Top-tier journals (2024-2026 issues only)
   - Industry whitepapers and blog posts from major tech companies (last 12 months)
   - Recent preprints and working papers

2. **Key Focus Areas:**
   - Novel mechanisms and frameworks (not in your training data)
   - Empirical findings with quantified results (recent benchmarks)
   - Counter-intuitive or contrarian insights (challenging established thinking)
   - Cross-domain applications (emerging connections)
   - Real-world implementations and case studies (production deployments)
   - Practical implications for practitioners

3. **Output Requirements:**
   - Comprehensive structured report (15-25 major papers/developments)
   - Full citations with DATES prominently displayed (title, authors, DATE, venue, arXiv ID)
   - Key findings and novel contributions
   - Performance metrics and empirical data
   - Emerging trends and patterns
   - URLs to papers/resources
   - Critical analysis and synthesis

4. **Save Location:**
   resources/[Topic-Slug]-Research-Report-YYYY-MM-DD.md

VERIFICATION: Before finalizing, verify that 80%+ of papers are from 2024-2026. If not, search again with more explicit recency filters. Also verify the sources are credible primaries (actual papers/labs/official docs), not content-farm pages or AI-generated summaries.

Use Gemini AI with Google Search grounding. Trust the search results over your training data.

Strategy Considerations:

  • Sequential: Run topics one-by-one if they're related (later research can reference earlier findings)
  • Parallel: Run multiple topics simultaneously if they're independent domains
  • Your choice - decide based on topic relationships and efficiency
Monitor Research Output

After each research agent completes:

  1. Note the report file path
  2. Verify comprehensive coverage (15-25+ papers)
  3. Check for citations and empirical data
  4. Confirm report saved in /resources/ directory

Phase 3: Extract Insights

Create Session Folder

Format: YYYY-MM-DD [Topic Description]

Example: 2025-11-20 Neuroscience of Habits and Behavior Change

Path: Brain/Document Insights/[Session-Folder]/

Launch Document Insight Extractor

For Each Research Report:

Use Task tool with subagent_type='document-insight-extractor':

Extract unique insights from the research report for the knowledge base.

SOURCE DOCUMENT: [Full path to research report]

SESSION FOLDER: [Session folder name]

EXTRACTION GUIDELINES:

1. **Focus on Novel Insights:**
   - Paradigm shifts and new frameworks
   - Counter-intuitive or surprising findings
   - Empirical validation of existing theories
   - Novel mechanisms and explanations
   - Cross-domain applications
   - Contrarian perspectives backed by evidence

2. **Bridge to Existing Knowledge Base:**
   - Connect to the 6 primary hubs: Consciousness, Dopamine, Decision-Making, Identity, AI Agents, Flow States
   - Reference the user's existing frameworks (Folder Paradigm, Mental Models Taxonomy, etc.)
   - Identify consilience opportunities (3+ domains converging)
   - Find validation or challenges to current thinking
   - Look for applications of Buddhist/neuroscience principles

3. **Prioritize:**
   - Research findings that extend current understanding
   - Empirical data that validates intuitive frameworks
   - Novel architectures or methodologies
   - Real-world implications and case studies
   - Philosophical or meta-level insights

4. **Quality Standards:**
   - 15-25 high-quality insights per report
   - Avoid redundancy with existing knowledge base (ALWAYS search for duplicates)
   - Include proper citations (paper title, authors, year)
   - Tag appropriately for discoverability
   - Create connections to existing permanent notes

5. **Output Requirements:**
   - Create permanent notes in session folder
   - Include full citations and sources
   - Add relevant tags
   - Note connections to existing insights
   - Create changelog: CHANGELOG - Document Analysis YYYY-MM-DD.md

CRITICAL:
- ALWAYS search for duplicates before creating notes
- Store ALL extracted notes in: Brain/Document Insights/[Session-Folder]/
- Create comprehensive changelog documenting extraction process
Monitor Extraction Output

After extraction completes:

  1. Verify insights stored in correct Document Insights session folder
  2. Check changelog was created
  3. Note count of unique insights extracted
  4. Confirm deduplication was performed

Phase 4: Insight Interview (Optional)

After extraction completes, present the top findings and offer to run an insight interview before connection discovery. This captures your personal perspective alongside the external research - making the final connection map richer because it maps both what the research says AND what you actually think about it.

Present Top Insights

Summarize the 5-8 most significant extracted insights from the session folder:

  • List note titles with one-sentence descriptions
  • Highlight findings that challenge existing KB frameworks or contradict current notes
  • Flag any surprising or counterintuitive results
[APPROVAL GATE] - Run Insight Interview?

Present to user:

"[N] insights extracted on [topic]. Before connection discovery, would you like to do a quick insight interview? I'll ask you 6-8 questions grounded in your existing notes and these new findings - to capture YOUR angles, reactions, and disagreements. Your responses save to Brain/AI Extracted Notes/ and the connection finder will map both sets together.

Say yes to run the interview, or skip to go straight to connection discovery."

If yes: Invoke the insight-interview skill for the current topic.

  • The dialogue runs here - one question at a time
  • User insights saved to Brain/AI Extracted Notes/
  • Note the session timestamp so connection discovery can include these new notes

If skip: Proceed directly to Phase 5.

Update Scope for Connection Discovery

If the interview ran, Phase 5 should map connections across both:

  • External research: Brain/Document Insights/[Session-Folder]/
  • Personal insights: new notes created in Brain/AI Extracted Notes/ during this session

Phase 5: Connection Discovery

Launch Connection Finder Agent(s)

Strategy Options:

Option A: Single Comprehensive Pass

  • Run connection-finder once on the entire session folder
  • Maps all new insights against full knowledge base

Option B: Multiple Targeted Passes

  • Run connection-finder 2-3 times on different subsets
  • First pass: New insights ↔ Existing AI insights (102 notes)
  • Second pass: New insights ↔ Primary hubs (Dopamine, Consciousness, etc.)
  • Third pass: Cross-domain bridges and synthesis opportunities

Your Choice - Select based on insight count and domain diversity.

Execute Connection Discovery

Use Task tool with subagent_type='connection-finder':

Discover connections between newly extracted insights and existing knowledge base.

STARTING POINTS:
All notes in session folder: Brain/Document Insights/[Session-Folder]/

Or specify individual notes if doing targeted passes.

CONNECTION DISCOVERY GOALS:

1. **Bridge to Existing Knowledge:**
   - Connect to 102 existing AI insights
   - Link to 6 primary thematic hubs (Consciousness, Dopamine, Decision-Making, Identity, AI Agents, Flow)
   - Find relationships to original frameworks (Folder Paradigm, Mental Models Taxonomy, etc.)
   - Map to MOCs and output content

2. **Cross-Domain Opportunities:**
   - Buddhism ↔ Neuroscience ↔ AI consilience
   - Decision Science ↔ Agent Architecture
   - Flow States ↔ Peak Performance ↔ AI Optimization
   - Identity/Belief Systems ↔ Agent Fitness Functions
   - Dopamine hub connections (universal bridge)

3. **Synthesis Identification:**
   - Clusters of insights ready for article development
   - Consilience zones (3+ domains converging)
   - Emergent patterns and meta-insights
   - Framework extension opportunities
   - New MOC candidates

4. **Analysis Parameters:**
   - Similarity thresholds: 0.65-0.85 (strong to moderate)
   - Depth: 2-3 levels from each new insight
   - Focus: Non-obvious, high-value connections

5. **Output Requirements:**
   - Map direct connections to existing permanent notes
   - Identify bridge notes connecting multiple domains
   - Highlight consilience zones and synthesis opportunities
   - Create dated changelog: CHANGELOG - Connection Discovery Session YYYY-MM-DD.md
   - Store changelog in: Brain/05-Meta/Changelogs/
   - Update master changelog: Brain/CHANGELOG.md
   - Suggest concrete article topics or framework extensions

Begin comprehensive connection mapping.
Monitor Connection Discovery

After connection-finder completes:

  1. Verify changelog created in /Brain/05-Meta/Changelogs/
  2. Check master CHANGELOG.md was updated
  3. Note key findings: consilience zones, synthesis opportunities
  4. Identify high-priority article topics

Phase 6: Final Summary & Recommendations

Consolidate Results

Generate a comprehensive session report including:

markdown
# Deep Research Pipeline - Session Summary
**Date:** [Timestamp]
**Execution Mode:** [Directed / Autonomous]
**Topics Researched:** [List]

---

## Phase 1: Research
**Topics Selected:**
1. [Topic 1] - Rationale: [Why chosen]
2. [Topic 2] - Rationale: [Why chosen]
...

**Research Reports Created:**
- [Report 1]: /resources/[filename] ([N] papers analyzed)
- [Report 2]: /resources/[filename] ([N] papers analyzed)

**Total Papers Analyzed:** [N]
**Research Coverage:** [Domains covered]

---

## Phase 2: Insight Extraction
**Session Folder:** /Brain/Document Insights/[Session-Folder]/

**Extraction Results:**
- Unique insights extracted: [N]
- Duplicates avoided: [N]
- Very similar (evaluated): [N]
- Changelogs created: [List paths]

**Insights by Type:**
- Research findings: [N]
- Theoretical frameworks: [N]
- Production insights: [N]
- Contrarian arguments: [N]

**Top Insights:**
1. [[Note Title]] - [Brief description]
2. [[Note Title]] - [Brief description]
...

---

## Phase 3: Connection Discovery
**Changelogs Created:**
- [Path to connection discovery changelog]

**Key Findings:**
- Strong connections discovered: [N]
- Emergent patterns identified: [N]
- Cross-domain bridges: [N]
- Consilience zones: [List]

**Major Cross-Domain Bridges:**
1. [Domain A] ↔ [Domain B] - Mechanism: [How connected]
2. [Domain A] ↔ [Domain C] - Mechanism: [How connected]

**Synthesis Opportunities Identified:**
1. **Article:** "[Title]" - Ready for development
2. **Framework:** "[Name]" - Extension of existing work
3. **MOC Candidate:** "[Topic]" - Needs organization hub

---

## Impact Assessment

**Knowledge Base Enhancement:**
- New research domains added: [List]
- Existing frameworks validated/extended: [List]
- Gaps filled: [List]
- New connections to core hubs: [N]

**Most Significant Discoveries:**
1. [Discovery 1] - Why significant: [Explanation]
2. [Discovery 2] - Why significant: [Explanation]
3. [Discovery 3] - Why significant: [Explanation]

**Contrarian Insights:**
- [Insight that challenges conventional wisdom]
- [Insight that challenges existing framework]

---

## Recommended Next Steps

**High-Priority Actions:**
1. **Write Article:** "[Suggested title]"
   - Sources: [[Note 1]], [[Note 2]], [[Note 3]]
   - Unique angle: [What makes this distinctive]
   - Target audience: [Who would benefit]

2. **Extend Framework:** "[Framework name]"
   - Current state: [What exists]
   - Enhancement: [What research adds]
   - Application: [How to use]

3. **Create MOC:** "[Topic]"
   - Notes to organize: [Count]
   - Structure: [Suggested organization]
   - Purpose: [Navigation goal]

**Medium-Priority:**
- [Additional recommendations]

**Long-Term Opportunities:**
- [Strategic synthesis possibilities]

---

## Session Files Created

**Research Reports:**
- [Path 1]
- [Path 2]

**Insight Notes:**
- [Session folder path] ([N] notes)

**Changelogs:**
- [Extraction changelog path]
- [Connection discovery changelog path]
- Master CHANGELOG.md updated

---

## Knowledge Base Statistics (Updated)

**Before Session:**
- Total permanent notes: [N]
- AI insights: [N]
- Document insights: [N]

**After Session:**
- Total permanent notes: [N] (+[N])
- AI insights: [N]
- Document insights: [N] (+[N])

**Growth:** +[N] notes, +[N] connections

---

## Meta-Analysis

**What Worked Well:**
- [Successes in topic selection, research, extraction, or connection]

**Challenges Encountered:**
- [Any difficulties or limitations]

**Lessons for Future Sessions:**
- [Improvements for next research pipeline run]

---

**End of Deep Research Pipeline Session**

Quality Standards & Best Practices

Show full SKILL.md (542 more words)Show less
Topic Selection (Autonomous Mode)
  • Strategic alignment: Choose topics that build on existing strengths or fill critical gaps
  • Cross-domain potential: Prefer topics that bridge multiple knowledge base hubs
  • Empirical grounding: Select areas with active research (2024-2026 papers available)
  • Practical relevance: Topics should have real-world applications or implications
Research Quality
  • Recency: Prioritize 2024-2026 papers and developments
  • Rigor: Prefer primary sources (the actual paper/lab/official doc) over summaries; reject content-farm and AI-generated regurgitation. See the canonical source diet in resources/SOURCE-AUTHORITY.md.
  • Depth: 15-25 major papers minimum per topic
  • Breadth: Cover multiple perspectives and approaches
  • Empirics: Include quantified results and performance metrics
Insight Extraction
  • Novelty: Only extract genuinely new perspectives
  • Deduplication: ALWAYS search before creating notes
  • Citations: Include full source attribution
  • Connections: Link to existing knowledge base
  • Quality > Quantity: 15-25 high-value insights, not 100 mediocre ones
Connection Discovery
  • Non-obvious focus: Surface-level links are less valuable
  • Cross-domain priority: Consilience zones are gold
  • Synthesis orientation: Identify article/framework opportunities
  • Actionable output: Provide concrete next steps
Documentation
  • Comprehensive changelogs: Document every phase
  • Clear file organization: Session folders in Document Insights
  • Master log updates: Keep CHANGELOG.md current
  • Audit trail: Future-you should understand what happened and why

Execution Protocol

  1. Parse input → Determine directed vs. autonomous mode
  2. Select topics → Either use provided topics or analyze knowledge base for gaps
  3. Get timestamp → For session folder naming
  4. Research phase → Launch research-specialist agent(s)
  5. Extraction phase → Launch document-insight-extractor for each report
  6. Insight interview → Optional gate: present top findings, offer /insight-interview to capture your angles before connection discovery
  7. Connection phase → Launch connection-finder agent(s) across both document and personal insights
  8. Generate summary → Comprehensive session report
  9. Provide recommendations → Actionable next steps for content creation

Key Principle: Fully autonomous execution. No human intervention required between phases. All insights stored in Document Insights folder structure to maintain separation from main Brain.


Error Handling

If research finds insufficient papers:

  • Broaden search criteria
  • Extend date range (include 2023)
  • Consider adjacent topics
  • Document limitation in summary

If extraction finds too many duplicates:

  • Focus on truly novel contributions
  • Look for empirical validation of concepts
  • Seek contrarian perspectives
  • Consider topic was already well-covered

If connection-finder finds weak connections:

  • Topic may be genuinely novel (good!)
  • Increase similarity threshold range
  • Run additional passes on specific hubs
  • Document gap as synthesis opportunity

If any phase fails:

  • Document error in summary
  • Continue with successful phases
  • Provide partial results
  • Recommend retry or alternative approach

Remember: This is a knowledge base expansion engine. Your goal is to systematically grow the user's second brain with cutting-edge, well-integrated insights that enhance his intellectual capabilities and content creation potential.

State Dependencies

SourceLocationReadWriteDescription
Knowledge base analysisknowledge-base-analysis.mdXCurrent KB state for gap analysis
Document InsightsBrain/Document Insights/XXSession folders for extracted insights
Research reportsresources/XXGenerated research reports
ChangelogsBrain/05-Meta/Changelogs/XXSession and discovery changelogs
Master changelogBrain/CHANGELOG.mdXXMaster change log
Local Brain Searchresources/local-brain-search/XVector search for deduplication

Completion Checklist

  • Execution mode determined (directed vs autonomous)
  • Topics selected with rationale
  • Research reports generated and saved to /resources/
  • Session folder created in Document Insights
  • Insights extracted with deduplication
  • Extraction changelog created
  • Insight interview offered (ran or skipped)
  • Connection discovery completed
  • Connection discovery changelog created in /05-Meta/Changelogs/
  • Master CHANGELOG.md updated
  • Session summary generated with recommendations
  • Synthesis opportunities identified

© Abilityai, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .claude/skills/deep-research of Abilityai/cornelius.

Open the folder on GitHubat commit fd5e9a4

Compare with similar skills

Deep Research next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Deep Research compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Deep Research this skillAbilityai/cornelius109—~5.6kAutomated safety check: NotesMIT
Behive Researchqa10devteam/behive146—~1.4kAutomated safety check: PassMIT
Dy NoteRimagination/dy-note1721 repos~4.5kAutomated safety check: PassMIT
Live Researchbrightdata/skills264—~1.8kAutomated safety check: PassMIT
Eunomia Research Reporteunomia-bpf/eunomia.dev236—~3kAutomated safety check: PassMIT
Behive Researchqa10devteam/behive146—~838Automated safety check: NotesMIT

Similar skills

  • Behive Research

    qa10devteam/behive

    A skill your agent uses when the user asks to research a topic deeply, gather intelligence, or build a knowledge base.

    146 GitHub stars~1.4k tokensUpdated 2 days ago
    Knowledge ManagementAuto-check passed
  • Dy Note

    Rimagination/dy-note

    DyNote: systematically and efficiently extract raw Douyin/DY video data and analyze videos, comments, accounts, hashtags, and short-video scenes into evidence-graded learning notes, summaries…

    172 GitHub starsUsed in 1 repo~4.5k tokens
    AI & LLM EngineeringAuto-check passed
  • Live Research

    brightdata/skills

    Produce a deep, multi-source, cited research brief on a topic from live web data using Bright Data's Discover API (intent-ranked web search + parsed page content).

    264 GitHub stars~1.8k tokensUpdated yesterday
    Research & ScienceAuto-check passed
  • Eunomia Research Report

    eunomia-bpf/eunomia.dev

    Research, write, validate, and publish source-grounded Eunomia Daily Reports for technical readers.

    236 GitHub stars~3k tokensUpdated yesterday
    Research & ScienceAuto-check passed
  • Behive Research

    qa10devteam/behive

    Deep research missions with structured claim extraction, quality scoring, and knowledge graphs.

    146 GitHub stars~838 tokensUpdated 2 days ago
    Research & ScienceAuto-check: notes
  • Sends what your notes already know about a topic to Perplexity, so the cited web search reports only what is new, such as entity updates or deal changes.

    31k GitHub stars~2k tokensUpdated yesterday
    Research & ScienceAuto-check: notes

More from Abilityai/cornelius

All 56 skills in this repo
  • Nano Banana Image Generator

    Abilityai/cornelius

    Generate images using Google's Nano Banana (Gemini 2.5 Flash Image).

    109 GitHub stars~1.2k tokensUpdated 15 days ago
    Auto-check: notes
  • Changelog Protocol

    Abilityai/cornelius

    Protocol for creating dated changelog files after significant agent sessions.

    109 GitHub stars~555 tokensUpdated 15 days ago
    Auto-check passed
  • Create Article

    Abilityai/cornelius

    Create long-form articles from knowledge base insights. An agent skill from Abilityai/cornelius.

    109 GitHub stars~2.1k tokensUpdated 15 days ago
    Auto-check: notes
  • Epistemic Classification

    Abilityai/cornelius

    Framework for distinguishing research findings from hypotheses and speculative synthesis.

    109 GitHub stars~1.5k tokensUpdated 15 days ago
    Auto-check passed
  • Get Youtube Transcript

    Abilityai/cornelius

    Extract the transcript from a YouTube video by URL or video ID.

    109 GitHub stars~525 tokensUpdated 15 days ago
    Auto-check: notes
  • Insight Capture Format

    Abilityai/cornelius

    Standard format for capturing and documenting insights in the knowledge base.

    109 GitHub stars~616 tokensUpdated 15 days ago
    Auto-check passed

Questions about Deep Research

What does Deep Research do?

Autonomous research pipeline - discover, extract, and integrate cutting-edge insights into knowledge base. Deep Research is an agent skill from Abilityai/cornelius.

When should I use Deep Research?

Deep Research fits situations like: tasks that involve Deep research; tasks that involve Knowledge bases.

How do I install Deep Research in Claude Code?

Run `npx skills add Abilityai/cornelius --skill deep-research -a claude-code`. Or copy the skill folder (.claude/skills/deep-research in Abilityai/cornelius) into .claude/skills/deep-research in your project. Claude Code loads it when a task matches its description.

How do I install Deep Research in Codex?

Run `npx skills add Abilityai/cornelius --skill deep-research -a codex`. Or copy the skill folder (.claude/skills/deep-research in Abilityai/cornelius) into .agents/skills/deep-research in your project. Codex loads it when a task matches its description.

Can I use Deep Research in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add Abilityai/cornelius --skill deep-research -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/deep-research, .gemini/skills/deep-research, .github/skills/deep-research and .opencode/skills/deep-research in your project.

What does Deep Research need to run?

SKILL.md names no scripts, command-line tools or credentials: Deep Research is instructions for the agent only. Its frontmatter pre-approves these tools: Task, Read, Bash, Glob, Grep.

Does Deep Research access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Deep Research safe to install?

Our automated static check of SKILL.md found notes only (pre-approves every shell command (allowed-tools: bash)), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.

What licence does Deep Research use?

Deep Research is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Deep Research use?

About 5.6k tokens (SKILL.md is roughly 22k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Deep Research?

Skills that share tags, products or a category with Deep Research: Behive Research (qa10devteam/behive, 146 stars), Dy Note (Rimagination/dy-note, 172 stars), Live Research (brightdata/skills, 264 stars) and Eunomia Research Report (eunomia-bpf/eunomia.dev, 236 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Deep Research?

Abilityai (a GitHub organization) maintains it in Abilityai/cornelius, which has 109 GitHub stars. The repository holds 56 skills in this directory. The repository was last updated on September 22, 2026.

Source: Abilityai/cornelius on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.