com um clique
knowledge-capture
// Transform conversations and discussions into structured documentation pages in Notion. Captures insights, decisions, and knowledge from chat context with proper organization and linking.
// Transform conversations and discussions into structured documentation pages in Notion. Captures insights, decisions, and knowledge from chat context with proper organization and linking.
Insert a new row into a specified Notion database using natural-language property values. Handles property name matching and validation.
Create a new Notion page, optionally under a specific parent. Automatically structures content based on page type (meeting notes, project pages, etc.).
Create a new task in the user's Notion tasks database with sensible defaults for due date, status, owner, and project.
Query a Notion database by name or ID and return structured, readable results with optional filters and sorting.
Quickly find pages or databases in Notion by title keywords. Returns precise matches rather than comprehensive results.
Prepare meeting materials by gathering context from Notion, enriching with research, and creating both an internal pre-read and external agenda saved to Notion.
| name | knowledge-capture |
| description | Transform conversations and discussions into structured documentation pages in Notion. Captures insights, decisions, and knowledge from chat context with proper organization and linking. |
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:
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 |
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)
From chat discussions, extract:
From problem-solving sessions:
From knowledge sharing:
After creating a page, link it so others can find it:
| 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 |