mcpbeat

Notion Research Documentation

prat011/notion-research-documentation

Searches across your Notion workspace, synthesizes findings from multiple pages, and creates comprehensive research documentation saved as new Notion pages. Turns scattered information into structured reports with proper citations and actionable insights.

This is a copy. The original lives at christophacham/notion-research-documentation.

16k tokens
context cost
the whole folder, loaded on every use
21
files
instructions only
0
copies elsewhere
how many repositories repackaged it
1431
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository
npx skills add https://github.com/Prat011/awesome-llm-skills --skill notion-research-documentation

The instruction itself

13 sections, as written by the author

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:

  • Search for relevant content: Use Notion:notion-search to find pages
  • Fetch detailed information: Use Notion:notion-fetch to read full page content
  • Synthesize findings: Analyze and combine information from multiple sources
  • 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) 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

Comprehensive Report: See reference/comprehensive-report-format.md

Quick Brief: See reference/quick-brief-format.md

Best Practices

  • Cast a wide net first: Start with broad searches, then narrow down
  • Cite sources: Always link back to source pages using mentions
  • Verify recency: Check page last-edited dates for current information
  • Cross-reference: Validate findings across multiple sources
  • 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

Citation styles: See 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/ for complete workflow demonstrations:

  • examples/market-research.md - Researching market trends
  • examples/technical-investigation.md - Technical deep-dive
  • examples/competitor-analysis.md - Multi-source synthesis

How to use it

Copy the folder

Take prat011/notion-research-documentation from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.