Agent skill
research
Conduct comprehensive academic research using OpenAlex, PDF extraction, paper search MCPs, and web search. Always produces comprehensive reports with 5+ evidence cards covering conflicting ideas and best approaches. Integrates academic papers (high weight) and non-academic sources (blogs, docs - lower weight but valuable for SOTA). Use when: (1) Researching software architecture patterns, (2) Finding academic papers on technical topics, (3) Conducting literature reviews, (4) Analyzing research papers for evidence-based decisions, (5) Building evidence cards from papers, (6) Finding related works and citations, or (7) When you need grounded, paper-backed technical recommendations. Triggers: research, find papers, literature review, evidence-based, academic research, compare approaches, what does research say, find studies on, search for papers about.
Install this agent skill to your Project
npx add-skill https://github.com/LukasStrickler/ai-dev-atelier/tree/main/content/skills/research
Metadata
Additional technical details for this skill
- author
- ai-dev-atelier
- version
- 1.0
SKILL.md
Research
Comprehensive academic research using OpenAlex, Paper-search, PDF extraction, and web search (Tavily). Always produces 5+ evidence cards covering conflicting ideas with weighted evidence synthesis.
Quick Start
Decision Tree:
- Need evidence-based decision? → Use this skill
- Quick lookup only? → Use
searchskill instead - Already researched topic? → Run
ada::research:list
Core Workflow:
Step 0: Gather codebase context (ALWAYS FIRST)
Step 1: Formulate research question
Step 2: Comprehensive discovery (25+ sources)
Step 3: Create 5+ evidence cards incrementally
Critical Evaluation: Assess for codebase context
Step 4: Generate comprehensive report
Mandatory Requirements:
- ✅ Always 5+ evidence cards (broad coverage)
- ✅ Explicitly seek conflicting ideas
- ✅ Weight evidence (academic + real-world sources)
- ✅ Codebase context informs research question
CRITICAL: Write-First Pattern
MANDATORY: After 1-2 tool calls:
- Write/update evidence card immediately
- Update
references.jsonimmediately - SAVE files before next tool calls
- CONTINUE research (writing ≠ stopping)
Why: Context windows are limited. Writing preserves knowledge even if context resets.
Failure Modes:
- ❌ 3+ tool calls before writing → context overload
- ❌ Stopping after one card → must continue until complete
- ❌ Not updating
references.json→ loses tracking
Workflow Summary
Step 0: Codebase Context (ALWAYS FIRST)
Search codebase for: architecture, patterns, technologies, existing implementations. Use context to inform research question.
Step 1: Research Question
- Create
.ada/data/research/{topic}/ - Create
research-question.mdusing template - Create
references.jsonwith intent
Step 2: Discovery (Target: 25+ Sources)
Academic (OpenAlex, Paper-search):
- Foundational:
get_top_cited_works(min_citations: 50+) - Recent SOTA:
search_works(from_year: 2020+) - Citation networks:
get_citation_network
Non-Academic (Tavily via search skill):
- Blogs, docs, case studies in parallel
- Target: 5-10 relevant sources
Conflict-Seeking:
- "{approach A} vs {approach B}"
- "{approach} limitations"
- "alternative to {approach}"
Step 3: Evidence Cards (5+ Required)
- Read 1-2 papers/sources
- Create/update evidence card
- Update
references.json - SAVE files
- REPEAT until 5+ cards
Grouping: Same approach → same card. Different approach → new card.
Critical Evaluation
After 5+ cards, before report:
- Assess strengths/weaknesses
- Evaluate for codebase context
- Compare tradeoffs systematically
- Identify best fit
Step 4: Research Report
- Re-read all evidence cards:
ada::research:show - Re-read
research-question.md - Create
research-report.mdusing template - Include "Answer to Original Question" section
Tools Quick Reference
| Tool | Purpose | When |
|---|---|---|
OpenAlex get_top_cited_works |
Foundational papers | Discovery |
OpenAlex search_works |
Recent SOTA | Discovery |
OpenAlex get_citation_network |
Related work | Deep dive |
Paper-search search_arxiv |
Preprints | Recent work |
PDF read_pdf |
Extract content | Reading papers |
| Tavily (search skill) | Non-academic | Parallel discovery |
zai-zread search_doc |
Semantic issues/PRs/docs | Real-world implementations |
webfetch |
Direct URL reads | Lightweight docs/files |
look_at |
Interpret diagrams/images | PDFs/screenshots |
Research Management Commands
ada::research:status # Full status + next action
ada::research:status --next # Just next action
ada::research:status --checkpoint # Verify state
ada::research:status --ref <name> # Load reference file
ada::research:list # List all sessions
ada::research:show <session> # Show evidence cards
ada::research:cleanup --all # Clear PDFs
Load References On-Demand:
ada::research:status --ref workflow # Workflow guide
ada::research:status --ref evidence-cards # Card guide
ada::research:status --ref template-card # Card template
ada::research:status --ref weighting # Weighting framework
Key Tips (Reminders)
Source Weighting
| Type | Weight | Examples |
|---|---|---|
| Academic (50+ citations) | High | Peer-reviewed papers |
| Academic (10-50 citations) | Medium | Recent SOTA |
| Real-world case studies | High | Company post-mortems |
| Blogs, tutorials | Medium-Low | Expert content |
Evidence Card Essentials
- Key claims with page number citations
- Assumptions and conditions
- Tradeoffs and limitations
- Related/conflicting approaches
- Implementation resources
Common Mistakes
- ❌ Reading 3+ papers before writing → Write after 1-2
- ❌ Not seeking conflicts → Explicitly search opposing views
- ❌ Skipping codebase context → Always start with Step 0
- ❌ Stopping at 3 cards → Must reach 5+ for broad coverage
Directory Structure
.ada/
├── data/research/{topic}/
│ ├── research-question.md
│ ├── evidence-card-*.md
│ ├── research-report.md
│ └── references.json
└── temp/research/downloads/ # Temporary PDFs
References
Templates:
references/templates/template-research-question.mdreferences/templates/template-evidence-card.mdreferences/templates/template-research-report.mdreferences/templates/template-references.json
Guides:
references/guides/guide-workflow.md- Detailed workflowsreferences/guides/guide-evidence-cards.md- Card creationreferences/guides/guide-weighting.md- Source weightingreferences/guides/guide-critical-evaluation.md- Evaluation frameworkreferences/guides/guide-reports.md- Report generationreferences/guides/guide-adaptive-strategies.md- Handling edge cases
Examples:
references/examples/example-evidence-card.mdreferences/examples/example-research-report.mdreferences/examples/example-workflows.md
Reference:
references/reference/reference-tools.md- Complete MCP documentation
Integration
- With search skill: Use Tavily in parallel for non-academic sources
- With docs-write: Use evidence cards for documentation decisions
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
resolve-pr-comments
Resolve bot review comments (CodeRabbit, Copilot, Gemini) on GitHub PRs using subagents. Use when: (1) User asks to 'review PR comments' or 'resolve PR comments', (2) User says 'work through PR N comments' or 'handle bot comments', (3) Need to triage CodeRabbit/Copilot/Gemini review comments, (4) Processing PR feedback at scale, (5) Want to see what's already fixed vs still pending. NOT for: creating PRs, reviewing code yourself, writing new reviews. Triggers: review PR comments, resolve PR comments, work through PR comments, handle bot comments, process CodeRabbit comments, triage PR feedback, fix PR review issues, resolve bot comments, pr comment resolver.
tdd
Strict Red-Green-Refactor workflow for robust, self-documenting code. Discovers project test setup via codebase exploration before assuming frameworks. Use when: (1) Implementing new features with test-first approach, (2) Fixing bugs with reproduction tests, (3) Refactoring existing code with test safety net, (4) Adding tests to legacy code, (5) Ensuring code quality before committing, (6) When tests exist but workflow unclear, or (7) When establishing testing practices in a new project. Triggers: test, tdd, red-green-refactor, failing test, test first, test-driven, write tests, add tests, run tests.
use-graphite
Manage stacked PRs with Graphite CLI (gt) instead of git push/gh pr create. Auto-detects Graphite repos and blocks conflicting commands with helpful alternatives. Use when: (1) About to run git push or gh pr create in a Graphite repo, (2) Creating a new branch for a feature, (3) Submitting code for review, (4) Large changes that should be split into reviewable chunks, (5) Hook blocks your git command and suggests gt equivalent. NOT for: repos not initialized with Graphite, git add/commit/status/log. Triggers: git push blocked, gh pr create blocked, create branch, submit PR, stacked PRs, split large PR, gt create, gt submit, graphite workflow.
git-commit
Write clear git commits with Conventional Commits format. Detects project conventions from history and config. Guides commit granularity. Use when: (1) Completing working code, (2) Code builds and tests pass, (3) Ready to save, (4) Before pushing, (5) After review feedback. Triggers: automatically when finishing commitable work that builds and passes tests.
code-review
Review code changes using CodeRabbit CLI - supports uncommitted files (task mode) or all PR files vs main branch (pr mode). Catches bugs, security issues, and code quality problems before committing or when reviewing pull requests. Use when: (1) Reviewing uncommitted changes before committing (task mode), (2) Reviewing all changed files in a PR against main branch (pr mode), (3) Working on subtasks and want to check progress, (4) Need feedback on work-in-progress code, (5) Preparing PR for merge, (6) When CodeRabbit review is needed, (7) For bug detection and security scanning, or (8) For automated code quality assessment. Triggers: review code, check code quality, review changes, code review, review PR, check for bugs, security scan, review uncommitted, finalize code, pre-commit review.
image-generation
Generate, edit, and upscale AI images. Use when creating visual assets for apps, websites, or documentation. FREE Cloudflare tier for iterate generation (~96/day), Fal.ai for paid tiers. Four quality tiers (iterate/default/premium/max). Supports text specialists, multi-ref editing, SVG, background removal. Triggers: generate image, create image, edit image, upscale, logo, picture of, remove background.
Didn't find tool you were looking for?