Agent skill

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.

Stars 0
Forks 0

Install this agent skill to your Project

npx add-skill https://github.com/yurake/skills/tree/main/.curated/notion-knowledge-capture

Metadata

Additional technical details for this skill

short description
Capture conversations into structured Notion pages

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

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

Expand your agent's capabilities with these related and highly-rated skills.

yurake/skills

issue-create

GitHub Issue を作成する手順。依頼を受けたとき、.github/ISSUE_TEMPLATE の内容に応じてテンプレを選び、必須項目を埋めて GitHub MCP(issue_write/create)で Issue を作成する。

0 0
Explore
yurake/skills

ci-fail-followup

PR 作成後に .github/workflows/ci.yml が失敗したときの対応手順。ローカルで pytest 全ケースを実行し、エラー有無で分岐。エラーがあれば修正して commit-push スキルでコミット・プッシュ、無ければ GitHub Actions のログを確認して原因を特定する。

0 0
Explore
yurake/skills

review-rules

セッションの会話から恒久的な振る舞いルールを抽出し、AGENTS.md と突き合わせて追加すべきものを提示する。出力は rules と agents_md_patch の二部構成。

0 0
Explore
yurake/skills

pr-create

PR 作成手順を自動化するためのガイド。依頼を受けたとき、または 参照しているTODOファイル の「PR 作成」以外が完了したタイミングでタイトル・本文整形、テンプレ適用、MCP での PR 作成を行う。

0 0
Explore
yurake/skills

architecture-patterns

Implement proven backend architecture patterns including Clean Architecture, Hexagonal Architecture, and Domain-Driven Design. Use when architecting complex backend systems or refactoring existing applications for better maintainability.

0 0
Explore
yurake/skills

test-risk-analyzer

あらゆる言語/スタックで潜在バグリスクを洗い出し、追加すべきテストケースを提案する。未テストのエッジケース探索や安全性確認、カバレッジ強化のテスト案提示を求められたときに使用する。

0 0
Explore

Didn't find tool you were looking for?

Be as detailed as possible for better results