8.6k
GitHub Stars
2
Bundled Files
2 months ago
Catalog Refreshed
4 months ago
First Indexed
Readme & install
Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.
Installation
Preview and clipboard use veilstrat where the catalogue uses aiagentskills.
npx veilstrat add skill openai/skills --skill notion-knowledge-capture- LICENSE.txt1.0 KB
- SKILL.md3.2 KB
Overview
This skill converts conversations, notes, and meeting outcomes into structured, linkable Notion pages for team knowledge reuse. It helps turn chats into decisions, how-tos, FAQs, wiki entries, or documentation with correct schema, links, and owners. Use it to maintain a discoverable, up-to-date knowledge base.
How this skill works
Start by clarifying the capture purpose and audience, then select the appropriate Notion database or template from the reference set. The skill extracts facts, decisions, action items, and rationale from the source content, structures them to match the target schema, and creates or updates pages via Notion APIs. It adds properties (title, tags, owner, status, dates), backlinks to hubs, and related tasks so information is discoverable and actionable.
When to use it
- After meetings to record decisions and action items
- When turning a conversation or chat thread into a wiki or how-to guide
- To create concise FAQs from recurring support or product questions
- When documenting design rationale, alternatives, and outcomes
- To keep documentation synchronized with evolving discussions
Best practices
- Clarify capture intent and audience before drafting to choose the correct template
- Search Notion first for related pages to update rather than creating duplicates
- Include a short summary, source links, and a changelog entry on each page
- Record alternatives and rationale for decisions to preserve context
- Link pages to hub records and create follow-up tasks when actions are identified
Example use cases
- Post-standup decision capture: store rationale, chosen option, and owners in the decision log
- Customer support thread → FAQ: extract question/answer pairs and link to deeper docs
- How-to creation: convert a troubleshooting thread into step-by-step instructions with prerequisites and edge cases
- Onboarding docs: consolidate knowledge from multiple conversations into a team wiki page
- Documentation update: fetch an existing page, apply edits, and add a short changelog entry
FAQ
Pause and configure the Notion MCP. Add the MCP, enable remote client, and log in with OAuth. After successful login restart the tool and continue the capture flow.
How do I choose the right database?
Check the reference templates (team wiki, how-to, FAQ, decision log, learning, documentation). If multiple match, ask the team which database should own the record; default to the primary wiki/documentation DB if unsure.