research-documentation
Searches across your Notion workspace, synthesizes findings from multiple pages, and creates comprehensive research documentation saved as new Notion pages. Trigger on "노션 검색", "조사해줘", "리서치 정리". For meeting prep use meeting-intelligence; for saving knowledge use knowledge-capture; for spec breakdown use spec-to-implementation.
Best use case
research-documentation is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Searches across your Notion workspace, synthesizes findings from multiple pages, and creates comprehensive research documentation saved as new Notion pages. Trigger on "노션 검색", "조사해줘", "리서치 정리". For meeting prep use meeting-intelligence; for saving knowledge use knowledge-capture; for spec breakdown use spec-to-implementation.
Teams using research-documentation should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/research-documentation/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How research-documentation Compares
| Feature / Agent | research-documentation | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Searches across your Notion workspace, synthesizes findings from multiple pages, and creates comprehensive research documentation saved as new Notion pages. Trigger on "노션 검색", "조사해줘", "리서치 정리". For meeting prep use meeting-intelligence; for saving knowledge use knowledge-capture; for spec breakdown use spec-to-implementation.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
Related Guides
AI Agents for Startups
Explore AI agent skills for startup validation, product research, growth experiments, documentation, and fast execution with small teams.
Best AI Skills for ChatGPT
Find the best AI skills to adapt into ChatGPT workflows for research, writing, summarization, planning, and repeatable assistant tasks.
Best AI Skills for Claude
Explore the best AI skills for Claude and Claude Code across coding, research, workflow automation, documentation, and agent operations.
SKILL.md Source
# Research & Documentation Enables comprehensive research workflows: search for information across your Notion workspace, fetch and analyze relevant pages, synthesize findings, and create well-structured documentation. ## Quick Start When asked to research and document a topic: 1. **Search for relevant content**: Use `Notion:notion-search` to find pages 2. **Fetch detailed information**: Use `Notion:notion-fetch` to read full page content 3. **Synthesize findings**: Analyze and combine information from multiple sources 4. **Create structured output**: Use `Notion:notion-create-pages` to write documentation ## Research Workflow ### Step 1: Search for relevant information ``` Use Notion:notion-search with the research topic Filter by teamspace if scope is known Review search results to identify most relevant pages ``` ### Step 2: Fetch page content ``` Use Notion:notion-fetch for each relevant page URL Collect content from all relevant sources Note key findings, quotes, and data points ``` ### Step 3: Synthesize findings Analyze the collected information: - Identify key themes and patterns - Connect related concepts across sources - Note gaps or conflicting information - Organize findings logically ### Step 4: Create structured documentation Use the appropriate documentation template (see [reference/format-selection-guide.md](reference/format-selection-guide.md)) to structure output: - Clear title and executive summary - Well-organized sections with headings - Citations linking back to source pages - Actionable conclusions or next steps ## Output Formats Choose the appropriate format based on request: **Research Summary**: See [reference/research-summary-format.md](reference/research-summary-format.md) **Comprehensive Report**: See [reference/comprehensive-report-format.md](reference/comprehensive-report-format.md) **Quick Brief**: See [reference/quick-brief-format.md](reference/quick-brief-format.md) ## Best Practices 1. **Cast a wide net first**: Start with broad searches, then narrow down 2. **Cite sources**: Always link back to source pages using mentions 3. **Verify recency**: Check page last-edited dates for current information 4. **Cross-reference**: Validate findings across multiple sources 5. **Structure clearly**: Use headings, bullets, and formatting for readability ## Page Placement By default, create research documents as standalone pages. If the user specifies: - A parent page → use `page_id` parent - A database → fetch the database first, then use appropriate `data_source_id` - A teamspace → create in that context ## Advanced Features **Search filtering**: See [reference/advanced-search.md](reference/advanced-search.md) **Citation styles**: See [reference/citations.md](reference/citations.md) ## Common Issues **"No results found"**: Try broader search terms or different teamspaces **"Too many results"**: Add filters or search within specific pages **"Can't access page"**: User may lack permissions, ask them to verify access ## Examples See [examples/](examples/) for complete workflow demonstrations: - [examples/market-research.md](examples/market-research.md) - Researching market trends - [examples/technical-investigation.md](examples/technical-investigation.md) - Technical deep-dive - [examples/competitor-analysis.md](examples/competitor-analysis.md) - Multi-source synthesis
Related Skills
writing-documentation
Creates technical documentation including READMEs, API references, user guides, architecture docs, ADRs, and runbooks. Use for requests to create, write, generate, or draft documentation. Trigger phrases include "document this", "write docs", "create readme", "API reference", "user guide", "architecture docs", "ADR", "runbook". For updating existing READMEs, use updating-readme instead.
speckit-documentation-engineer.agent
Expert documentation engineer specializing in technical documentation, API docs, developer guides, and documentation-as-code. Creates maintainable, searchable documentation that developers actually use.
reviewing-documentation
Use when reviewing documentation quality, auditing README or CLAUDE.md files, or standardizing AI instruction files.
quality-documentation-manager
Document control system management for medical device QMS. Covers document numbering, version control, change management, and 21 CFR Part 11 compliance. Use for document control procedures, change control workflow, document numbering, version management, electronic signature compliance, or regulatory documentation review.
documentation-templates
Documentation templates and structure guidelines. README, API docs, code comments, and AI-friendly documentation.
documentation-structure-validator
Validate documentation structure, check for missing sections, verify markdown syntax, ensure consistency with templates. Use when user mentions docs validation, structure check, README review, documentation quality, or wants to verify documentation completeness.
documentation-standards
Clear technical documentation with JSDoc, READMEs, Mermaid diagrams, ISMS policy references, and comprehensive code examples
documentation-specialist
文档专家。专注于技术文档编写、API 文档生成、README 优化和文档维护。提供清晰的文档结构、规范的格式和用户友好的内容。
documentation-research
Enforces documentation research before implementation. Auto-loads when implementing features to ensure current best practices are followed. Researches official docs first.
documentation
Technical writing, API docs, and documentation best practices
Documentation Hygiene
This skill should be used when the user asks to perform "documentation hygiene", "update docs for change", "mark historical docs", "add deprecation headers", "documentation migration", or when making significant changes that affect multiple documentation files (like license migrations, tier changes, or API changes).
documentation-guidelines
Write or update backend feature documentation that follows a repo's DOCUMENTATION_GUIDELINES.md (or equivalent) across any project. Use when asked to create/update module docs, API contracts, or backend documentation that must include architecture, endpoints, payloads, Mermaid diagrams, and seeding instructions.