This skill should be used when the user asks to "extend knowledge-manager", "create a knowledge management plugin for Notion/Obsidian/Linear", "implement SECI for a specific tool", "build a knowledge adapter", or wants to create a tool-specific plugin that inherits from knowledge-manager's theoretical foundation.
/plugin marketplace add therealchrisrock/basho/plugin install knowledge-manager@baThis skill inherits all available tools. When active, it can use any tool Claude has access to.
examples/hypothetical-notion-extension.mdreferences/extension-patterns.mdThis skill defines how tool-specific plugins can extend the knowledge-manager foundation. Extension plugins implement the theoretical framework for specific tools and platforms.
Knowledge-manager provides:
Extension plugins provide:
Extensions work through skill composition—when both plugins are installed, their skills combine:
┌─────────────────────────────────────────────────────┐
│ knowledge-manager │
│ ┌───────────┐ ┌───────────┐ ┌────────────────┐ │
│ │ seci-grai │ │ ba-context│ │ knowledge-asset│ │
│ └───────────┘ └───────────┘ └────────────────┘ │
└─────────────────────────────────────────────────────┘
+
┌─────────────────────────────────────────────────────┐
│ km-notion (extension) │
│ ┌────────────────┐ ┌──────────────────────────┐ │
│ │ notion-patterns│ │ notion-externalization │ │
│ └────────────────┘ └──────────────────────────┘ │
└─────────────────────────────────────────────────────┘
=
┌─────────────────────────────────────────────────────┐
│ Combined Context │
│ Theory + Notion-specific implementation │
└─────────────────────────────────────────────────────┘
km-[tool-name]/
├── .claude-plugin/
│ └── plugin.json
├── skills/
│ └── [tool]-knowledge/
│ ├── SKILL.md
│ └── references/
├── agents/
│ └── [tool]-externalizer.md (optional)
├── commands/
│ └── externalize.md (optional)
└── README.md
{
"name": "km-[tool-name]",
"version": "0.1.0",
"description": "Knowledge management for [Tool] - extends knowledge-manager",
"keywords": [
"knowledge-management",
"seci-model",
"[tool-name]"
],
"dependencies": {
"knowledge-manager": ">=0.1.0"
}
}
Note: The dependencies field documents the relationship; actual dependency management is handled by installation order.
Map each SECI phase to tool operations:
| SECI Phase | Extension Must Define |
|---|---|
| Socialization | How to share tacit knowledge using [tool] |
| Externalization | How to capture explicit knowledge in [tool] |
| Combination | How to synthesize/organize in [tool] |
| Internalization | How to learn from [tool] content |
Describe how to create each Ba type within the tool:
## [Tool] as Originating Ba
[How to use tool for shared experience]
## [Tool] as Dialoguing Ba
[How to use tool for articulation]
## [Tool] as Systemizing Ba
[How to use tool for organization]
## [Tool] as Exercising Ba
[How to use tool for practice]
Create agents for common tool operations:
---
name: [tool]-externalizer
description: Use this agent when the user wants to capture
knowledge in [Tool], create documentation in [Tool], or
externalize tacit understanding using [Tool] features.
---
[System prompt for tool-specific externalization]
Create commands for common workflows:
---
name: externalize
description: Capture tacit knowledge in [Tool]
argument-hint: <topic-to-document>
---
[Instructions for tool-specific externalization workflow]
km-[tool-name]
Examples:
km-notionkm-obsidiankm-linearkm-confluence[tool]-knowledge
[tool]-[phase] (if phase-specific skills)
Examples:
notion-knowledgeobsidian-externalizationlinear-combinationUse the tool name as namespace:
/notion:externalize
/obsidian:combine
/linear:capture
---
name: [Tool] Knowledge Patterns
description: This skill should be used when the user asks about
"[Tool] for knowledge management", "SECI in [Tool]",
"documenting in [Tool]", "organizing knowledge in [Tool]",
or needs to apply knowledge management principles using [Tool].
version: 0.1.0
---
# [Tool] Knowledge Management Patterns
This skill extends knowledge-manager with [Tool]-specific patterns.
It maps SECI phases and Ba contexts to [Tool] features.
## Prerequisites
- knowledge-manager plugin installed (provides theoretical foundation)
- [Tool] access configured
- [Any MCP servers or integrations]
## [Tool] for SECI Phases
### Socialization with [Tool]
**Tool features used:** [List relevant features]
**Patterns:**
1. [Pattern name]: [Description]
2. [Pattern name]: [Description]
**Example workflow:**
[Step-by-step for socialization in tool]
### Externalization with [Tool]
**Tool features used:** [List relevant features]
**Patterns:**
1. [Pattern name]: [Description]
2. [Pattern name]: [Description]
**Example workflow:**
[Step-by-step for externalization in tool]
### Combination with [Tool]
**Tool features used:** [List relevant features]
**Patterns:**
1. [Pattern name]: [Description]
2. [Pattern name]: [Description]
**Example workflow:**
[Step-by-step for combination in tool]
### Internalization with [Tool]
**Tool features used:** [List relevant features]
**Patterns:**
1. [Pattern name]: [Description]
2. [Pattern name]: [Description]
**Example workflow:**
[Step-by-step for internalization in tool]
## [Tool] as Ba
[Description of how tool serves each Ba type]
## Integration with knowledge-manager
This skill complements:
- **seci-grai**: For theoretical foundation
- **ba-contexts**: For context selection
- **knowledge-assets**: For asset type identification
Use knowledge-manager skills for "why" and this skill for "how in [Tool]".
See examples/hypothetical-notion-extension.md for a complete example of what a Notion extension might look like.
km-[tool-name]For detailed extension patterns:
references/extension-patterns.md - Complete implementation patternsWorking extension examples:
examples/hypothetical-notion-extension.md - Full example extensionCreating 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.