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.
Works with
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionnotion-knowledge-captureExecute the skills CLI command in your project's root directory to begin installation:
Fetches notion-knowledge-capture from makenotion/claude-code-notion-plugin and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate notion-knowledge-capture. Access via /notion-knowledge-capture in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
0
total installs
0
this week
302
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
302
stars
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:
Make data-driven prioritization decisions faster
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Prerequisites
Time Estimate
30-60 minutes to see productivity improvements
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid when
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
mattpocock/skills
parcadei/continuous-claude-v3
cursor/plugins
ailabs-393/ai-labs-claude-skills
pproenca/dot-skills
ailabs-393/ai-labs-claude-skills
Registry listing for notion-knowledge-capture matched our evaluation — installs cleanly and behaves as described in the markdown.
Keeps context tight: notion-knowledge-capture is the kind of skill you can hand to a new teammate without a long onboarding doc.
notion-knowledge-capture has been reliable in day-to-day use. Documentation quality is above average for community skills.
We added notion-knowledge-capture from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
Useful defaults in notion-knowledge-capture — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
I recommend notion-knowledge-capture for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
Solid pick for teams standardizing on skills: notion-knowledge-capture is focused, and the summary matches what you get after install.
notion-knowledge-capture fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
Solid pick for teams standardizing on skills: notion-knowledge-capture is focused, and the summary matches what you get after install.
Registry listing for notion-knowledge-capture matched our evaluation — installs cleanly and behaves as described in the markdown.
showing 1-10 of 34