From knowledge-manager
This skill should be used when the user asks about "knowledge assets", "capturing knowledge", "organizational memory", "experiential knowledge", "conceptual knowledge", "systemic knowledge", "routine knowledge", "preserving insights", "knowledge artifacts", or needs guidance on what types of knowledge artifacts to create and maintain in AI-human collaboration.
How this skill is triggered — by the user, by Claude, or both
Slash command
/knowledge-manager:skills/knowledge-assetsThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Knowledge assets are organizational resources that can be used repeatedly to create value. Understanding knowledge asset types helps determine what artifacts to create and how to maintain them.
Knowledge assets are organizational resources that can be used repeatedly to create value. Understanding knowledge asset types helps determine what artifacts to create and how to maintain them.
Knowledge assets are the inputs, outputs, and moderators of the knowledge creation process. Unlike physical assets, knowledge assets:
Knowledge assets map to the SECI phases that create them:
| Asset Type | Created By | Nature | Example |
|---|---|---|---|
| Experiential | Socialization | Tacit, shared | Team intuitions, culture |
| Conceptual | Externalization | Explicit, articulated | Designs, specifications |
| Systemic | Combination | Explicit, systematized | Databases, documentation |
| Routine | Internalization | Tacit, embedded | Skills, operational know-how |
What they are: Shared tacit knowledge built through common experiences.
Characteristics:
Examples:
How to cultivate:
AI-Human cultivation:
What they are: Explicit knowledge articulated from tacit understanding.
Characteristics:
Examples:
How to cultivate:
AI-Human cultivation:
What they are: Systematized explicit knowledge combined and organized for reuse.
Characteristics:
Examples:
How to cultivate:
AI-Human cultivation:
What they are: Tacit know-how embedded in individuals and processes.
Characteristics:
Examples:
How to cultivate:
AI-Human cultivation:
Each asset type is created through its corresponding SECI phase:
Experiential ← Socialization (shared experiences)
Conceptual ← Externalization (articulation)
Systemic ← Combination (organization)
Routine ← Internalization (practice)
Assets require different maintenance approaches:
| Asset Type | Maintenance Need | Approach |
|---|---|---|
| Experiential | Keep team connected | Regular interaction, culture activities |
| Conceptual | Keep current and accurate | Review cycles, update triggers |
| Systemic | Keep organized and accessible | Curation, pruning, search optimization |
| Routine | Keep skills sharp | Practice, refresher training |
Knowledge assets become less valuable when:
Deprecation signals:
Organizations need all four types in balance:
Over-indexed on Experiential:
Over-indexed on Conceptual:
Over-indexed on Systemic:
Over-indexed on Routine:
Healthy balance:
Experiential → Conceptual → Systemic → Routine
↑ │
└────────────────────────────────────┘
| Task | Primary Asset | AI Role |
|---|---|---|
| New feature exploration | Experiential | Build shared context |
| Specification writing | Conceptual | Structure and articulate |
| Documentation building | Systemic | Synthesize and organize |
| Skill development | Routine | Generate practice, give feedback |
Pattern 1: Experience → Documentation
1. Collaborative exploration (Experiential)
2. Articulate insights (Conceptual)
3. Integrate into knowledge base (Systemic)
Pattern 2: Documentation → Capability
1. Read existing docs (Systemic)
2. Practice with AI support (Routine)
3. Apply in real context
Pattern 3: Capture Before Loss
1. Identify tacit knowledge at risk
2. Conduct articulation sessions (Experiential → Conceptual)
3. Systematize for longevity (Conceptual → Systemic)
For detailed cultivation strategies:
references/asset-cultivation.md - Comprehensive strategies for growing each asset typenpx claudepluginhub therealchrisrock/bashoCapture and structure institutional knowledge before it is lost. Activate for: institutional knowledge, knowledge capture, knowledge transfer, knowledge base article, knowledge management, preserve knowledge, what do they know, departing employee knowledge, exit knowledge, succession knowledge, tacit knowledge, undocumented knowledge, before they leave, knowledge interview, knowledge extraction, document what we know, knowledge at risk, knowledge map. NOT for: policy lookup or FAQ queries (use policy-lookup), onboarding plans (use onboarding), offboarding checklists (use offboard).
Processes external resources like articles, blogs, and papers into stored knowledge via quality evaluation, curation, tidying, and routing to storage or codebase application. Use for capturing session knowledge into memory structures.
Captures insights as markdown files, searches prior learnings, and promotes patterns to CLAUDE.md using tiered backends (local, qmd, agent-fs) for knowledge across projects.