What does this skill do, and when should you use it?
This skill converts conversations and notes into structured Notion pages for decisions, how-to guides, FAQs, learning notes, and documentation. It first clarifies the content type, audience, freshness, and whether the request is new or an update, then selects a suitable database or template. It can search and fetch existing Notion pages, create or update pages, and maintain links, relations, owners, and statuses. It requires Notion MCP and includes Codex-specific recovery instructions for connection failures.
Clarifies purpose, audience, freshness, and whether the content is new or being updated; selects database guides and templates from reference/; reads existing pages with Notion:notion-search and Notion:notion-fetch; extracts facts, decisions, actions, rationale, steps, links, and edge cases; creates pages with Notion:notion-create-pages or updates them with Notion:notion-update-page; adds links or relations to hubs, related records, and follow-up tasks.
- A team member needs to record an important decision, its alternatives, rationale, and outcome in a decision log.
- A knowledge-base owner wants to turn chat-based procedures, prerequisites, and asset links into a how-to page.
- A support or operations team needs to convert recurring questions into a linked FAQ.
- A team wants to preserve learning notes or conversation findings as searchable, related wiki content.
How do you install this skill?
- Require explicit user confirmation of the target page, database, and content before writing to Notion, especially when conversations may contain personal, confidential, or credential data.
- The documentation lacks detailed recovery and rollback behavior for unavailable remote MCP access, network inaccessibility, or schema mismatches.
- The repository is marked deprecated, while license, versioning, and maintenance responsibility are unclear; confirm the supported source and update channel before deployment.
- Examples contain high-impact commands such as kill -9, sudo, and database configuration changes; captured content should retain context and must not be executed without review.
- Shell / CLI
- Network access
- MCP Server
Notion MCP server
In Codex, run: $skill-installer notion-knowledge-capture. The skill is in the curated directory of openai/skills; restart Codex after installation so it can load the skill. The source does not document a more specific destination configuration.
tmp="$(mktemp -d)"
git clone --depth 1 https://github.com/openai/skills.git "$tmp"
mkdir -p ~/.claude/skills
cp -R "$tmp/skills/.curated/notion-knowledge-capture" ~/.claude/skills/
rm -rf "$tmp"Generated from the source repository and skill path; it copies only this skill's folder. If the author's install steps above differ, follow those first. To scope it to one project, replace ~/.claude/skills with that project's .claude/skills.
How do you use this skill?
Once installed, send your agent any of these to trigger it:
- Turn this conversation into a team wiki page for engineers and link it to related existing pages.
Use a natural-language request such as: “Turn this conversation into a team wiki page for engineers and link it to related existing pages.” The skill will clarify the purpose, audience, content type, and create-versus-update status, then search Notion, select a database template, and create or update the page. If Notion MCP is unavailable, the source instructs users to configure it and complete OAuth login first.
What are this skill's strengths and limitations?
- Covers several concrete capture formats, including decisions, how-tos, FAQs, learning notes, and documentation.
- Provides an end-to-end workflow for finding existing pages, creating or updating content, and maintaining related links.
- Explicitly structures summaries, context, source links, tags, owners, statuses, and relations.
- Core operation depends on Notion MCP and its Notion actions; it cannot perform the workflow without a Notion connection.
- Database selection depends on guides and templates in reference/, whose detailed contents are not provided here.
- The README states that the overall repository is deprecated and points users to the OpenAI Plugins repository for current examples.
- The source provides no test suite, platform-version matrix, or cost information.
How does this skill compare with similar options?
Side by side with related skills; every score comes from the same FSRS standard.
| Skill | FS score | Stars | Last updated | License |
|---|---|---|---|---|
| Notion Knowledge Capture this page ✓ OpenAI · Official | 36 · Not recommended | ★ 28k | 4mo ago | — |
| Recursive Research | 50 · Use with care | ★ 49 | 6mo ago | MIT |
| Obsidian Wiki Query | 50 · Use with care | ★ 16k | 1mo ago | MIT |
| Compound Vault Methodology Modes | 56 · Use with care | ★ 16k | 1mo ago | MIT |
| Wiki Log Folder | 55 · Use with care | ★ 16k | 1mo ago | MIT |
How did FollowSkills review this skill?
The skill specifies Notion search, fetch, create, and update operations, exposes part of its data flow and OAuth setup, and asks the user to choose among multiple destinations; however, it lacks explicit pre-write confirmation, sensitive-data handling, least-privilege guidance, rollback, and retention boundaries. Remote MCP writes create external side effects, so points are deducted.
The main workflow is broadly self-consistent and includes a path for an unconnected Notion MCP; however, referenced files are not fully present in the supplied material, and there is little diagnostic handling for malformed input, failed writes, schema mismatches, or partial success. No executable reproduction evidence is supplied, so the static score remains conservative.
The audience, capture types, and primary scenarios are reasonably clear across wikis, how-tos, FAQs, and decision records; however, non-fit boundaries and Chinese-language behavior are not defined. The core capability depends entirely on a remote Notion service, with no evidence about reachability from mainland-China networks, so points are deducted.
The documentation has clear sections, a quick start, workflow, references, examples, and evaluation files; however, the license is unknown, versioning and changelog information are absent, maintenance ownership and update path are unclear, and the repository README states that the repository is deprecated. These governance gaps reduce the score.
The skill plausibly transforms conversations into structured, linkable Notion pages, and its examples show usable sections, properties, and linking patterns; however, actual success depends on the correct database schema, Notion connectivity, and agent execution. The supplied material contains no real execution verification, and user review remains necessary, so the score is limited under static calibration.
Committed evaluation scenarios, expected behaviors, and success criteria provide some auditable evidence; however, the materials describe manual evaluation rather than executable CI-backed tests, and no third-party execution results are supplied. The examples are largely illustrative, so independent reproduction remains limited.
Open a dimension to read why it scored that way
Evidence confidence：Low — Mostly static review, author material or a limited demo; useful for discovery, not high-risk decisions.
See the full review method →