notion-knowledge-capture by makenotion/claude-code-notion-plugin
npx skills add https://github.com/makenotion/claude-code-notion-plugin --skill notion-knowledge-capture将对话、讨论和见解转化为 Notion 工作区中的结构化文档。从聊天上下文中捕获知识,进行适当格式化,并通过适当的组织和链接保存到正确的位置。
当被要求将信息保存到 Notion 时:
Notion:notion-search 查找合适的维基页面/数据库Notion:notion-create-pages 保存内容从对话上下文中提取:
- 关键概念和定义
- 做出的决定及其理由
- 操作方法和流程信息
- 重要的见解或学习成果
- 问答对
- 示例和用例
对知识进行分类:
- 概念/定义
- 操作指南
- 决策记录
- 常见问题条目
- 会议摘要
- 学习/事后分析
- 参考文档
根据内容类型进行适当格式化:
- 使用模板以确保一致性
- 添加清晰的标题和章节
- 在有用处包含示例
- 添加相关的元数据
- 链接到相关页面
广告位招租
在这里展示您的产品或服务
触达数万 AI 开发者,精准高效
保存位置:
- 维基页面(通用知识库)
- 特定项目页面(项目特定知识)
- 文档数据库(结构化文档)
- 常见问题数据库(问题和答案)
- 决策日志(架构/产品决策)
- 团队维基(团队特定知识)
使用 Notion:notion-create-pages:
- 设置适当的标题
- 使用模板中的结构化内容
- 如果在数据库中,则设置属性
- 添加标签/类别
- 链接到相关页面
链接新页面,以便其他人可以找到它:
1. 更新中心/索引页面:
- 添加到维基目录页面
- 从相关项目页面添加链接
- 从类别/主题页面添加链接(例如,“工程文档”)
2. 如果页面在数据库中:
- 设置适当的标签/类别
- 设置状态(例如,“已发布”)
- 添加到相关视图
3. 可选更新父页面:
- 如果保存在项目下,则添加到项目的“文档”部分
- 如果在团队维基中,确保从团队主页链接
示例:
Notion:notion-update-page
page_id: "team-wiki-homepage-id"
command: "insert_content_after"
selection_with_ellipsis: "## How-To Guides..."
new_str: "- <mention-page url='...'>How to Deploy to Production</mention-page>"
此步骤确保知识不会变成“孤立”状态——它被正确地连接到工作区的导航结构中。
根据内容选择适当的结构:
概念:概述 → 定义 → 特征 → 示例 → 用例 → 相关 操作指南:概述 → 先决条件 → 步骤(编号) → 验证 → 故障排除 → 相关 决策:背景 → 决策 → 理由 → 考虑的选项 → 后果 → 实施 常见问题:简短答案 → 详细解释 → 示例 → 何时使用 → 相关问题 学习:发生了什么 → 哪些做得好 → 哪些没做好 → 根本原因 → 学习成果 → 行动项
通用维基:独立页面 → 添加到索引 → 打标签 → 从相关页面链接
项目维基:项目页面的子页面 → 从项目概述链接 → 用项目名称打标签
文档数据库:使用属性(标题、类型、类别、标签、最后更新、所有者)
决策日志数据库:使用属性(决策、日期、状态、领域、决策者、影响)
常见问题数据库:使用属性(问题、类别、标签、最后审阅、有用计数)
有关数据库选择指南和单独的架构文件,请参阅 reference/database-best-practices.md。
聊天讨论:要点、结论、资源、行动项、问答
问题解决:问题陈述、尝试的方法、解决方案、为何有效、未来考虑
知识分享:解释的概念、示例、最佳实践、常见陷阱、资源
决策讨论:问题、选项、权衡、决策、理由、后续步骤
结构:一致地使用 #(标题)、##(章节)、###(子章节)
写作:从概述开始,使用项目符号,保持段落简短,添加示例
链接:链接相关页面、提及人员、引用资源、创建双向链接
元数据:包含日期、作者、标签、状态
可搜索性:清晰的标题、自然的关键词、常见的搜索标签、图片替代文本
维基索引:按章节组织(入门指南、操作指南、参考、常见问题、决策)并包含页面链接
类别页面:创建包含概述、文档链接和最近更新的着陆页
标签策略:对技术/工具、主题、受众和状态使用一致的标签
创建新的:内容是实质性的(>2 段)、将被多次引用、属于知识库的一部分、需要独立发现
更新现有的:添加到现有主题、更正信息、扩展概念、为变更而更新
版本控制:为重大更改添加更新历史记录部分(日期、作者、更改内容、原因)
文档数据库:有关数据库架构模式,请参阅 reference/database-best-practices.md。
“不确定保存在哪里”:默认保存到通用维基,以后可以移动 “内容零散”:将相关的零散内容分组为连贯的文档 “已存在”:先搜索,如果合适则更新现有内容 “太随意”:清理语言,同时保留见解
有关完整工作流程,请参阅 examples/:
每周安装量
251
仓库
GitHub 星标数
279
首次出现
2026年2月7日
安全审计
安装于
opencode247
gemini-cli246
codex246
github-copilot243
kimi-cli242
amp242
Transforms conversations, discussions, and insights into structured documentation in your Notion workspace. Captures knowledge from chat context, formats it appropriately, and saves it to the right location with proper organization and linking.
When asked to save information to Notion:
Notion:notion-search to find appropriate wiki page/databaseNotion:notion-create-pages to save contentFrom conversation context, extract:
- Key concepts and definitions
- Decisions made and rationale
- How-to information and procedures
- Important insights or learnings
- Q&A pairs
- Examples and use cases
Classify the knowledge:
- Concept/Definition
- How-to Guide
- Decision Record
- FAQ Entry
- Meeting Summary
- Learning/Post-mortem
- Reference Documentation
Format appropriately based on content type:
- Use templates for consistency
- Add clear headings and sections
- Include examples where helpful
- Add relevant metadata
- Link to related pages
Where to save:
- Wiki page (general knowledge base)
- Specific project page (project-specific knowledge)
- Documentation database (structured docs)
- FAQ database (questions and answers)
- Decision log (architecture/product decisions)
- Team wiki (team-specific knowledge)
Use Notion:notion-create-pages:
- Set appropriate title
- Use structured content from template
- Set properties if in database
- Add tags/categories
- Link to related pages
Link the new page so others can find it:
1. Update hub/index pages:
- Add link to wiki table of contents page
- Add link from relevant project page
- Add link from category/topic page (e.g., "Engineering Docs")
2. If page is in a database:
- Set appropriate tags/categories
- Set status (e.g., "Published")
- Add to relevant views
3. Optionally update parent page:
- If saved under a project, add to project's "Documentation" section
- If in team wiki, ensure it's linked from team homepage
Example:
Notion:notion-update-page
page_id: "team-wiki-homepage-id"
command: "insert_content_after"
selection_with_ellipsis: "## How-To Guides..."
new_str: "- <mention-page url='...'>How to Deploy to Production</mention-page>"
This step ensures the knowledge doesn't become "orphaned" - it's properly connected to your workspace's navigation structure.
Choose appropriate structure based on content:
Concept : Overview → Definition → Characteristics → Examples → Use Cases → Related How-To : Overview → Prerequisites → Steps (numbered) → Verification → Troubleshooting → Related Decision : Context → Decision → Rationale → Options Considered → Consequences → Implementation FAQ : Short Answer → Detailed Explanation → Examples → When to Use → Related Questions Learning : What Happened → What Went Well → What Didn't → Root Causes → Learnings → Actions
General Wiki : Standalone page → add to index → tag → link from related pages
Project Wiki : Child of project page → link from project overview → tag with project name
Documentation Database : Use properties (Title, Type, Category, Tags, Last Updated, Owner)
Decision Log Database : Use properties (Decision, Date, Status, Domain, Deciders, Impact)
FAQ Database : Use properties (Question, Category, Tags, Last Reviewed, Useful Count)
See reference/database-best-practices.md for database selection guide and individual schema files.
Chat Discussion : Key points, conclusions, resources, action items, Q&A
Problem-Solving : Problem statement, approaches tried, solution, why it worked, future considerations
Knowledge Sharing : Concept explained, examples, best practices, common pitfalls, resources
Decision Discussion : Question, options, trade-offs, decision, rationale, next steps
Structure : Use # (title), ## (sections), ### (subsections) consistently
Writing : Start with overview, use bullets, keep paragraphs short, add examples
Linking : Link related pages, mention people, reference resources, create bidirectional links
Metadata : Include date, author, tags, status
Searchability : Clear titles, natural keywords, common search tags, image alt-text
Wiki Index : Organize by sections (Getting Started, How-To Guides, Reference, FAQs, Decisions) with page links
Category Pages : Create landing pages with overview, doc links, and recent updates
Tagging Strategy : Use consistent tags for technology/tools, topics, audience, and status
Create New : Content is substantive (>2 paragraphs), will be referenced multiple times, part of knowledge base, needs independent discovery
Update Existing : Adding to existing topic, correcting info, expanding concept, updating for changes
Versioning : Add update history section for significant changes (date, author, what changed, why)
Documentation databases : See reference/database-best-practices.md for database schema patterns.
"Not sure where to save" : Default to general wiki, can move later "Content is fragmentary" : Group related fragments into cohesive doc "Already exists" : Search first, update existing if appropriate "Too informal" : Clean up language while preserving insights
See examples/ for complete workflows:
Weekly Installs
251
Repository
GitHub Stars
279
First Seen
Feb 7, 2026
Security Audits
Gen Agent Trust HubFailSocketPassSnykPass
Installed on
opencode247
gemini-cli246
codex246
github-copilot243
kimi-cli242
amp242
Azure RBAC 权限管理工具:查找最小角色、创建自定义角色与自动化分配
104,600 周安装