This skill should be used when the user asks about "Notion knowledge management", "SECI in Notion", "documenting in Notion", "organizing knowledge in Notion", "Notion database architecture", "PARA in Notion", "second brain Notion", "Notion templates for knowledge", or needs to apply knowledge management principles using Notion's features.
/plugin marketplace add therealchrisrock/basho/plugin install km-notion@baThis skill inherits all available tools. When active, it can use any tool Claude has access to.
references/database-patterns.mdreferences/para-implementation.mdreferences/templates.mdThis skill extends knowledge-manager with Notion-specific implementations of SECI phases, PARA organization, CODE workflow, and native Notion architecture patterns.
seci-grai skill if needed)Goal: Share tacit knowledge through shared experience in Notion.
Notion Features:
Patterns:
Collaborative Exploration Pages
Create temporary "Exploration: [Topic]" pages
- Invite collaborators
- Add initial observations loosely
- Use comments for side discussions
- Delete after insights captured elsewhere
Team Wiki with Open Editing
Shared space with low barrier to contribute
- Anyone can add observations
- Comments surface tacit disagreements
- @mentions bring in domain experts
Meeting Notes as Socialization
Live collaborative notes during discussions
- Capture emerging shared understanding
- Use callouts for key insights
- Tag action items inline
GRAI Field: Socialization H→M achieved through iterative prompting with Notion content as context.
Goal: Convert tacit understanding into structured Notion pages.
Notion Features:
Patterns:
Template-Driven Capture
## Concept Template
- **What it is:** [Definition]
- **Why it matters:** [Rationale]
- **How it works:** [Mechanism]
- **Examples:** [Concrete illustrations]
- **Related to:** [Links to other pages]
Progressive Formalization
Stage 1: Bullet points (quick capture)
Stage 2: Paragraphs (expand ideas)
Stage 3: Sections with headings (structure)
Stage 4: Templates and properties (formalize)
Database-as-Glossary
Create "Concepts" database with:
- Name (title)
- Definition (text)
- Category (select)
- Related Concepts (relation)
- Status (Draft/Review/Published)
- Owner (person)
GRAI Field: Externalization M→H achieved when AI structures informal notes into Notion format.
Goal: Synthesize and organize explicit knowledge using Notion's database power.
Notion Features:
Patterns:
Hub Database Pattern
Central "Knowledge Base" database
├── Related: Projects (what uses this)
├── Related: Sources (where it came from)
├── Related: People (who knows this)
└── Views:
├── By Category (board)
├── By Status (table)
├── Recent (sorted list)
└── Gaps (filtered: needs review)
Synthesis Pages
Create pages that combine multiple sources:
- Linked database view of related items
- Narrative connecting the pieces
- Callouts for key insights
- Gap identification section
Cross-Reference Views
On any knowledge page, add:
- "Related Knowledge" linked database
- Filter: Related Concepts contains [this page]
- Shows everything connected to current topic
GRAI Field: Combination M→H achieved when AI synthesizes multiple Notion pages into unified content.
Goal: Convert Notion documentation into embodied capability through practice.
Notion Features:
Patterns:
Progressive Disclosure Learning
> 💡 **Question:** What are the four SECI phases?
<toggle>
**Answer:**
1. Socialization (Tacit → Tacit)
2. Externalization (Tacit → Explicit)
3. Combination (Explicit → Explicit)
4. Internalization (Explicit → Tacit)
</toggle>
Practice Checklists
## Practice: [Topic]
### Prerequisites
- [ ] Read: [Link to concept page]
- [ ] Understand: [Key principle]
### Exercise
- [ ] Step 1: [Action]
- [ ] Step 2: [Action]
- [ ] Step 3: [Action]
### Reflection
- What worked well?
- What was confusing?
- How would you apply this?
Annotated Examples
Real-world walkthrough with:
- Step-by-step with callouts explaining "why"
- Common mistakes highlighted
- Links to reference material
- Space for personal notes
GRAI Field: Internalization M→H achieved when AI generates practice exercises from Notion docs.
Organize SECI outputs using PARA structure:
Properties:
- Name (title)
- Status (Not Started/Active/Complete/On Hold)
- Deadline (date)
- Area (relation → Areas)
- Tasks (relation → Tasks)
- Notes (relation → Resources)
Properties:
- Name (title)
- Description (text)
- Projects (relation → Projects)
- Resources (relation → Resources)
- Owner (person)
Properties:
- Name (title)
- Type (Concept/Process/Reference/Template)
- Topics (multi-select)
- Related (relation → self)
- Source (URL)
- SECI Phase (select: S/E/C/I)
Filter: Status = "Archived" OR
Last Edited > 90 days ago
Sort: Last Edited (descending)
| PARA | Primary SECI Output |
|---|---|
| Projects | Internalization artifacts (applied knowledge) |
| Areas | Combination artifacts (organized domains) |
| Resources | Externalization artifacts (captured concepts) |
| Archives | Historical combination (preserved knowledge) |
Inbox database for quick capture:
Properties:
- Content (title)
- Source (URL/text)
- Captured (date, auto)
- Processed (checkbox)
- Destination (relation → Resources)
Quick capture template:
## Quick Capture
**Source:**
**Key insight:**
**Why it matters:**
**Process to:** [Projects/Areas/Resources/Archive]
Weekly review process:
Progressive summarization in Notion:
Layer 1: Full capture (original content)
Layer 2: Bold key passages
Layer 3: Highlight within bold
Layer 4: Executive summary at top
Use callouts for each layer:
> 📌 **Summary:** [Layer 4 - one sentence]
> 💡 **Key Points:** [Layer 3 - highlights]
<toggle>Full content with Layer 2 bolding...</toggle>
Output templates:
Hub & Spoke Pattern:
┌─── Tasks
│
Knowledge ───┼─── Projects
Hub │
└─── People
Master Database Pattern:
One "Everything" database with:
- Type property (Task/Note/Project/Resource)
- Filtered views for each type
- Single source of truth
Create multiple views of same data:
| View Type | Use For |
|---|---|
| Table | Bulk editing, data entry |
| Board | Workflow/status management |
| Calendar | Time-based planning |
| Gallery | Visual browsing |
| List | Simple scanning |
| Timeline | Project planning |
Use synced blocks for:
Create template buttons for:
This skill complements knowledge-manager's theoretical foundation:
| knowledge-manager | km-notion |
|---|---|
| SECI theory | Notion implementation |
| Ba contexts | Notion collaboration features |
| Knowledge assets | PARA organization |
| Phase transitions | CODE workflow |
Use knowledge-manager skills for "why" and this skill for "how in Notion".
For detailed patterns and templates:
references/para-implementation.md - Complete PARA setup in Notionreferences/database-patterns.md - Advanced database architecturesreferences/templates.md - Ready-to-use Notion templatesCreating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems. Create original algorithmic art rather than copying existing artists' work to avoid copyright violations.
Applies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply.
Create beautiful visual art in .png and .pdf documents using design philosophy. You should use this skill when the user asks to create a poster, piece of art, design, or other static piece. Create original visual designs, never copying existing artists' work to avoid copyright violations.