AutoGineer
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
Download ZIP

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://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/advanced-search.md

Advanced Search Techniques

Search Filtering

By Date Range

Use created_date_range to find recent content:

filters: {
  created_date_range: {
    start_date: "2024-01-01",
    end_date: "2025-01-01"
  }
}

When to use:

  • Finding recent updates on a topic

  • Focusing on current information

  • Excluding outdated content

By Creator

Use created_by_user_ids to find content from specific people:

filters: {
  created_by_user_ids: ["user-id-1", "user-id-2"]
}

When to use:

  • Research from subject matter experts

  • Team-specific information

  • Attribution tracking

Combined Filters

Stack filters for precision:

filters: {
  created_date_range: {
    start_date: "2024-10-01"
  },
  created_by_user_ids: ["expert-user-id"]
}

Scoped Searches

Teamspace Scoping

Restrict search to specific teamspace:

teamspace_id: "teamspace-uuid"

When to use:

  • Project-specific research

  • Department-focused information

  • Reducing noise from irrelevant results

Page Scoping

Search within a specific page and its subpages:

page_url: "https://notion.so/workspace/Page-Title-uuid"

When to use:

  • Research within a project hierarchy

  • Documentation updates

  • Focused investigation

Database Scoping

Search within a database's content:

data_source_url: "collection://data-source-uuid"

When to use:

  • Task/project database research

  • Structured data investigation

  • Finding specific entries

Search Strategies

Broad to Narrow

  1. Start with general search term

  2. Review results for relevant teamspaces/pages

  3. Re-search with scope filters

  4. Fetch detailed content from top results

Example:

Search 1: query="API integration" → 50 results across workspace
Search 2: query="API integration", teamspace_id="engineering" → 12 results
Fetch: Top 3-5 most relevant pages
Multi-Query Approach

Run parallel searches with related terms:

Query 1: "API integration"
Query 2: "API authentication"
Query 3: "API documentation"

Combine results to build comprehensive picture.

Temporal Research

Search across time periods to track evolution:

Search 1: created_date_range 2023 → Historical context
Search 2: created_date_range 2024 → Recent developments
Search 3: created_date_range 2025 → Current state

Result Processing

Identifying Relevant Results

Look for:

  • High semantic match: Result summary closely matches query intent

  • Recent updates: Last-edited date is recent

  • Authoritative sources: Created by known experts or in official locations

  • Comprehensive content: Result summary suggests detailed information

Prioritizing Fetches

Fetch pages in order of relevance:

  1. Primary sources: Direct documentation, official pages

  2. Recent updates: Newly edited content

  3. Related context: Supporting information

  4. Historical reference: Background and context

Don't fetch everything - be selective based on research needs.

Handling Too Many Results

If search returns 20+ results:

  1. Add filters: Narrow by date, creator, or teamspace

  2. Refine query: Use more specific terms

  3. Use page scoping: Search within relevant parent page

  4. Sample strategically: Fetch diverse results (recent, popular, authoritative)

Handling Too Few Results

If search returns < 3 results:

  1. Broaden query: Use more general terms

  2. Remove filters: Search full workspace

  3. Try synonyms: Alternative terminology

  4. Search in related areas: Adjacent teamspaces or pages

Search Quality

Effective Search Queries

Good queries (specific, semantic):

  • "Q4 product roadmap"

  • "authentication implementation guide"

  • "customer feedback themes"

Weak queries (too vague):

  • "roadmap"

  • "guide"

  • "feedback"

Over-specific queries (too narrow):

  • "Q4 2024 product roadmap for mobile app version 3.2 feature X"

User Context

Always use available user context:

  • Query should match their terminology

  • Scope to their relevant teamspaces

  • Consider their role/department

  • Reference their recent pages

Connected Sources

Notion Integrations

Search extends beyond Notion pages to:

  • Slack messages (if connected)

  • Google Drive documents (if connected)

  • GitHub issues/PRs (if connected)

  • Jira tickets (if connected)

Be aware results may come from these sources.

Source Attribution

When citing results from connected sources:

  • Note the source type in documentation

  • Use appropriate mention format

  • Verify user has access to the source system

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