Generated banner for Notion Research Documentation
Generated logo for Notion Research Documentation

Notion Research Documentation

OpenAIOfficialCreated by Notion Labs, IncDistributed by OpenAI

  • Skill
  • Content generator
  • Automation and integrations
  • MIT
  • No issues found

From the author

Research across Notion and synthesize into structured documentation; use when gathering info from multiple Notion sources to produce briefs, comparisons, or reports with citations.
— the description by Notion Labs, Inc

AutoGineer summary

Written by AutoGineer from the skill’s own files, not by the author

This skill provides a systematic approach to gathering information from multiple Notion sources and transforming it into professional documentation. It guides the user through searching, fetching, synthesizing, and creating structured outputs like briefs, summaries, comparisons, or comprehensive reports, ensuring all content is properly cited and linked back to the original Notion pages.

What it does

  • Searches Notion workspaces to identify relevant information sources.
  • Fetches and extracts key facts, metrics, and claims from Notion pages.
  • Provides templates for various output formats including briefs and reports.
  • Creates new Notion pages containing synthesized findings and recommendations.
  • Maintains traceability by adding citations and links to original source material.
  • Updates existing Notion reports with new information or status changes.

When to use it

  • When you need to consolidate information scattered across multiple Notion pages.
  • When preparing executive-ready reports or summaries based on internal knowledge.
  • When performing comparative analysis of options documented in Notion.
  • When you need to maintain a living document that requires periodic updates from source data.

Advantages

  • Ensures consistent documentation quality through standardized templates.
  • Reduces manual effort in cross-referencing and citing internal information.
  • Maintains clear provenance for all claims by linking directly to source pages.
  • Supports iterative updates to keep reports current as source data changes.

Usage examples

“Research our last three project retrospectives in Notion and create a summary report of common bottlenecks.”
The agent searches for the relevant retrospective pages, extracts recurring themes, and generates a structured summary report in Notion with citations to the original documents.
“Compare the two vendor evaluation pages in our workspace and draft a comparison brief.”
The agent fetches the content from both vendor pages, identifies key trade-offs, and creates a comparison document highlighting the pros and cons for decision-making.

Install

  1. Download the skill as a ZIP:

    https://mp-staging.autogineer.com/agent-skills/openai/notion-research-documentation/download
  2. Unzip it into the cross-client skills folder of your project:

    mkdir -p .agents/skills && unzip notion-research-documentation.zip -d .agents/skills

Documentation by Notion Labs, Inc

Research & Documentation

Pull relevant Notion pages, synthesize findings, and publish clear briefs or reports (with citations and links to sources).

Quick start

  1. Find sources with Notion:search using targeted queries; confirm scope with the user.

  2. Fetch pages via Notion:fetch; note key sections and capture citations (reference/citations.md).

  3. Choose output format (brief, summary, comparison, comprehensive report) using reference/format-selection-guide.md.

  4. Draft in Notion with Notion:notion-create-pages using the matching template (quick, summary, comparison, comprehensive).

  5. Link sources and add a references/citations section; update as new info arrives with Notion:notion-update-page.

Tool-call guardrails

  • Notion tool availability can vary by workspace. If a Notion MCP call returns Tool <name> not found, treat that tool as unavailable for the rest of the current task. Do not retry it with different arguments or call it again later; use Notion:search and Notion:fetch where sufficient.

  • Use one literal search query per Notion:search call and include filters: {} when no narrower filter is needed.

  • Only fetch Notion page, database, or data-source URLs/IDs. Search results can include external connected-source URLs, which are not valid Notion:fetch inputs.

  • Create output pages with an explicit parent and a pages array.

  • When updating an existing report, fetch it first and use Notion:notion-update-page with update_content, properties: {}, and search-and-replace pairs. For property-only updates, use update_properties with content_updates: []. The current deployed schema expects both top-level fields even when one is unused. Do not invent insertion-only commands.

Workflow

0) If Notion tools are unavailable, pause and ask the user to connect the Notion app:
  1. Enable the bundled Notion app for this plugin or session.

  2. Complete the Notion auth flow if prompted.

  3. Start a new session if the tools still do not appear.

After the app is connected, finish your answer and tell the user to retry so they can continue with Step 1.

1) Gather sources
  • Search first (Notion:search); refine queries, and ask the user to confirm if multiple results appear.

  • Fetch relevant pages (Notion:fetch), skim for facts, metrics, claims, constraints, and dates.

  • Track each source URL/ID for later citation; prefer direct quotes for critical facts.

2) Select the format
  • Quick readout → quick brief.

  • Single-topic dive → research summary.

  • Option tradeoffs → comparison.

  • Deep dive / exec-ready → comprehensive report.

  • See reference/format-selection-guide.md for when to pick each.

3) Synthesize
  • Outline before writing; group findings by themes/questions.

  • Note evidence with source IDs; flag gaps or contradictions.

  • Keep user goal in view (decision, summary, plan, recommendation).

4) Create the doc
  • Pick the matching template in reference/ (brief, summary, comparison, comprehensive) and adapt it.

  • Create the page with Notion:notion-create-pages; include title, summary, key findings, supporting evidence, and recommendations/next steps when relevant.

  • Add citations inline and a references section; link back to source pages.

5) Finalize & handoff
  • Add highlights, risks, and open questions.

  • If the user needs follow-ups, create tasks or a checklist in the page; link any task database entries if applicable.

  • Share a short changelog or status using Notion:notion-update-page when updating.

References and examples

  • reference/ — search tactics, format selection, templates, and citation rules (e.g., advanced-search.md, format-selection-guide.md, research-summary-template.md, comparison-template.md, citations.md).

  • examples/ — end-to-end walkthroughs (e.g., competitor-analysis.md, technical-investigation.md, market-research.md, trip-planning.md).

Files

reference/citations.md

Citation Styles

Basic Page Citation

Always cite sources using Notion page mentions:

<mention-page url="https://notion.so/workspace/Page-Title-uuid">Page Title</mention-page>

The URL must be provided. The title is optional but improves readability:

<mention-page url="https://notion.so/workspace/Page-Title-uuid"/>

Inline Citations

Cite immediately after referenced information:

The Q4 revenue increased by 23% quarter-over-quarter (<mention-page url="...">Q4 Financial Report</mention-page>).

Multiple Sources

When information comes from multiple sources:

Customer satisfaction has improved across all metrics (<mention-page url="...">Q3 Survey Results</mention-page>, <mention-page url="...">Support Analysis</mention-page>).

Section-Level Citations

For longer sections derived from one source:

### Engineering Priorities

According to the <mention-page url="...">Engineering Roadmap 2025</mention-page>:

- Focus on API scalability
- Improve developer experience
- Migrate to microservices architecture

Sources Section

Always include a "Sources" section at document end:

## Sources

- <mention-page url="...">Strategic Plan 2025</mention-page>
- <mention-page url="...">Market Analysis Report</mention-page>
- <mention-page url="...">Competitor Research: Q3</mention-page>
- <mention-page url="...">Customer Interview Notes</mention-page>

Group by category for long lists:

## Sources

### Primary Sources
- <mention-page url="...">Official Roadmap</mention-page>
- <mention-page url="...">Strategy Document</mention-page>

### Supporting Research
- <mention-page url="...">Market Trends</mention-page>
- <mention-page url="...">Customer Feedback</mention-page>

### Background Context
- <mention-page url="...">Historical Analysis</mention-page>

Quoting Content

When quoting directly from source:

The product team noted: "We need to prioritize mobile experience improvements" (<mention-page url="...">Product Meeting Notes</mention-page>).

For block quotes:

> We need to prioritize mobile experience improvements to meet our Q4 goals. This includes performance optimization and UI refresh.
>
> — <mention-page url="...">Product Meeting Notes - Oct 2025</mention-page>

Data Citations

When presenting data, cite the source:

| Metric | Q3 | Q4 | Change |
|--------|----|----|--------|
| Revenue | $2.3M | $2.8M | +21.7% |
| Users | 12.4K | 15.1K | +21.8% |

Source: <mention-page url="...">Financial Dashboard</mention-page>

Database Citations

When referencing database content:

Based on analysis of the <mention-database url="...">Projects Database</mention-database>, 67% of projects are on track.

User Citations

When attributing information to specific people:

<mention-user url="...">Sarah Chen</mention-user> noted in <mention-page url="...">Architecture Review</mention-page> that the microservices migration is ahead of schedule.

Citation Frequency

Over-citing (every sentence):

The revenue increased (<mention-page url="...">Report</mention-page>).
Costs decreased (<mention-page url="...">Report</mention-page>).
Margin improved (<mention-page url="...">Report</mention-page>).

Under-citing (no attribution):

The revenue increased, costs decreased, and margin improved.

Right balance (grouped citation):

The revenue increased, costs decreased, and margin improved (<mention-page url="...">Q4 Financial Report</mention-page>).

Outdated Information

Note when source information might be outdated:

The original API design (<mention-page url="...">API Spec v1</mention-page>, last updated January 2024) has been superseded by the new architecture in <mention-page url="...">API Spec v2</mention-page>.

Cross-References

Link to related research documents:

## Related Research

This research builds on previous findings:
- <mention-page url="...">Market Analysis - Q2 2025</mention-page>
- <mention-page url="...">Competitor Landscape Review</mention-page>

For implementation details, see:
- <mention-page url="...">Technical Implementation Guide</mention-page>

Citation Validation

Before finalizing research:

✓ Every key claim has a source citation ✓ All page mentions have valid URLs ✓ Sources section includes all cited pages ✓ Outdated sources are noted as such ✓ Direct quotes are clearly marked ✓ Data sources are attributed

Citation Style Consistency

Choose one citation style and use throughout:

Inline style (lightweight):

Revenue grew 23% (Financial Report). Customer count increased 18% (Metrics Dashboard).

Formal style (full mentions):

Revenue grew 23% (<mention-page url="...">Q4 Financial Report</mention-page>). Customer count increased 18% (<mention-page url="...">Metrics Dashboard</mention-page>).

Recommend formal style for most research documentation as it provides clickable navigation.

Requirements and compatibility

Written for: OpenAI Codex

Works with: Claude Code, Claude apps, OpenAI Codex, GitHub Copilot, Cursor, Gemini CLI, Kiro, OpenCode, Goose, Amp, Roo Code, JetBrains Junie, Factory Droid, Devin (ex-Windsurf), Mistral Vibe, OpenHands, Letta

“Works with” means the tool reads the open Agent Skills format; a skill written for one tool may use features others lack.

Security

No issues found by our static scan· No issues found

A static scan is not a guarantee. Skills are third-party content: review a skill before you let an agent use it.

Attribution and licence

Created by
Notion Labs, Inc
Publisher
OpenAI (Official)
Distributed by
OpenAI
Source
openai/plugins · plugins/notion/skills/notion-research-documentation · commit d420d13
Licence
MIT License (redistribution allowed)
  • ATTRIBUTION.md (written by AutoGineer)
Synced

AutoGineer is not affiliated with or endorsed by Notion Labs, Inc or OpenAI.

Download ZIP

The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download notion-research-documentation.zip