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 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).

openai의 다른 스킬

release
openai
커밋된 버전을 올리고, 이를 반영하고, 병합된 커밋에 태그를 단 후, Burrito 릴리스 워크플로우를 검증하여 Symphony 릴리스를 진행합니다. 다음과 같이 요청받았을 때 사용합니다…
signing-entitlements
openai
macOS 앱의 서명, 자격, 강화된 런타임 및 Gatekeeper 문제를 검사합니다. 코드 서명 실패, 누락된 자격 등을 진단하라는 요청을 받을 때 사용하세요.
building-ai-agent-on-cloudflare
openai
Cloudflare에서 Agents SDK를 사용하여 상태 관리, 실시간 WebSockets, 예약 작업, 도구 통합, 채팅을 통해 AI 에이전트를 구축합니다…
epigraphdb-skill
openai
온톨로지, 문헌, MR, 유전자-약물 및 지원 경로 증거에 대한 간결한 EpiGraphDB API 요청을 제출합니다. 사용자가 간결한 EpiGraphDB 요약을 원할 때 사용하세요.
runtime-behavior-probe
openai
런타임 동작 조사를 계획하고 실행하며, 임시 프로브 스크립트, 검증 매트릭스, 상태 제어, 결과 우선 보고서를 사용합니다. 다음 경우에만 사용하세요…
deep-security-scan
openai
사용자가 심층적이고, 철저하며, 다중 패스 또는 변동성을 줄이는 저장소 전체 또는 범위가 지정된 경로의 Codex Security 스캔을 요청할 때 사용합니다. 반복적으로 독립적인…
define-security-policy
openai
저장소 또는 구성 요소에 대한 SECURITY.md 지침을 정의, 검토 또는 업데이트합니다. 사용자가 Codex Security가 검토해야 할 대상과 범위를 벗어나는 항목을 명확히 하려 할 때 사용합니다…
validation
openai
Codex가 보안 스캔의 검증 단계에 이미 있거나 사용자가 하나 이상의 후보 보안 결과를 판별하도록 명시적으로 요청할 때 사용합니다…