notion-knowledge-capture

notion-knowledge-capture is a skill for Codex from cass-2003/local-workflow-skill. It costs 39 tokens per session (790 once invoked), scanned A, a copy of notion-knowledge-capture, MIT.

A workflow for turning conversations and notes into structured, linkable Notion pages such as wiki articles, how-to guides, decisions, and FAQs.

In plain words
What is it for?
Use it to capture meeting decisions, document procedures, create FAQs, record learnings, and update existing Notion knowledge pages.
Why use it?
It makes useful knowledge and decisions easier to organise, find, and connect with related information.

Skill for Codex

Written for Codex: agents/openai.yaml present. Also seen: mentions Codex.

Good fit Use it to capture meeting decisions, document procedures, create FAQs, record learnings, and update existing Notion knowledge pages.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/cass-2003/local-workflow-skill/notion-knowledge-capture
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add cass-2003/local-workflow-skill --skill notion-knowledge-capture
Clone the repo
git clone --depth 1 https://github.com/cass-2003/local-workflow-skill

Made for: Codex.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for notion-knowledge-capture

README.md
[![agentmods](https://agentmods.dev/badge/skills/cass-2003/local-workflow-skill/notion-knowledge-capture/github.svg)](https://agentmods.dev/skills/cass-2003/local-workflow-skill/notion-knowledge-capture)
Your own site
<a href="https://agentmods.dev/skills/cass-2003/local-workflow-skill/notion-knowledge-capture"><img src="https://agentmods.dev/badge/skills/cass-2003/local-workflow-skill/notion-knowledge-capture/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for notion-knowledge-capture

Your own site · 80×15
<a href="https://agentmods.dev/skills/cass-2003/local-workflow-skill/notion-knowledge-capture"><img src="https://agentmods.dev/badge/skills/cass-2003/local-workflow-skill/notion-knowledge-capture.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 39 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 790 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin 100% copy Near-identical to another mod in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00039 $0.00790
Opus 5 $0.00019 $0.00395
Sonnet 5 $0.00008 $0.00158
Haiku 4.5 $0.00004 $0.00079

Measured 5d ago against content hash b49383b229bc, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

notion-knowledge-capture scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 5d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

Origin

This is a copy

100% identical to notion-knowledge-capture — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

skills/content-authoring/codex/notion-knowledge-capture/SKILL.md · 57 lines

How it starts

The opening of the file, as written. The whole thing — 57 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Knowledge Capture

Convert conversations and notes into structured, linkable Notion pages for easy reuse.

Quick start

  1. Clarify what to capture (decision, how-to, FAQ, learning, documentation) and target audience.
  2. Identify the right database/template in reference/ (team wiki, how-to, FAQ, decision log, learning, documentation).
  3. Pull any prior context from Notion with Notion:notion-searchNotion:notion-fetch (existing pages to update/link).
  4. Draft the page with Notion:notion-create-pages using the database’s schema; include summary, context, source links, and tags/owners.
  5. Link from hub pages and related records; update status/owners with Notion:notion-update-page as the source evolves.

Workflow

0) If any MCP call fails because Notion MCP is not connected, pause and set it up:

  1. Add the Notion MCP:
    • codex mcp add notion --url https://mcp.notion.com/mcp
  2. Enable remote MCP client:
    • Set [features].rmcp_client = true in config.toml or run codex --enable rmcp_client
  3. 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) Define the capture

  • Ask purpose, audience, freshness, and whether this is new or an update.
  • Determine content type: decision, how-to, FAQ, concept/wiki entry, learning/note, documentation page.

2) Locate destination

  • Pick the correct database using reference/*-database.md guides; confirm required properties (title, tags, owner, status, date, relations).
  • If multiple candidate databases, ask the user which to use; otherwise, create in the primary wiki/documentation DB.

3) Extract and structure

  • Extract facts, decisions, actions, and rationale from the conversation.
  • For decisions, record alternatives, rationale, and outcomes.
  • For how-tos/docs, capture steps, pre-reqs, links to assets/code, and edge cases.
  • For FAQs, phrase as Q&A with concise answers and links to deeper docs.

Read the full file on GitHub · 57 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 5d ago First seen · 57 lines · 39 tokens per session scan A b49383b229bc

Subscribe to this mod's changes

notion-knowledge-capture is a skill published in the GitHub repository cass-2003/local-workflow-skill (12 stars, last pushed 2mo ago), licensed MIT. It adds 39 tokens to every session and 790 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to notion-knowledge-capture, differing in 0 lines, and is treated as a copy.

Related

Other skills, from other repositories

recipe-create-meet-space

Create a Google Meet meeting space and share the join link.

googleworkspace/cli · 18 tokens

workthreads

SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…

specstoryai/getspecstory · 126 tokens

atmos-config

Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.

cloudposse/atmos · 31 tokens

story-readiness

Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…

Donchitos/Claude-Code-Game-Studios · 77 tokens

autotask-creator

Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.

Orkas-AI/Orkas · 5 tokens

projects

List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.

me2resh/apexyard · 24 tokens