notion-research-documentation

作者: openai

在Notion中进行研究并整合为结构化文档;当需要从多个Notion来源收集信息以生成简报、对比或…时使用。

npx skills add https://github.com/openai/plugins --skill notion-research-documentation

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 Codex prompts for it.
  3. Restart Codex or the current 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).

来自 openai 的更多技能

user-context
openai
加载或管理数据分析插件的持久化源路由偏好、引导逻辑、设置进度及语义层注册表。
official
notion-research-documentation
openai
研究Notion内容,并将其综合成带有引用的结构化简报、报告或对比。通过定向查询搜索并获取Notion页面,然后按主题组织发现,附带内联来源引用和参考文献部分。根据范围和用户目标,从四种输出格式(快速简报、研究摘要、对比、综合报告)中选择。使用内置模板创建和更新Notion页面;直接链接来源,并在新信息到达时跟踪变更...
official
rcsb-pdb-skill
openai
提交紧凑的RCSB PDB请求以获取核心元数据、Search API查询和FASTA下载。当用户需要简洁的RCSB摘要时使用;保存原始JSON或…
official
pdf
openai
PDF的读取、创建与验证,支持可视化渲染与程序化生成。使用Poppler(pdftoppm)将PDF页面渲染为PNG,以便在交付前直观检查布局、间距与排版;通过reportlab程序化生成PDF,确保格式可靠;利用pdfplumber或pypdf提取文本与元数据。执行质量标准:无文本裁剪、元素重叠、表格损坏或渲染伪影;仅使用ASCII连字符,引用内容需可读。使用...
official
test-coverage-improver
openai
改进OpenAI Agents JS mon
official
playwright
openai
基于终端驱动的浏览器自动化,支持元素快照与交互式UI工作流。通过playwright-cli包装脚本运行(需npx),支持无头模式与有头模式进行可视化调试。核心工作流:打开页面、获取快照以稳定元素引用、使用引用进行交互、在导航或DOM变更后重新快照。包含表单填写、点击、输入、多标签页管理、截图/PDF捕获及用于流程调试的追踪记录。元素引用(如e3、e15)...
official
ukb-topmed-phewas-skill
openai
通过接受rsID、GRCh37或GRCh38输入并解析为所需的GRCh38查询,获取单个变体的紧凑型UKB-TOPMed PheWAS摘要。当需要…时使用。
official
code-review-context
openai
模型可见上下文
official