Capture conversations and decisions into structured, linkable Notion pages for documentation and knowledge reuse.
Works with
Supports six content types: decisions, how-to guides, FAQs, wiki entries, learning notes, and documentation pages, each with dedicated database templates and schemas.
Workflow includes search and fetch of existing Notion pages to avoid duplication and establish proper linking and relations.
Requires Notion MCP connection; includes setup steps for OAuth login and remote MC
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 davila7/claude-code-templates 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
24.2K
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
24.2K
stars
Convert conversations and notes into structured, linkable Notion pages for easy reuse.
reference/ (team wiki, how-to, FAQ, decision log, learning, documentation).Notion:notion-search → Notion:notion-fetch (existing pages to update/link).Notion:notion-create-pages using the database's schema; include summary, context, source links, and tags/owners.Notion:notion-update-page as the source evolves.codex mcp add notion --url https://mcp.notion.com/mcp[features].rmcp_client = true in config.toml or run codex --enable rmcp_clientcodex mcp login notionAfter 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.
reference/*-database.md guides; confirm required properties (title, tags, owner, status, date, relations).Notion:notion-create-pages with the correct data_source_id; set properties (title, tags, owner, status, dates, relations).reference/ to structure content (section headers, checklists).Notion:notion-update-page.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).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.
davila7/claude-code-templates
mattpocock/skills
parcadei/continuous-claude-v3
cursor/plugins
ailabs-393/ai-labs-claude-skills
pproenca/dot-skills
notion-knowledge-capture fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
Registry listing for notion-knowledge-capture matched our evaluation — installs cleanly and behaves as described in the markdown.
notion-knowledge-capture is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
notion-knowledge-capture reduced setup friction for our internal harness; good balance of opinion and flexibility.
Solid pick for teams standardizing on skills: notion-knowledge-capture is focused, and the summary matches what you get after install.
We added notion-knowledge-capture from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
notion-knowledge-capture reduced setup friction for our internal harness; good balance of opinion and flexibility.
Keeps context tight: notion-knowledge-capture is the kind of skill you can hand to a new teammate without a long onboarding doc.
We added notion-knowledge-capture from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
I recommend notion-knowledge-capture for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
showing 1-10 of 43