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

examples/trip-planning.md

Example: Group Trip Research & Planning

User Request: "Research and plan our friends' trip to Japan in March - we're 6 people looking for 10 days"

Workflow

1. Search Existing Notes
Notion:search
query: "Japan travel"
query_type: "internal"
filters: {}

Found: Japan Travel Guide (from friend), Tokyo Restaurants, Kyoto Temple Guide

2. Fetch & Extract Tips
Repeat for each Notion page result:
Notion:fetch
id: "japan-travel-guide-page-id"

Key info from previous travelers:

  • Best time: March-April (cherry blossoms)

  • Must-see: Tokyo, Kyoto, Osaka

  • Budget: $200-300/day (mid-range)

  • Book accommodations 3 months ahead

  • Get JR Pass before arrival

  • Top restaurants: Sushi Dai, Ichiran Ramen, Tsunahachi Tempura

3. Research & Synthesize

Combined previous traveler insights with:

  • Flight options and prices

  • Accommodation types (hotels/ryokans/Airbnb)

  • Transportation (JR Pass essential)

  • 10-day itinerary structure

  • Budget breakdown

4. Create Comprehensive Plan
Notion:notion-create-pages
parent: { page_id: "travel-plans-parent-id" }
pages: [{
  properties: {
    title: "Japan Trip 2026 - March 15-25 (10 Days)"
  },
  content: "[Full trip plan with itinerary, budget, tips...]"
}]

Output Sample

# Japan Trip 2026 - March 15-25 (10 Days)

## Trip Overview
**Dates**: March 15-25, 2026 (Cherry Blossom Season 🌸)
**Group**: 6 people | **Budget**: $3,000-4,000/person

## Itinerary Summary

**Days 1-3: Tokyo**
- Arrive, explore Shibuya, Harajuku, Shinjuku
- Visit Tsukiji Market, Imperial Palace, Sensoji Temple
- Experience Tokyo nightlife, teamLab Borderless

**Days 4-5: Hakone**
- Day trip from Tokyo
- Hot springs, Mt. Fuji views, Lake Ashi cruise

**Days 6-8: Kyoto**
- Bullet train from Tokyo
- Fushimi Inari, Kinkaku-ji, Arashiyama Bamboo Grove
- Geisha district (Gion), traditional tea ceremony

**Days 9-10: Osaka + Depart**
- Osaka Castle, Dotonbori food district
- Nara day trip (deer park, Todai-ji Temple)
- Return flight from Osaka (KIX)

## Budget Breakdown (per person)
- **Flights**: $900-1,200 (round-trip)
- **Accommodations**: $700-1,000 (9 nights)
- **JR Pass**: $280 (7-day pass)
- **Food**: $500-700 ($50-70/day)
- **Activities**: $300-400
- **Local transport**: $100
**Total**: $2,780-3,680

## Key Bookings
- **Flights**: Book 3-4 months ahead
- **Hotels**: Book now (cherry blossom season)
  - Tokyo: Shinjuku area (2 nights) + Asakusa (1 night)
  - Kyoto: Gion area (3 nights)
  - Osaka: Namba area (2 nights)
- **JR Pass**: Order 2-3 weeks before travel
- **Restaurants**: Reserve 1 week ahead (Sushi Dai, high-end spots)

## Essential Tips
Source: <mention-page url="...">Japan Travel Guide</mention-page>
- Get pocket WiFi or eSIM on arrival
- Download: Google Translate, Hyperdia (train routes), Tabelog (restaurants)
- Cash-heavy country - withdraw at 7-Eleven ATMs
- Shoes off in temples, ryokans, some restaurants
- Trains extremely punctual - don't be late
- Learn basic phrases: arigatou, sumimasen, itadakimasu

## Packing List
- Comfortable walking shoes (10k+ steps/day)
- Light jacket (March 55-65°F)
- Backpack for day trips
- Cash pouch
- Portable charger

## Next Steps
- [ ] Book flights (target: <$1,100/person)
- [ ] Order JR Passes
- [ ] Book hotels (Tokyo → Kyoto → Osaka)
- [ ] Create shared expense tracker
- [ ] Schedule group planning call

## Sources
- <mention-page url="...">Japan Travel Guide</mention-page> (Sarah's 2024 trip)
- <mention-page url="...">Tokyo Restaurant Recommendations</mention-page>
- <mention-page url="...">Kyoto Temple Guide</mention-page>

Key Takeaways

  • Leveraged previous traveler notes from Notion

  • Combined personal insights with research

  • Created actionable itinerary with budget breakdown

  • Included practical tips from experienced travelers

  • Set clear next steps for group coordination

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