notion-research-documentation · openai — Codex skill: overview and setup
Gathers information across Notion pages, extracts facts, and drafts structured briefs or comparative reports with source citations directly in your workspace.
npx skills add openai/plugins --skill notion-research-documentation -a codexWhat notion-research-documentation does
The skill coordinates research inside a Notion workspace. It finds pages via Notion:search and reads them with Notion:fetch. The agent pulls out key metrics and direct quotes, grouping findings into structured themes.
Results go back into Notion. Using Notion:notion-create-pages, the skill formats output as concise briefs, option comparisons, or detailed reports. When changes occur, Notion:notion-update-page updates existing entries.
Search queries often surface connected external links that break Notion:fetch. The fetch tool accepts only native Notion page and database identifiers. Missing workspace tools also trigger an immediate fallback instead of repeated retries.
What it helps with
- synthesize scattered Notion notes into an executive brief
- build structured option comparisons with citations
- draft project reports directly in a Notion workspace
- update existing documentation without manual copy-pasting
Example prompts for the agent
- Search Notion for our launch retro notes and draft a quick summary
- Compare database migration options from our docs and publish the comparison page
- Review the customer interview notes in Notion and compile a cited report
How to install notion-research-documentation
1Skills CLI (Vercel)
npx skills add openai/plugins --skill notion-research-documentation -a codex2Manually: put the files in place
.agents/skills/notion-research-documentation/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add openai/plugins --skill notion-research-documentation -a claude-code2Manually: put the files in place
~/.claude/skills/notion-research-documentation/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/notion-research-documentation/
Manually: put the files in place
.cursor/skills/notion-research-documentation/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install openai/plugins notion-research-documentation2Manually: put the files in place
.github/skills/notion-research-documentation/SKILL.mdPlatform CLI
gemini skills install https://github.com/openai/plugins --path plugins/notion/skills/notion-research-documentationManually: put the files in place
.devin/skills/notion-research-documentation/SKILL.mdThe legacy .windsurf/skills/ path still works
Claude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: Codex skills: how to install, where they live, how to call them
Questions about notion-research-documentation
What does notion-research-documentation do?
It scans your Notion workspace for relevant documents, extracts critical points, and writes structured reports with back-links and citations.
How do I install notion-research-documentation in Codex?
Run npx skills add openai/plugins --skill notion-research-documentation. You can also target Codex explicitly by running npx skills add openai/plugins --skill notion-research-documentation -a codex.
Why does Notion:fetch fail on certain search results?
Notion search results sometimes include links to external connected integrations. The Notion:fetch tool strictly requires Notion page or database IDs and cannot parse outside URLs.
Source text
SKILL.md · MIT
---
name: notion-research-documentation
description: Research across Notion and synthesize into structured documentation; use when gathering info from multiple Notion sources to produce briefs, comparisons, or reports with citations.
metadata:
short-description: Research Notion content and produce briefs/reports
---
# 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`).
© Notion · MIT · openai/plugins
Similar skills
All skills for Writing and docs →notion-research-documentation by other authors comes first.