Notion research documentation skill
Research across Notion and synthesize into structured documentation.
by davila7·MIT license·★ 32,299 Stars on the repo·GitHub ↗
Use now
npx degit davila7/claude-code-templates/cli-tool/components/skills/productivity/notion-research-documentation#main ~/.claude/skills/notion-research-documentationChecked ·commit main
Files of Notion research documentation
SKILL.md
Show the full text60 lines
Research & Documentation
Pull relevant Notion pages, synthesize findings, and publish clear briefs or reports (with citations and links to sources).
Quick start
- Find sources with
Notion:notion-searchusing targeted queries; confirm scope with the user. - Fetch pages via
Notion:notion-fetch; note key sections and capture citations (reference/citations.md). - Choose output format (brief, summary, comparison, comprehensive report) using
reference/format-selection-guide.md. - Draft in Notion with
Notion:notion-create-pagesusing the matching template (quick, summary, comparison, comprehensive). - Link sources and add a references/citations section; update as new info arrives with
Notion:notion-update-page.
Workflow
0) If any MCP call fails because Notion MCP is not connected, pause and set it up:
- Add the Notion MCP:
codex mcp add notion --url https://mcp.notion.com/mcp
- Enable remote MCP client:
- Set
[features].rmcp_client = trueinconfig.tomlor runcodex --enable rmcp_client
- Set
- Log in with OAuth:
codex mcp login notion
After successful login, the user will have to restart codex. You should finish your answer and tell them so when they try again they can continue with Step 1.
1) Gather sources
- Search first (
Notion:notion-search); refine queries, and ask the user to confirm if multiple results appear. - Fetch relevant pages (
Notion: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.mdfor 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-pagewhen 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).
| 1 | |
| 2 | name notion-research-documentation |
| 3 | 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. |
| 4 | metadata |
| 5 | short-description Research Notion content and produce briefs/reports |
| 6 | |
| 7 | |
| 8 | # Research & Documentation |
| 9 | |
| 10 | Pull relevant Notion pages, synthesize findings, and publish clear briefs or reports (with citations and links to sources). |
| 11 | |
| 12 | ## Quick start |
| 13 | 1) Find sources with `Notion:notion-search` using targeted queries; confirm scope with the user. |
| 14 | 2) Fetch pages via `Notion:notion-fetch`; note key sections and capture citations (`reference/citations.md`). |
| 15 | 3) Choose output format (brief, summary, comparison, comprehensive report) using `reference/format-selection-guide.md`. |
| 16 | 4) Draft in Notion with `Notion:notion-create-pages` using the matching template (quick, summary, comparison, comprehensive). |
| 17 | 5) Link sources and add a references/citations section; update as new info arrives with `Notion:notion-update-page`. |
| 18 | |
| 19 | ## Workflow |
| 20 | ### 0) If any MCP call fails because Notion MCP is not connected, pause and set it up: |
| 21 | Add the Notion MCP: |
| 22 | `codex mcp add notion --url https://mcp.notion.com/mcp` |
| 23 | Enable remote MCP client: |
| 24 | Set `[features].rmcp_client = true` in `config.toml` **or** run `codex --enable rmcp_client` |
| 25 | Log in with OAuth: |
| 26 | `codex mcp login notion` |
| 27 | |
| 28 | After successful login, the user will have to restart codex. You should finish your answer and tell them so when they try again they can continue with Step 1. |
| 29 | |
| 30 | ### 1) Gather sources |
| 31 | Search first (`Notion:notion-search`); refine queries, and ask the user to confirm if multiple results appear. |
| 32 | Fetch relevant pages (`Notion:notion-fetch`), skim for facts, metrics, claims, constraints, and dates. |
| 33 | Track each source URL/ID for later citation; prefer direct quotes for critical facts. |
| 34 | |
| 35 | ### 2) Select the format |
| 36 | Quick readout → quick brief. |
| 37 | Single-topic dive → research summary. |
| 38 | Option tradeoffs → comparison. |
| 39 | Deep dive / exec-ready → comprehensive report. |
| 40 | See `reference/format-selection-guide.md` for when to pick each. |
| 41 | |
| 42 | ### 3) Synthesize |
| 43 | Outline before writing; group findings by themes/questions. |
| 44 | Note evidence with source IDs; flag gaps or contradictions. |
| 45 | Keep user goal in view (decision, summary, plan, recommendation). |
| 46 | |
| 47 | ### 4) Create the doc |
| 48 | Pick the matching template in `reference/` (brief, summary, comparison, comprehensive) and adapt it. |
| 49 | Create the page with `Notion:notion-create-pages`; include title, summary, key findings, supporting evidence, and recommendations/next steps when relevant. |
| 50 | Add citations inline and a references section; link back to source pages. |
| 51 | |
| 52 | ### 5) Finalize & handoff |
| 53 | Add highlights, risks, and open questions. |
| 54 | If the user needs follow-ups, create tasks or a checklist in the page; link any task database entries if applicable. |
| 55 | Share a short changelog or status using `Notion:notion-update-page` when updating. |
| 56 | |
| 57 | ## References and examples |
| 58 | `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`). |
| 59 | `examples/` — end-to-end walkthroughs (e.g., `competitor-analysis.md`, `technical-investigation.md`, `market-research.md`, `trip-planning.md`). |
| 60 |
Discussion
Alternatives
Github repository analysis and enhancementAct as a GitHub Repository Analyst to perform in-depth analysis and suggest improvements for repository structure, documentation, code quality, and community engagement.Multi-Audience Application Discovery & Documentation PromptA prompt designed to analyze a codebase and generate comprehensive Markdown documentation tailored for executive, technical, product, and business audiences. It guides an AI to extract high-level system purpose, architecture, key components, workflows, product features, business domains, and limitations, producing an onboarding and discovery document suitable for both technical and non-technical stakeholders.
Documentation and adrsRecords decisions and documentation. Use when you need to document an architecture decision (ADR) or the reasoning behind a design choice, when changing public APIs, shipping features, or when you need to record context that future engineers and agents will need to understand the codebase.
Treatment-Plan DocumentationFormat and structurally validate local treatment-plan documentation after clinical decisions have already been supplied and verified by authorized licensed professionals. Use for source traceability, clinician-authored intervention records, goals and checkpoints, shared-decision records, reconciliation handoffs, and release gates—not for clinical decision-making.
Browse more free Claude skills or everything in Development.