Knowledge Capture
- 22 installs
- 19 repo stars
- Updated February 7, 2026
- makenotion/cursor-notion-plugin
knowledge-capture saves structured Notion docs from conversation context.
About
The knowledge-capture skill transforms conversations and discussions into structured documentation pages in Notion with proper organization and linking. Workflow extracts key points from chat context, chooses structure by content type such as concept, how-to, decision, FAQ, or learning retrospective, searches Notion for the right wiki page or database destination, then creates the page via MCP with tags and backlinks. Destination patterns cover general wikis, project child pages, documentation databases, decision logs, and FAQ databases with appropriate properties. Best practices emphasize capturing promptly while context is fresh, linking extensively to related pages, using searchable titles, and including concrete examples. Post-creation steps update hub index pages and parent project documentation sections so content stays discoverable. 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.
- Extracts insights from conversations into structured docs.
- Chooses templates for concept, how-to, decision, and FAQ content.
- Places pages in wikis or databases with correct properties.
- Links new pages from hub and project index pages.
- Writes searchable titles with examples and context.
Knowledge Capture by the numbers
- 22 all-time installs (skills.sh)
- Ranked #988 of 1,879 Documentation skills by installs in the Skillselion catalog
- Data as of Jul 25, 2026 (Skillselion catalog sync)
knowledge-capture capabilities & compatibility
- Capabilities
- content type structure table · destination patterns and database properties · discoverability linking workflow
- Works with
- notion
- Use cases
- documentation · research
npx skills add https://github.com/makenotion/cursor-notion-plugin --skill knowledge-captureAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 22 |
|---|---|
| repo stars | ★ 19 |
| Last updated | February 7, 2026 |
| Repository | makenotion/cursor-notion-plugin ↗ |
How do I document this decision in our Notion wiki?
Turn chat discussions into structured, linked Notion documentation pages.
Who is it for?
Teams turning chat insights into durable Notion knowledge.
Skip if: Skip for ephemeral chat without documentation intent.
When should I use this skill?
User asks to save, capture, or document discussion content in Notion.
What you get
Published Notion page with structure, tags, and hub links.
Files
Knowledge Capture
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.
Quick Start
When asked to save information to Notion:
1. Extract content: Identify key information from conversation context 2. Structure information: Organize into appropriate documentation format 3. Determine location: Use Notion search to find appropriate wiki page/database 4. Create page: Use Notion MCP to save content 5. Make discoverable: Link from relevant hub pages, add to databases, or update wiki navigation
Content Types
Choose appropriate structure based on content:
| Type | Structure |
|---|---|
| Concept | Overview → Definition → Characteristics → Examples → Use Cases → Related |
| How-To | Overview → Prerequisites → Steps (numbered) → Verification → Troubleshooting |
| Decision | Context → Decision → Rationale → Options Considered → Consequences |
| FAQ | Short Answer → Detailed Explanation → Examples → When to Use |
| Learning | What Happened → What Went Well → What Didn't → Root Causes → Actions |
Destination Patterns
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)
Content Extraction
From chat discussions, extract:
- Key points and conclusions
- Resources and references
- Action items
- Q&A pairs
From problem-solving sessions:
- Problem statement
- Approaches tried
- Solution found
- Why it worked
- Future considerations
From knowledge sharing:
- Concept explained
- Examples provided
- Best practices
- Common pitfalls
Making Content Discoverable
After creating a page, link it so others can find it:
1. Update hub/index pages: Add link to wiki table of contents, relevant project page, or category page 2. If in a database: Set appropriate tags/categories, set status to "Published" 3. Update parent page: Add to project's "Documentation" section or team wiki homepage
Best Practices
1. Capture promptly: Document while context is fresh 2. Structure consistently: Use templates for similar content 3. Link extensively: Connect related knowledge 4. Write for discovery: Use searchable titles and tags 5. Include context: Why this matters, when to use 6. Add examples: Concrete examples aid understanding 7. Maintain: Review and update periodically
Common Issues
| Issue | Solution |
|---|---|
| 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 |
Related skills
Lark MarkdownInstantly turn any markdown file into clean, formatted Lark/Figma-compatible documents without manual reformatting.488k
Lark DocCreate, read, update, summarize, rewrite and manage Feishu/Lark cloud documents directly from agent workflows.401k16.1kLark WikiCreate, organize, query, and manage documents, spaces, and members inside Lark (Feishu) knowledge bases directly from AI agent workflows.397k16.1k
Domain ModelingBuild and sharpen a project's domain model: pin down domain terminology in a glossary and record architectural decisions as ADRs.318k202k
Opensource Guide CoachGet expert, attribution-safe guidance on launching and sustaining an open-source project.270k71Readme I18nMaintain consistent, updatable language selector blocks across every README variant in a multilingual repository.270k71FAQ
What does knowledge-capture do?
knowledge-capture saves structured Notion docs from conversation context.
When should I use knowledge-capture?
User asks to save, capture, or document discussion content in Notion.
Is this skill safe to install?
Review the Security Audits panel on this page before installing in production.