Agent skill · Documentation

notion-knowledge-capture

Transforms conversations and discussions into structured documentation pages in Notion. Captures insights, decisions, and knowledge from chat context, formats appropriately, and saves to wikis or databases with proper organization and linking for easy discovery.

Prat011github.com/Prat011GitHub ↗
claude-codecodex
Install
npx skills add Prat011/awesome-llm-skills --skill notion-knowledge-capture --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 14
SKILL.md size: 7 KB
Bundled scripts: none
Path: notion-knowledge-capture/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 1,435
Language: Python

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# 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:notion-search` to find appropriate wiki page/database 4. **Create page**: Use `Notion:notion-create-pages` to save content 5. **Make discoverable**: Link from relevant hub pages, add to databases, or update wiki navigation so others can find it ## Knowledge Capture Workflow ### Step 1: Identify content to capture ``` From 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 ``` ### Step 2: Determine content type ``` Classify the knowledge: - Concept/Definition - How-to Guide - Decision Record - FAQ Entry - Meeting Summary - Learning/P

What's inside
Steps it walks through
  1. Quick Start
  2. Knowledge Capture Workflow
  3. Step 1: Identify content to capture
  4. Step 2: Determine content type
  5. Step 3: Structure the content
  6. Step 4: Determine destination
  7. Step 5: Create the page
  8. Step 6: Make content discoverable
  9. Content Types
  10. Destination Patterns
  11. Content Extraction from Conversations
  12. Formatting Best Practices
  13. Indexing and Organization
  14. Update Management
Ships with 13 files
  • evaluations/README.md
  • evaluations/conversation-to-wiki.json
  • evaluations/decision-record.json
  • examples/conversation-to-faq.md
  • examples/decision-capture.md
  • examples/how-to-guide.md
  • reference/database-best-practices.md
  • reference/decision-log-database.md
  • reference/documentation-database.md
  • reference/faq-database.md
  • reference/how-to-guide-database.md
  • reference/learning-database.md
  • reference/team-wiki-database.md
More from awesome-llm-skills
All skills →
About this skill
What does the notion-knowledge-capture skill do?

Transforms conversations and discussions into structured documentation pages in Notion. Captures insights, decisions, and knowledge from chat context, formats appropriately, and saves to wikis or databases with proper organization and linking for easy discovery.

How do I install it?

Run `npx skills add Prat011/awesome-llm-skills --skill notion-knowledge-capture --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From Prat011/awesome-llm-skills, a repository with 1,435 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going