Notion Knowledge Capture

Transforms conversations and discussions into structured documentation pages in Notion, formatted and saved to wikis or databases with…

You say
Buy it · $99 Read it before you buy $99 Written by makenotion · unverified publisher
Context cost
13.7k tokensestimated from the bundle, loaded when it triggers
Bundle
14 files · 54.7 kBtext throughout, nothing executable
Licence
MITpaid listing
Last change
no release on file
Servers it uses
Noneruns standalone

What it does

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.

Installed, it changes the agent in these ways.

What this skill changes about the agent is not written down here yet. The listing was collected from its source, and the description is in its own SKILL.md.

Workflow

Runs a procedure end to end.

notiondocumentationknowledge-base

The skill itself

This is the whole product. A skill is instructions the model reads, so there is nothing behind the listing you cannot see first — the front matter loads with every session, and the body below it loads when the skill triggers.

SKILL.md7.2 kB · 201 lines
--- name: notion-knowledge-capture description: 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. ---
6# Knowledge Capture
7
8Transforms 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.
9
10## Quick Start
11
12When asked to save information to Notion:
13
141. **Extract content**: Identify key information from conversation context
152. **Structure information**: Organize into appropriate documentation format
163. **Determine location**: Use Notion:notion-search to find appropriate wiki page/database
174. **Create page**: Use Notion:notion-create-pages to save content
185. **Make discoverable**: Link from relevant hub pages, add to databases, or update wiki navigation so others can find it
19
20## Knowledge Capture Workflow
21
22### Step 1: Identify content to capture
23
24```
25From conversation context, extract:
26- Key concepts and definitions
27- Decisions made and rationale
28- How-to information and procedures
29- Important insights or learnings
30- Q&A pairs
31- Examples and use cases
32```
33
34### Step 2: Determine content type
35
36```
37Classify the knowledge:
38- Concept/Definition
39- How-to Guide
40- Decision Record
41- FAQ Entry
42- Meeting Summary
43- Learning/Post-mortem
44- Reference Documentation
45```
46
47### Step 3: Structure the content
48
49```
50Format appropriately based on content type:
51- Use templates for consistency
52- Add clear headings and sections
53- Include examples where helpful
54- Add relevant metadata
55- Link to related pages
56```
57
58### Step 4: Determine destination
59
60```
61Where to save:
62- Wiki page (general knowledge base)
63- Specific project page (project-specific knowledge)
64- Documentation database (structured docs)
65- FAQ database (questions and answers)
66- Decision log (architecture/product decisions)
67- Team wiki (team-specific knowledge)
68```
69
70### Step 5: Create the page
71
72```
73Use Notion:notion-create-pages:
74- Set appropriate title
75- Use structured content from template
76- Set properties if in database
77- Add tags/categories
78- Link to related pages
79```
80
81### Step 6: Make content discoverable
82
83```
84Link the new page so others can find it:
85
861. Update hub/index pages:
87 - Add link to wiki table of contents page
88 - Add link from relevant project page
89 - Add link from category/topic page (e.g., "Engineering Docs")
90
912. If page is in a database:
92 - Set appropriate tags/categories
93 - Set status (e.g., "Published")
94 - Add to relevant views
95
963. Optionally update parent page:
97 - If saved under a project, add to project's "Documentation" section
98 - If in team wiki, ensure it's linked from team homepage
99
100Example:
101Notion:notion-update-page
102page_id: "team-wiki-homepage-id"
103command: "insert_content_after"
104selection_with_ellipsis: "## How-To Guides..."
105new_str: "- <mention-page url='...'>How to Deploy to Production</mention-page>"
106```
107
108This step ensures the knowledge doesn't become "orphaned" - it's properly connected to your workspace's navigation structure.
109
110## Content Types
111
112Choose appropriate structure based on content:
113
114**Concept**: Overview → Definition → Characteristics → Examples → Use Cases → Related
115**How-To**: Overview → Prerequisites → Steps (numbered) → Verification → Troubleshooting → Related
116**Decision**: Context → Decision → Rationale → Options Considered → Consequences → Implementation
117**FAQ**: Short Answer → Detailed Explanation → Examples → When to Use → Related Questions
118**Learning**: What Happened → What Went Well → What Didn't → Root Causes → Learnings → Actions
119
120## Destination Patterns
121
122**General Wiki**: Standalone page → add to index → tag → link from related pages
123
124**Project Wiki**: Child of project page → link from project overview → tag with project name
125
126**Documentation Database**: Use properties (Title, Type, Category, Tags, Last Updated, Owner)
127
128**Decision Log Database**: Use properties (Decision, Date, Status, Domain, Deciders, Impact)
129
130**FAQ Database**: Use properties (Question, Category, Tags, Last Reviewed, Useful Count)
131
132See [reference/database-best-practices.md](reference/database-best-practices.md) for database selection guide and individual schema files.
133
134## Content Extraction from Conversations
135
136**Chat Discussion**: Key points, conclusions, resources, action items, Q&A
137
138**Problem-Solving**: Problem statement, approaches tried, solution, why it worked, future considerations
139
140**Knowledge Sharing**: Concept explained, examples, best practices, common pitfalls, resources
141
142**Decision Discussion**: Question, options, trade-offs, decision, rationale, next steps
143
144## Formatting Best Practices
145
146**Structure**: Use # (title), ## (sections), ### (subsections) consistently
147
148**Writing**: Start with overview, use bullets, keep paragraphs short, add examples
149
150**Linking**: Link related pages, mention people, reference resources, create bidirectional links
151
152**Metadata**: Include date, author, tags, status
153
154**Searchability**: Clear titles, natural keywords, common search tags, image alt-text
155
156## Indexing and Organization
157
158**Wiki Index**: Organize by sections (Getting Started, How-To Guides, Reference, FAQs, Decisions) with page links
159
160**Category Pages**: Create landing pages with overview, doc links, and recent updates
161
162**Tagging Strategy**: Use consistent tags for technology/tools, topics, audience, and status
163
164## Update Management
165
166**Create New**: Content is substantive (>2 paragraphs), will be referenced multiple times, part of knowledge base, needs independent discovery
167
168**Update Existing**: Adding to existing topic, correcting info, expanding concept, updating for changes
169
170**Versioning**: Add update history section for significant changes (date, author, what changed, why)
171
172## Best Practices
173
1741. **Capture promptly**: Document while context is fresh
1752. **Structure consistently**: Use templates for similar content
1763. **Link extensively**: Connect related knowledge
1774. **Write for discovery**: Use searchable titles and tags
1785. **Include context**: Why this matters, when to use
1796. **Add examples**: Concrete examples aid understanding
1807. **Maintain**: Review and update periodically
1818. **Get feedback**: Ask if documentation is helpful
182
183## Advanced Features
184
185**Documentation databases**: See [reference/database-best-practices.md](reference/database-best-practices.md) for database schema patterns.
186
187## Common Issues
188
189**"Not sure where to save"**: Default to general wiki, can move later
190**"Content is fragmentary"**: Group related fragments into cohesive doc
191**"Already exists"**: Search first, update existing if appropriate
192**"Too informal"**: Clean up language while preserving insights
193
194## Examples
195
196See [examples/](examples/) for complete workflows:
197
198- [examples/conversation-to-faq.md](examples/conversation-to-faq.md) - FAQ from Q&A
199- [examples/decision-capture.md](examples/decision-capture.md) - Decision record
200- [examples/how-to-guide.md](examples/how-to-guide.md) - How-to from discussion
201
In the file
SKILL.md940 words
Files14
LicenceMIT
Why you can read it

Nothing in a skill executes. The client loads the text and the model follows it, so a skill can be audited the way a runbook is — by reading it.

What it costs in context

Skills are not billed by the call. They are paid for in context: every token the instructions occupy is a token your code, your diff and your conversation cannot use. Here is what this one takes and when it takes it.

≈80
always loaded
The name and description, so the model knows the skill exists and when to reach for it.
13,595
on trigger
The instruction body and 13 supporting files, read only when the skill fires.
6.8%
of a 200k window
Ten skills this size would take about 68% of the window before you open a file.
050k100k150k200k context window

13.7k tokens, estimated from the bundle at four bytes to the token, held for the rest of the session once it triggers. Heavy. Teams tend to install this one per project rather than globally, and load it only when the job comes up.

Servers bill, skills cost

A server charges by the month. A skill charges once per session, in context, and then keeps charging it for as long as the session lives.

Before and after

The same question, put to the same model twice: once as it comes, and once with these instructions loaded.

No worked example has been published for this skill yet.

Adoption
Installsnone yet
Ratingno reviews yet

The procedure it runs

The procedure has not been published here. It is in the skill’s own SKILL.md, which its author has not sent to the marketplace yet.

Prose, not code

These steps are written for a model to follow, not executed by a runtime. It can still be told to skip one, and it will say so when it does.

Servers it uses

None. This skill calls no MCP servers at all.

Everything it needs is in the instructions, so it works in a project with nothing connected — the model reads the file and changes how it works with what it can already reach.

It writes no files and reaches no network. All it changes is how the model reasons and writes.

What it asks for
Writes filesno
Network accessno

Read from the allowed-tools line of this skill’s own SKILL.md. A skill grants no permissions of its own — it can only ask for tools your client already has.

What it will not do

Every skill is narrow, and the useful ones say where they stop. These are the jobs this one is the wrong tool for.

What this skill is not for has not been published here. Nothing is implied by that: it is a section the author has not filled in.

What is in the bundle

14 files, 54.7 kB on disk. A bundle is text throughout: the instructions the model reads, plus the templates it fills in.

  • SKILL.md7.2 kB
  • evaluations/README.md3.5 kB
  • evaluations/conversation-to-wiki.json2.0 kB
  • evaluations/decision-record.json2.2 kB
  • examples/conversation-to-faq.md16.3 kB
  • examples/decision-capture.md3.6 kB
  • examples/how-to-guide.md2.9 kB
  • reference/database-best-practices.md3.1 kB
  • reference/decision-log-database.md2.6 kB
  • reference/documentation-database.md3.7 kB
  • reference/faq-database.md2.7 kB
  • reference/how-to-guide-database.md1.7 kB
  • reference/learning-database.md1.8 kB
  • reference/team-wiki-database.md1.4 kB
What is not in it

No dependencies and nothing executable: a skill is text the agent reads, so the bundle is 14 files you can review in full before installing. The MIT licence covers the templates and examples as well as the instructions.

Install

Installing copies the bundle into your project. Nothing runs at install time — the files sit on disk until the model reads them.

$99 once
Notion Knowledge Capture · MIT · makenotion
one-time
Price$99 once
LicenceMIT — the author’s, unchanged by this purchase
Paid throughStripe, once, on the card you add at the checkout
Keeps workingfor good — the files are yours once they are on disk
Updatesevery update its author ships, delivered through this account

You can read the whole bundle before paying — the SKILL.md above is the product, not a preview of it. What the money buys is the delivery: the folder packaged and handed to your machine by key, every update its author ships, and our support if it does not do what this listing says. The terms of use are MIT, set by the author and unchanged by buying it here.

Payment runs through Stripe, on a page like this one rather than a redirect. Once there is an account it joins the same mcprush invoice as everything else you run, so there is never a second card to enter.

Which clients pick it up on their own

A skill is a folder of text. A client with a skills folder reads it without being told; everywhere else the same text works, it is just handed to the model rather than found.

Claude Code.claude/skills/
Claude Desktop
ChatGPT
Cursor.cursor/skills/
VS Code.github/skills/
Codex CLI.agents/skills/
Gemini CLI.gemini/skills/
Grok.grok/skills/
Zed.agents/skills/
Windsurf.windsurf/skills/
Agent SDK.claude/skills/
HTTP / API
This release
Versionnot versioned
Publishedno release date on file
Price$99
Referencemakenotion/notion-knowledge-capture

Versions

Its author publishes no version number, so there is nothing here to pin to: what you install is the folder as it stands today. Instructions change more often than APIs do — a skill can be rewritten entirely without anything it depends on moving.

v
  • No earlier releases have been published to the marketplace.
Pinning

Nothing to pin to: this skill carries no version number of its own. What you install is what the folder holds on the day you install it.

Reviews

no reviews yet · no installs yet

Nobody has reviewed this skill yet. The rating is the mean of the reviews written here, so there is none until somebody writes the first.

Who can post

Only accounts that have had the skill installed for fourteen days, so a review is written after living with it rather than after reading it. Publishers may reply once.

Who wrote it

MA
makenotion

Publishes on mcprush.

0 servers listed1 skill listednot claimed
Profile
Publisher
Servers0