Publisher: Notion / OpenAI plugin catalog · Editorial profile by AI Tools Ratings · Review method
What task is this skill designed for?
Convert a synthetic launch discussion into a decision record that separates the final decision from rejected proposals.
What input and output should you expect?
Input: A transcript, the approved outcome, intended readers and a chosen Notion destination. Supply existing related pages to avoid a second competing record.
Output: A structured draft with context, decision, alternatives, rationale and follow-up actions; publication belongs in the explicitly selected page or database.
What does it need to run?
A Codex session with the Notion plugin/app connected and access to the selected pages. Database-backed work also needs the actual database schema; the available search, fetch and writing tools depend on the workspace.
Published in the Notion plugin within OpenAI’s Codex plugin examples. Requires a connected Notion app and the tools available to the current workspace.
How should you approach installation?
- Review the pinned skill and the references for the intended task.
- Enable the Notion plugin/app and authorize the relevant workspace; confirm available tools and destination permissions.
- Try the sample prompt with synthetic pages, review the output and approve the destination before allowing shared-page changes.
Installation guide: discovery, dependencies and runtime checks
What files, accounts or data can it access?
Reads accessible Notion pages and supplied material through the connected app. The workflow can create or update pages and database records when authorized. Confirm the destination and sharing scope; use synthetic material for the first draft and keep confidential details out of supplemental web searches.
What does the skill cost?
No separate skill price is stated in the reviewed source. Codex usage, Notion workspace features and any connected research service have their own charges and access limits.
What are its limits and alternatives?
An ambiguous conversation may contain proposals that were never accepted. Ask for confirmation of the final decision rather than turning the latest comment into policy. A useful decision record captures why an option was rejected, not just the winning option.
Use Notion Research Documentation to synthesize several existing pages. Choose Knowledge Capture when the main source is a conversation or a single resolved decision.
What could you ask in a small trial?
Try this with a small sample:
Using these synthetic notes, draft a decision record. Separate accepted decisions, rejected alternatives and unanswered questions. Do not assign an owner or deadline that the notes do not provide. Show the draft before writing it to Notion.
How would you verify the result?
- Each decision is supported by a specific passage.
- Unresolved questions stay unresolved; no invented owners or deadlines.
- Check existing pages before creating a duplicate and verify the destination’s sharing scope.
Use a baseline and record acceptance evidence before treating a successful task as a reliable workflow.
Which source and license were checked?
Read the reviewed SKILL.md at its pinned commit · Complete reviewed folder
Repository and current publisher guidance
Checked:
MIT — identified in the reviewed Notion skill folder. Connected services have their own terms. License evidence
Version details and review scope
Source: openai/plugins/plugins/notion/skills/notion-knowledge-capture
Reviewed commit: 0722921d5542fc593105c27bd52630babd8b8c2a
SKILL.md SHA-256: ade7d8902823500f6af26bdf290f2a88e35b34ce9668739eb8807b773648e333
Source-document review. This profile covers the source workflow, stated dependencies and license evidence. See our editorial methodology for how we distinguish source reviews and hands-on evaluations.