本文へ移動
cccskills
無料GitHub で公開

notion-knowledge-capture

Capture conversations and decisions into structured Notion pages; use when turning chats/notes into wiki entries, how-tos, decisions, or FAQs with proper linking.

インストール方法を見る

含まれるファイル(18)

  • SKILL.md3.2 KB
  • agents/openai.yaml512 B
  • assets/notion-small.svg15.4 KB
  • assets/notion.png8.3 KB
  • evaluations/conversation-to-wiki.json2.0 KB
  • evaluations/decision-record.json2.2 KB
  • evaluations/README.md3.4 KB
  • examples/conversation-to-faq.md15.9 KB
  • examples/decision-capture.md3.5 KB
  • examples/how-to-guide.md2.8 KB
  • LICENSE.txt1.0 KB
  • reference/database-best-practices.md2.8 KB
  • reference/decision-log-database.md2.0 KB
  • reference/documentation-database.md2.7 KB
  • reference/faq-database.md2.0 KB
  • reference/how-to-guide-database.md1.2 KB
  • reference/learning-database.md1.3 KB
  • reference/team-wiki-database.md927 B

SKILL.md(原文)

インストールする前に、エージェントに与えられる指示の中身を確認できます。

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-search → Notion: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.

4) Create/update in Notion

  • Use Notion:notion-create-pages with the correct data_source_id; set properties (title, tags, owner, status, dates, relations).
  • Use templates in reference/ to structure content (section headers, checklists).
  • If updating an existing page, fetch then edit via Notion:notion-update-page.

5) Link and surface

  • Add relations/backlinks to hub pages, related specs/docs, and teams.
  • Add a short summary/changelog for future readers.
  • If follow-up tasks exist, create tasks in the relevant database and link them.

References and examples

  • reference/ — database schemas and templates (e.g., team-wiki-database.md, how-to-guide-database.md, faq-database.md, decision-log-database.md, documentation-database.md, learning-database.md, database-best-practices.md).
  • examples/ — capture patterns in practice (e.g., decision-capture.md, how-to-guide.md, conversation-to-faq.md).

レビュー

まだレビューはありません。使ってみた感想をお寄せください。

同じリポジトリのスキル

概要と使いどころ

Build, review, refactor, or architect ASP.NET Core web applications using current official guidance for .NET web development. Use when working on Blazor Web Apps, Razor Pages, MVC, Minimal APIs, controller-based Web APIs, SignalR, gRPC, middleware, dependency injection, configuration, authentication, authorization, testing, performance, deployment, or ASP.NET Core upgrades.

日本語の概要は準備中です。原文の説明を表示しています。

openai/skills2.8万2026年9月9日 更新

Build, scaffold, refactor, and troubleshoot ChatGPT Apps SDK applications that combine an MCP server and widget UI. Use when Codex needs to design tools, register UI resources, wire the MCP Apps bridge or ChatGPT compatibility APIs, apply Apps SDK metadata or CSP or domain settings, or produce a docs-aligned project scaffold. Prefer a docs-first workflow by invoking the openai-docs skill or OpenAI developer docs MCP tools before generating code.

日本語の概要は準備中です。原文の説明を表示しています。

openai/skills2.8万2026年9月9日 更新

Build a composable CLI for Codex from API docs, an OpenAPI spec, existing curl examples, an SDK, a web app, an admin tool, or a local script. Use when the user wants Codex to create a command-line tool that can run from any repo, expose composable read/write commands, return stable JSON, manage auth, and pair with a companion skill.

日本語の概要は準備中です。原文の説明を表示しています。

openai/skills2.8万2026年9月9日 更新

Deploy applications and infrastructure to Cloudflare using Workers, Pages, and related platform services. Use when the user asks to deploy, host, publish, or set up a project on Cloudflare.

日本語の概要は準備中です。原文の説明を表示しています。

openai/skills2.8万2026年9月9日 更新

Help the user define a concrete, measurable goal before starting work, especially when they ask to use the goal tool, create a goal, set an objective, clarify success criteria, or turn a fuzzy intention into a quantitative outcome. Use this skill for goal creation and goal refinement only; it does not manage durable snapshots, decision logs, or long-running execution artifacts.

日本語の概要は準備中です。原文の説明を表示しています。

openai/skills2.8万2026年9月9日 更新

figma

無料

Use the Figma MCP server to fetch design context, screenshots, variables, and assets from Figma, and to translate Figma nodes into production code. Trigger when a task involves Figma URLs, node IDs, design-to-code implementation, or Figma MCP setup and troubleshooting.

日本語の概要は準備中です。原文の説明を表示しています。

openai/skills2.8万2026年9月9日 更新

openai のスキルをすべて見る

このスキルの問題を報告する