How does this skill help prevent documentation rot?

It provides specific maintenance triggers and deprecation signals for different asset types, helping you identify when documentation becomes stale, contradictory, or no longer useful.

What is the SECI model used in this skill?

SECI stands for Socialization, Externalization, Combination, and Internalization. It is a framework for understanding how knowledge moves from individual experience to organizational systems.

What are knowledge assets in the context of Claude Code?

Knowledge assets are organizational resources—ranging from team intuitions to formal documentation—that Claude helps you identify, capture, and maintain to create repeatable value during development.

Can this skill help with team onboarding?

Yes, it helps teams identify 'Routine' and 'Experiential' assets—the tacit knowledge often missing from standard docs—to create more effective learning paths for new members.

Knowledge Assets

Name: Knowledge Assets
Author: therealchrisrock

bytherealchrisrock

Gestión de Contenido

Categorizes and cultivates organizational knowledge to build robust memory and efficient AI-human collaboration workflows.

Acerca de

The Knowledge Assets skill provides a structured framework for identifying, capturing, and maintaining organizational knowledge across four key dimensions: experiential, conceptual, systemic, and routine. Based on the SECI model of knowledge creation, it helps teams bridge the gap between tacit 'tribal knowledge' and explicit documentation. By applying this skill, developers and teams can ensure that insights gained during the development process are preserved, organized into reusable artifacts, and evolved to prevent knowledge rot, ultimately creating a balanced and searchable knowledge portfolio.

Características Principales

0 GitHub stars
Categorizes knowledge into Experiential, Conceptual, Systemic, and Routine types
Balances knowledge portfolios to prevent information silos and documentation overload
Suggests specific maintenance strategies for different types of knowledge artifacts
Provides frameworks for converting tacit team intuition into explicit documentation
Identifies deprecation signals to prune outdated or contradictory information

Casos de Uso

Capturing architectural design rationale as conceptual assets during high-level planning sessions
Developing a comprehensive onboarding guide by identifying required routine and experiential skills
Organizing fragmented project notes and chat logs into a searchable systemic knowledge base

Acerca de

Características Principales

0 GitHub stars
Categorizes knowledge into Experiential, Conceptual, Systemic, and Routine types
Balances knowledge portfolios to prevent information silos and documentation overload
Suggests specific maintenance strategies for different types of knowledge artifacts
Provides frameworks for converting tacit team intuition into explicit documentation
Identifies deprecation signals to prune outdated or contradictory information

Casos de Uso

Capturing architectural design rationale as conceptual assets during high-level planning sessions
Developing a comprehensive onboarding guide by identifying required routine and experiential skills
Organizing fragmented project notes and chat logs into a searchable systemic knowledge base