@gabrywu/knowledge-bank 0.1.2-alpha.227 → 0.1.2-alpha.252

package/README.md

@@ -22,8 +22,10 @@ Knowledge Bank is a lightweight Claude Code plugin that transforms your developm
 ### Quick Setup
 
 ```bash
-# Clone the repository
+# Install Knowledge Bank globally
 npm install -g @gabrywu/knowledge-bank --registry https://registry.npmjs.org
+# For alpha/beta versions, use:
+npm install -g @gabrywu/knowledge-bank@alpha --registry https://registry.npmjs.org
 
 # Install the Knowledge Bank plugin
 knowledge-bank install

package/dist/claude-marketplace/.claude-plugin/marketplace.json

@@ -9,7 +9,7 @@
       "name": "core",
       "source": "./core",
       "description": "Core plugins for knowledge bank",
-      "version": "0.1.2-alpha.227",
+      "version": "0.1.2-alpha.252",
       "author": {
         "name": "garbywu",
         "email": "gabrywu@apache.org"
@@ -18,6 +18,6 @@
   ],
   "metadata": {
     "description": "A marketplace for knowledge bank plugins by gabrywu",
-    "version": "0.1.2-alpha.227"
+    "version": "0.1.2-alpha.252"
   }
 }

package/dist/claude-marketplace/core/.claude-plugin/plugin.json

@@ -1,7 +1,7 @@
 {
   "name": "core",
   "description": "Core plugins for knowledge bank",
-  "version": "0.1.2-alpha.227",
+  "version": "0.1.2-alpha.252",
   "author": {
     "name": "garbywu",
     "email": "gabrywu@apache.org"

package/dist/claude-marketplace/core/skills/KNOWLEDGE-DEFINITION.md

@@ -18,11 +18,22 @@ Every knowledge item MUST contain these essential elements:
 ### Knowledge Qualification Criteria
 
 Knowledge MUST meet ALL of the following requirements:
-- **Specific**: Tied to concrete files, patterns, or decisions in this project
+- **Relevant**: Tied to concrete files/patterns in this project OR applicable to personal development principles
 - **Valuable**: Saves significant time/effort for future development work
 - **Non-obvious**: Not immediately apparent from reading code alone
 - **Actionable**: Provides clear guidance for developers
 
+## Knowledge Scope
+
+Knowledge items are scoped based on their applicability:
+
+- **Project Scope** (`project`): Knowledge that is specific to the current codebase, its architecture, unique patterns, and project-specific configurations.
+- **Personal Scope** (`personal`): Knowledge that is:
+    - **General/Universal**: Broad technical insights or best practices.
+    - **Personal Preference**: Individual development styles, coding principles, or favored patterns.
+    - **Cross-Project**: Logic or workflows that can be reused across different projects.
+    - **Philosophical**: High-level development principles and decision-making frameworks.
+
 ## Knowledge Categories
 
 Knowledge items are classified into the following categories:
@@ -41,7 +52,7 @@ Automatically detect and flag knowledge for SIGNIFICANT technical insights:
 - Focus on substantial technical discoveries and problem-solving
 - Capture insights with clear developmental value
 - Balance quality and comprehensiveness
-- Prioritize project-specific, actionable knowledge
+- Prioritize project-specific or universally valuable personal knowledge
 
 ### POSITIVE Triggers - Detect Knowledge When:
 - **Problem-Solving**: Solving bugs/issues requiring investigation
@@ -61,7 +72,7 @@ Automatically detect and flag knowledge for SIGNIFICANT technical insights:
 Apply this evaluation for every potential knowledge item:
 1. **Effort Assessment**: Did this require meaningful investigation or problem-solving?
 2. **Future Impact**: Will this knowledge help future development work?
-3. **Project Specificity**: Is this tied to this project's unique characteristics?
+3. **Applicability**: Is this tied to this project's unique characteristics OR a valuable personal principle?
 4. **Non-obviousness**: Would this insight be difficult to derive from code alone?
 
 **Result**: If 3+ checks pass → FLAG for knowledge capture.

package/dist/claude-marketplace/core/skills/knowledge.add/skill.md

@@ -3,7 +3,7 @@ name: knowledge.add
 description: Add a new knowledge item to the knowledge base with automatic content generation from user instruction
 disable-model-invocation: false
 user-invocable: true
-allowed-tools: knowledge_create, knowledge_search, knowledge_list, Write(*/tmp/*), read
+allowed-tools: knowledge_create, knowledge_search, knowledge_list, Write, Read, Bash
 context: fork
 agent: general-purpose
 ---
@@ -14,7 +14,7 @@ Add a new knowledge item to the knowledge base with automatic content generation
 
 ## Knowledge Definition Standards
 
-**IMPORTANT:** Refer to [KNOWLEDGE-DEFINITION.md](../KNOWLEDGE-DEFINITION.md) for:
+**IMPORTANT:** Refer to KNOWLEDGE-DEFINITION.md for:
 - Knowledge categories and types
 - Quality standards and criteria
 - Content structure requirements

package/dist/claude-marketplace/core/skills/knowledge.collect/SKILL.md

@@ -3,7 +3,7 @@ name: knowledge.collect
 description: Intelligent knowledge management with CRUD operations and lifecycle management
 disable-model-invocation: false
 user-invocable: true
-allowed-tools: knowledge_create, knowledge_get, knowledge_update, knowledge_delete, knowledge_list, knowledge_search, knowledge_update_status, knowledge_stats, Write(**/.knowledge-bank/tmp/*.json), Bash
+allowed-tools: knowledge_create, knowledge_get, knowledge_update, knowledge_delete, knowledge_list, knowledge_search, knowledge_update_status, knowledge_stats, Write, Read, Bash
 context: fork
 agent: general-purpose
 ---
@@ -22,12 +22,12 @@ Intelligent knowledge lifecycle management system that processes detected knowle
 ## File Parameter Configuration
 
 The MCP tools support file operations through `to` and `from` parameters:
-- **Filename Only**: Both `to` and `from` parameters accept only filenames (e.g., `knowledge-data.json`, `search-results.md`)
+- **Filename Only**: Both `to` and `from` parameters accept only filenames (e.g., `knowledge-data.json`)
 - **Path Resolution**: The MCP tools automatically resolve the complete file paths and return them in responses
 
 ## Knowledge Definition Standards
 
-**IMPORTANT:** Refer to [KNOWLEDGE-DEFINITION.md](../KNOWLEDGE-DEFINITION.md) for:
+**IMPORTANT:** Refer to KNOWLEDGE-DEFINITION.md for:
 - Knowledge categories and types
 - Detection criteria and quality standards
 - Core knowledge elements and qualification criteria
@@ -79,7 +79,7 @@ Reason: [Brief explanation - e.g., "Routine operations without project-specific
 
 ## 2. Duplicate Detection & Conflict Resolution
 
-Before creating new knowledge, search for existing similar items using the `knowledge_search` tool from the `knowledge-bank-management` MCP server. Use the `to` parameter to save search results to a file for analysis. Note: The `to` parameter only contains the filename (e.g., `{knowledge title}.json` or `{knowledge title}.md`), not the full path. The MCP tool will return the complete file path after saving.
+Before creating new knowledge, search for existing similar items using the `knowledge_search` tool from the `knowledge-bank-management` MCP server. Use the `to` parameter to save search results to a file for analysis. Note: The `to` parameter only contains the filename (e.g., `{knowledge title}.json`), not the full path. The MCP tool will return the complete file path after saving.
 
 **Decision Logic:**
 - **EXACT MATCH**: Update existing knowledge
@@ -127,7 +127,7 @@ To ensure reliability and handle large content, always use file-based operations
    - Use `knowledge_update` with the `from` parameter (filename only, e.g., `merged-knowledge.json`).
 
 ## Update Existing Knowledge
-1. Use `knowledge_get` with the `to` parameter (filename only, e.g., `existing-knowledge.md`) to retrieve current data into a markdown/JSON file in !`npx knowledge-bank config -t`.
+1. Use `knowledge_get` with the `to` parameter (filename only, e.g., `existing-knowledge.json`) to retrieve current data into a markdown/JSON file in !`npx knowledge-bank config -t`.
 2. Merge new insights with the retrieved content.
 3. Write the merged data to a local JSON file in !`npx knowledge-bank config -t`.
 4. Use `knowledge_update` with the `from` parameter (filename only, e.g., `updated-knowledge.json`).

package/dist/claude-marketplace/core/skills/knowledge.delete/skill.md

@@ -3,7 +3,7 @@ name: knowledge.delete
 description: Delete a specific knowledge item from the knowledge base
 disable-model-invocation: false
 user-invocable: true
-allowed-tools: knowledge_delete, knowledge_get, knowledge_search
+allowed-tools: knowledge_delete, knowledge_get, knowledge_search, Write, Read, Bash
 context: fork
 agent: general-purpose
 ---

package/dist/claude-marketplace/core/skills/knowledge.enhance/SKILL.md

@@ -3,7 +3,7 @@ name: knowledge.enhance
 description: Search and inject relevant knowledge into current session based on user input
 disable-model-invocation: false
 user-invocable: true
-allowed-tools: knowledge_search, knowledge_list, knowledge_get, Write(*/tmp/*), Bash
+allowed-tools: knowledge_search, knowledge_list, knowledge_get, Read, Write, Bash
 context: fork
 agent: general-purpose
 ---
@@ -22,12 +22,12 @@ Intelligent knowledge retrieval system that searches for relevant knowledge item
 ## File Parameter Configuration
 
 The MCP tools support file operations through the `to` parameter:
-- **Filename Only**: The `to` parameter accepts only filenames (e.g., `knowledge-search.json`, `relevant-context.md`)
+- **Filename Only**: The `to` parameter accepts only filenames (e.g., `knowledge-search.json`)
 - **Path Resolution**: The MCP tools automatically resolve the complete file paths (specifically within the `tmp` directory) and return them in responses
 
 ## Knowledge Definition Standards
 
-**IMPORTANT:** Refer to [KNOWLEDGE-DEFINITION.md](../KNOWLEDGE-DEFINITION.md) for:
+**IMPORTANT:** Refer to KNOWLEDGE-DEFINITION.md for:
 - Knowledge categories and types
 - Search guidance and relevance criteria
 - Quality standards for knowledge retrieval
@@ -70,13 +70,21 @@ Use `knowledge_list` for type-specific knowledge retrieval with filters.
 - **Low Relevance**: Tangential knowledge for broader context
 
 ### Context Injection Format
-Retrieved knowledge should be saved to a temporary file using the `to` parameter in `knowledge_search` or `knowledge_list`. Use filename only (e.g., `{knowledge title}.md`) - the MCP tool will handle the complete path (resolving to the `tmp` directory) and return it. Then, present a summary and the file path:
+Retrieved knowledge should be saved to a temporary file using the `to` parameter in `knowledge_search` or `knowledge_list`. Use filename only (e.g., `{knowledge title}.json`) - the MCP tool will handle the complete path (resolving to the `tmp` directory) and return it. 
+
+**Crucial:** After the MCP tool returns the `file_path`, you MUST use the `Read` tool to read the contents of that file.
+
+Then, present the retrieved knowledge in the following format so it can be injected into the main session:
 
 ```
 🔍 RELEVANT KNOWLEDGE FOUND
 
 **Summary:** [Brief summary of the retrieved knowledge]
-**Storage:** Detailed knowledge items are stored in: [file_path]
+**Storage:** [file_path]
+
+<knowledge_content>
+[Insert the FULL content of the file you just read here]
+</knowledge_content>
 ```
 
 **Note:** The `to` parameter only contains the filename, not the full path. The MCP tool automatically resolves the complete file path and returns it after saving.

package/dist/claude-marketplace/core/skills/knowledge.import/skill.md

@@ -3,7 +3,7 @@ name: knowledge.import
 description: Import knowledge items from files or external sources
 disable-model-invocation: false
 user-invocable: true
-allowed-tools: knowledge_create, read, glob, Write(*/tmp/*)
+allowed-tools: knowledge_create, Write, Read, Bash
 context: fork
 agent: general-purpose
 ---
@@ -14,7 +14,7 @@ Import knowledge items from external files (JSON, Markdown) or documentation dir
 
 ## Knowledge Definition Standards
 
-**IMPORTANT:** Refer to [KNOWLEDGE-DEFINITION.md](../KNOWLEDGE-DEFINITION.md) for:
+**IMPORTANT:** Refer to KNOWLEDGE-DEFINITION.md for:
 - Knowledge categories and types
 - Validation criteria and quality standards
 - Import format requirements

package/dist/claude-marketplace/core/skills/knowledge.init/skill.md

@@ -3,7 +3,7 @@ name: knowledge.init
 description: Initialize a comprehensive knowledge base by analyzing the entire codebase
 disable-model-invocation: false
 user-invocable: true
-allowed-tools: knowledge_create, knowledge_list, glob, read, Write(*/tmp/*)
+allowed-tools: knowledge_create, knowledge_list, Write, Read, Bash
 context: fork
 agent: general-purpose
 ---
@@ -14,7 +14,7 @@ Analyzes the codebase structure, patterns, and key components to create foundati
 
 ## Knowledge Definition Standards
 
-**IMPORTANT:** Refer to [KNOWLEDGE-DEFINITION.md](../KNOWLEDGE-DEFINITION.md) for:
+**IMPORTANT:** Refer to KNOWLEDGE-DEFINITION.md for:
 - Knowledge categories and types
 - Quality standards for foundational knowledge
 - Comprehensive coverage criteria

package/dist/claude-marketplace/core/skills/knowledge.save/skill.md

@@ -3,7 +3,7 @@ name: knowledge.save
 description: Manually save knowledge from current conversation session to the knowledge base
 disable-model-invocation: false
 user-invocable: true
-allowed-tools: knowledge_create, knowledge_search, knowledge_update, knowledge_list, Write(*/tmp/*)
+allowed-tools: knowledge_create, knowledge_search, knowledge_update, knowledge_list, Write, Read, Bash
 context: fork
 agent: general-purpose
 ---
@@ -14,7 +14,7 @@ Analyzes the current conversation session to identify and save valuable knowledg
 
 ## Knowledge Definition Standards
 
-**IMPORTANT:** Refer to [KNOWLEDGE-DEFINITION.md](../KNOWLEDGE-DEFINITION.md) for:
+**IMPORTANT:** Refer to KNOWLEDGE-DEFINITION.md for:
 - Knowledge categories and types
 - Quality criteria for valuable knowledge
 - Standards for extracting insights from conversations

package/dist/claude-marketplace/core/skills/knowledge.status/skill.md

@@ -3,7 +3,7 @@ name: knowledge.status
 description: Show knowledge collection status and statistics
 disable-model-invocation: false
 user-invocable: true
-allowed-tools: knowledge_stats, knowledge_list
+allowed-tools: knowledge_stats, knowledge_list, Write, Read, Bash
 context: fork
 agent: general-purpose
 ---

package/dist/claude-marketplace/core/skills/knowledge.update/skill.md

@@ -3,7 +3,7 @@ name: knowledge.update
 description: Update existing knowledge items or create new ones based on current codebase analysis
 disable-model-invocation: false
 user-invocable: true
-allowed-tools: knowledge_update, knowledge_list, knowledge_search, knowledge_create, glob, read, Write(*/tmp/*)
+allowed-tools: knowledge_update, knowledge_list, knowledge_search, knowledge_create, Write, Read, Bash
 context: fork
 agent: general-purpose
 ---
@@ -14,7 +14,7 @@ Synchronizes the knowledge base with the current state of the codebase by updati
 
 ## Knowledge Definition Standards
 
-**IMPORTANT:** Refer to [KNOWLEDGE-DEFINITION.md](../KNOWLEDGE-DEFINITION.md) for:
+**IMPORTANT:** Refer to KNOWLEDGE-DEFINITION.md for:
 - Knowledge categories and types
 - Quality standards for updates
 - Criteria for creating new knowledge items