What are SECI and Ba contexts in this framework?

They are knowledge management models used to define how information is shared (Socialization), documented (Externalization), organized (Combination), and learned (Internalization).

How should I name my extension plugin?

The recommended convention is 'km-[tool-name]', such as 'km-notion' or 'km-obsidian', to ensure compatibility and discoverability.

What is the Knowledge Manager Extension Interface?

It is a framework for creating tool-specific plugins that apply the SECI and GRAI knowledge management models to specific software like Notion or Obsidian.

Which tools can I extend with this skill?

You can create extensions for any platform where knowledge is captured or stored, including Linear, Confluence, Jira, and local markdown vaults.

Does this skill work without the base knowledge-manager plugin?

This skill defines the interface for extensions; for full functionality, it requires the knowledge-manager plugin to provide the underlying theoretical foundation.

Knowledge Manager Extension Interface

Name: Knowledge Manager Extension Interface
Author: therealchrisrock

bytherealchrisrock

コンテンツ管理

Standardizes the creation and implementation of tool-specific knowledge management plugins for Claude Code.

概要

The Extension Interface skill provides a structured framework for developers to extend the base Knowledge Manager plugin to specific platforms like Notion, Obsidian, and Linear. It bridges the gap between theoretical knowledge models—such as SECI, GRAI, and Ba contexts—and practical, tool-specific implementations. By following this standardized interface, developers can create modular plugins that inherit core knowledge management principles while providing specialized workflows, automation scripts, and integration patterns for their favorite productivity tools.

主な機能

Guidance for implementing Ba contexts within third-party platforms
Blueprints for tool-specific agents and knowledge capture commands
Mapping of SECI phases to specific software features and operations
Standardized plugin structure for tool-specific knowledge adapters
0 GitHub stars
Composition model for combining theoretical foundations with practical integrations

ユースケース

Developing specialized knowledge capture and synthesis tools for Linear or Jira
Building a custom Claude Code plugin for Notion based on SECI principles
Integrating Obsidian workflows with the Knowledge Manager theoretical framework

概要

主な機能

Guidance for implementing Ba contexts within third-party platforms
Blueprints for tool-specific agents and knowledge capture commands
Mapping of SECI phases to specific software features and operations
Standardized plugin structure for tool-specific knowledge adapters
0 GitHub stars
Composition model for combining theoretical foundations with practical integrations

ユースケース

Developing specialized knowledge capture and synthesis tools for Linear or Jira
Building a custom Claude Code plugin for Notion based on SECI principles
Integrating Obsidian workflows with the Knowledge Manager theoretical framework