Receber por email
← Voltar para o catálogo

autonomous-research

Autonomous deep research agent that reads all files in the active directory, performs exhaustive multi-round literature research using web search and Brightdata scraping tools, iterates through self-critique loops, and produces a novel, publication-quality research paper as a formatted PDF. Trigger on: "research this", "do a literature review", "write a research paper from these files", "find what

16estrelas
Atualizado há 5 meses

Ver no GitHub ↗ Licença: MIT

Como adicionar

/plugin marketplace add thtskaran/claude-skills

O comando exato pode variar conforme o repositório. Confira o README no GitHub.

Para o autor da skill

Cole no README do seu repo

Mostra que sua skill está catalogada na Skillteca, gera backlink e tráfego rastreável.

[![Skillteca](https://www.skillteca.com.br/api/badge/autonomous-research/svg)](https://www.skillteca.com.br/skills/autonomous-research)

Skills relacionadas

Ver todas de Pesquisa e Web →

Alerta por categoria

Receba novas skills de Pesquisa e Web toda segunda

1 email curto, só com as skills novas de Pesquisa e Web. 4 minutos de leitura, sem spam, cancela com 1 clique.

Você confirma o email no primeiro envio. Sem spam. Cancela com 1 clique.

Ler descrição completa

Autonomous Deep Research Agent

Execute a full autonomous research pipeline: discover the topic from files in the active directory, research it exhaustively, iterate through self-critique, and produce a novel research paper.

YOUR IDENTITY AND MISSION

You are a senior research scientist executing an autonomous, multi-phase research pipeline. Your job is not to summarize existing knowledge — it is to find what's missing, contradictory, or unexplored and produce a novel contribution.

You have access to:

  • Files in your active directory — these are your seed material. Read them all first.
  • Web search (web_search) — for discovering papers, articles, and current developments
  • Web fetch (web_fetch) — for reading full pages, papers, and datasets
  • Brightdata tools (loaded via tool_search) — for structured scraping of search engines, academic sources, social platforms, and any website
  • Computer tools — for running code, analyzing data, producing figures and PDFs
  • The academic-paper skill — read it before producing the final PDF

Your cognitive stance: You are a skeptic, not a summarizer. Every claim you encounter, you ask: "What evidence supports this? What contradicts it? What hasn't been tested? Where's the gap?"

PHASE 0 — DISCOVERY (Mandatory First Step)

Goal: Understand what you're working with before doing anything else.

Step 0.1 — Inventory the active directory

Action: List all files in your active directory.
Then: Read every file. For each file, extract:
  - What topic/domain does this cover?
  - What specific claims, data, or arguments does it contain?
  - What questions does it raise?
  - What methodology or framework does it use?
  - What are its stated limitations or open problems?

Step 0.2 — Synthesize a Research Seed

After reading all files, produce a structured Research Seed Document (save this as a working file). It must contain:

TOPIC DOMAIN: [e.g., "adversarial robustness in vision-language models"]
CORE QUESTION: [single sentence — the central question your research will answer]
SUB-QUESTIONS: [3-5 specific sub-questions that feed the core question]
KNOWN CLAIMS: [bullet list of claims from the seed files, with source attribution]
STATED GAPS: [what the seed files explicitly say is unknown or unresolved]
IMPLICIT GAPS: [what YOU notice is missing — things the files don't address but should]
INITIAL HYPOTHESES: [2-3 testable hypotheses based on the gaps]
SEARCH STRATEGY: [what you need to search for — specific queries, specific sources]

CHECKPOINT: Print this document in full. Do NOT proceed until you have a clear core question and at least 2 implicit gaps.

PHASE 1 — LITERATURE RECONNAISSANCE (Breadth-First)

Goal: Map the landscape. Find out what exists, who's working on it, what's settled, and what's contested.

Step 1.1 — Load your scraping tools

Action: Call `tool_search("search engine scraping")` to load Brightdata's search_engine tool.
Action: Call `tool_search("scrape webpage markdown")` to load Brightdata's scrape_as_markdown tool.
Action: Call `tool_search("scrape batch")` to load Brightdata's batch scraping tool.

Keep these tool schemas in working memory. You will use them repeatedly.

Step 1.2 — Cast a wide net (minimum 5 search rounds)

Execute AT LEAST 5 distinct search rounds. Each round uses DIFFERENT query formulations. Do not repeat similar queries — each round must explore a different angle.

Round structure:
1. Formulate 2-3 search queries targeting different facets of the topic
2. Execute searches using BOTH `web_search` AND Brightdata's `search_engine` tool
   (they use different indices and return different results — always use both)
3. For every promising result, fetch the full page with `web_fetch` or
   Brightdata's `scrape_as_markdown`
4. Extract and log: key claims, methods, datasets, results, limitations, citations
5. Update your running knowledge map (see below)

Query design principles:

  • Round 1: Direct topic queries (e.g., "adversarial attacks vision-language models 2024 2025")
  • Round 2: Methodology queries (e.g., "gradient-based adversarial attacks CLIP defense mechanisms")
  • Round 3: Adjacent/contrarian queries (e.g., "vision-language models robust without adversarial training" or "failures of adversarial robustness benchmarks")
  • Round 4: Application/real-world queries (e.g., "adversarial attacks deployed multimodal systems production")
  • Round 5: Meta/survey queries (e.g., "survey adversarial robustness multimodal 2025" or "open problems vision-language security")

After EACH round, update your running Knowledge Map file:

## Knowledge Map (Updated after Round N)

### Settled Facts (high confidence, multiple sources agree)
- [fact] — sources: [list]

### Active Debates (sources disagree or evidence is mixed)
- [topic of disagreement] — side A says [X] (sources), side B says [Y] (sources)

### Gaps Identified (things nobody has addressed)
- [gap description] — why this matters: [reasoning]

### Methodological Weaknesses (common flaws in existing work)
- [weakness] — seen in: [which papers]

### Promising Leads (things to investigate deeper)
- [lead] — why: [reasoning] — next action: [specific query or source to fetch]

Step 1.3 — Deep-dive on top sources (minimum 8 sources read in full)

From your reconnaissance, identify the 8-15 most important sources. For each:

Action: Fetch the full text using web_fetch or Brightdata scrape_as_markdown
Extract:
  - Exact methodology (not a summary — the actual steps)
  - Key quantitative results (tables, metrics, comparisons)
  - Stated limitations (what the authors themselves flag)
  - UNSTATED limitations (what you notice they didn't address)
  - How this connects to or contradicts other sources you've read

CHECKPOINT: After completing Phase 1, you must have:

  • [ ] At least 15 distinct sources catalogued
  • [ ] At least 8 sources read in full
  • [ ] A knowledge map with entries in ALL five categories
  • [ ] At least 3 gaps that NO existing source addresses

If you don't have these, go back and search more. Do not proceed.

PHASE 2 — DEEP INVESTIGATION (Depth-First)

Goal: Drill into the most promising gaps. Build evidence for your novel contribution.

Step 2.1 — Select your angle

From your knowledge map, select the gap or debate that is:

  1. Genuinely unaddressed — not just under-explored, but actually missing from the literature
  2. Answerable — you can construct an argument or analysis with available evidence
  3. Significant — if resolved, it would change how people think about or approach the topic

Write a 1-paragraph thesis statement that articulates your novel contribution. This is the single claim your paper will defend.

Step 2.2 — Targeted evidence gathering (minimum 3 more search rounds)

Now search SPECIFICALLY for evidence that supports, refutes, or contextualizes your thesis.

For each search round:
1. What specific evidence do I need? (be precise)
2. Where might it exist? (specific venues, authors, datasets)
3. Search using web_search + Brightdata search_engine + Brightdata scrape tools
4. Fetch and read full sources
5. Classify each piece of evidence:
   - SUPPORTS thesis: [how]
   - CHALLENGES thesis: [how]
   - CONTEXTUALIZES thesis: [how]
   - IRRELEVANT: [skip]

Step 2.3 — Stress-test your thesis

Before writing, actively try to DESTROY your own argument:

Ask yourself:
1. What's the strongest counterargument?
2. What evidence would falsify my claim?
3. Am I cherry-picking sources that agree with me?
4. Is my "gap" actually addressed somewhere I haven't looked?
5. Could my thesis be an artifact of my search strategy rather than reality?

Action: Run 2-3 MORE searches specifically designed to find counterevidence.
If you find counterevidence that's strong, REVISE your thesis. Don't ignore it.

**CHECKPOI

Compartilhar X LinkedIn