thanh-kit 2.5.0

package/templates/discord/skills/auto-intent-router/SKILL.md

@@ -0,0 +1,195 @@
+---
+name: auto-intent-router
+description: Automatically detects user intent and routes to appropriate skill without manual commands
+user-invocable: false
+disable-model-invocation: false
+metadata: {"openclaw": {"always": true, "priority": 1}}
+---
+
+# Auto Intent Router
+
+## Purpose
+
+This skill runs on EVERY message to detect user intent and automatically activate the appropriate skill. Users don't need to type commands like `/plan` or `/brainstorm` - the bot understands natural language.
+
+## Priority
+
+This skill has highest priority (runs first) to route messages before other processing.
+
+## Intent Detection Matrix
+
+| Intent | Keywords/Patterns | Activated Skill |
+|--------|-------------------|-----------------|
+| **PLANNING** | plan, design, architect, implement, create, build feature | `planning`, `plan-fast`, `plan-hard` |
+| **BRAINSTORMING** | brainstorm, ideas, options, alternatives, think about, explore | `brainstorm` |
+| **DEBUGGING** | fix, debug, error, broken, bug, issue, not working, crash | `debugging`, `fix-fast`, `fix-hard` |
+| **CODE REVIEW** | review, check my code, look at this, audit, examine | `code-review` |
+| **CODING** | code, implement, write, develop, create function | `code`, `cook` |
+| **TESTING** | test, unit test, spec, coverage, jest, vitest | `testing` |
+| **DATABASE** | database, schema, migration, query, sql, table | `database` |
+| **API DESIGN** | api, endpoint, rest, graphql, route | `api-design` |
+| **DOCUMENTATION** | document, docs, readme, explain, describe | `documentation` |
+| **DEPLOYMENT** | deploy, release, staging, production, ci/cd | `deployment` |
+| **TRAINING** | train, learn, teach, add knowledge, remember | `train-prompt` |
+| **SCOUTING** | find, search, where is, locate, explore codebase | `scout` |
+
+## Detection Algorithm
+
+```
+1. EXTRACT keywords from user message
+2. MATCH against intent patterns
+3. CALCULATE confidence score for each intent
+4. IF confidence > 0.7:
+     ACTIVATE corresponding skill
+   ELSE IF multiple intents detected:
+     ASK user for clarification
+   ELSE:
+     PROCEED with general response
+```
+
+## Confidence Scoring
+
+```
+score = (keyword_matches * 0.4) + (pattern_matches * 0.3) + (context_relevance * 0.3)
+
+- keyword_matches: Number of intent keywords found
+- pattern_matches: Regex patterns matched
+- context_relevance: Based on conversation history
+```
+
+## Workflow
+
+### Step 1: Parse Message
+
+Extract:
+- Primary keywords
+- Question type (how, what, why, can you)
+- Code references (file paths, function names)
+- URLs or links
+
+### Step 2: Intent Classification
+
+For each potential intent:
+1. Count keyword matches
+2. Check pattern matches
+3. Consider conversation context
+4. Calculate confidence score
+
+### Step 3: Route or Clarify
+
+**High Confidence (>0.7):**
+```
+Silently activate the matched skill.
+User sees natural response, not "Activating planning skill..."
+```
+
+**Medium Confidence (0.4-0.7):**
+```
+"I think you want to [intent]. Should I:
+A) Create a plan for this
+B) Brainstorm alternatives first
+C) Just help directly"
+```
+
+**Low Confidence (<0.4):**
+```
+Respond naturally without special skill activation.
+```
+
+## Examples
+
+### Example 1: Planning Intent
+```
+User: "I need to add user authentication to the app"
+
+[Intent Detection]
+Keywords: "add", "authentication", "app"
+Pattern: "I need to" + feature description
+Confidence: PLANNING = 0.85
+
+[Action]
+Activate: planning skill
+Response: "I'll help you plan the authentication system..."
+```
+
+### Example 2: Debugging Intent
+```
+User: "The login button isn't working anymore"
+
+[Intent Detection]
+Keywords: "isn't working"
+Pattern: [component] + "not working"
+Confidence: DEBUGGING = 0.9
+
+[Action]
+Activate: debugging skill
+Response: "Let me investigate the login button issue..."
+```
+
+### Example 3: Ambiguous Intent
+```
+User: "Can you help with the API?"
+
+[Intent Detection]
+Keywords: "API"
+Confidence: API_DESIGN = 0.5, DEBUGGING = 0.4
+
+[Action]
+Clarify: "I can help with the API. Do you want to:
+A) Design new endpoints
+B) Fix an existing issue
+C) Review the current implementation"
+```
+
+### Example 4: Training Intent
+```
+User: "Learn this documentation: https://docs.stripe.com/api"
+
+[Intent Detection]
+Keywords: "learn", URL present
+Confidence: TRAINING = 0.95
+
+[Action]
+Activate: train-prompt skill
+Response: "I'll learn from the Stripe API documentation..."
+```
+
+## Context Awareness
+
+The router considers conversation history:
+
+- If previous message was about planning → lower threshold for planning-related follow-ups
+- If user just shared code → debugging/review more likely
+- If discussing architecture → planning/design more likely
+
+## Override Behavior
+
+Users can still use explicit commands to override:
+- `/plan` - Force planning mode
+- `/brainstorm` - Force brainstorming mode
+- `/fix` - Force debugging mode
+
+Explicit commands bypass intent detection.
+
+## Configuration
+
+Skills can declare their trigger conditions in their SKILL.md frontmatter:
+
+```yaml
+metadata: {
+  "openclaw": {
+    "triggers": {
+      "keywords": ["plan", "design", "architect"],
+      "patterns": ["how should I", "best way to"],
+      "confidence_boost": 0.1
+    }
+  }
+}
+```
+
+## Performance Notes
+
+- Intent detection runs in <50ms
+- Only loads full skill content after routing
+- Caches recent intent classifications
+- Batches multiple skill reads when needed

package/templates/discord/skills/train-prompt/SKILL.md

@@ -0,0 +1,306 @@
+---
+name: train-prompt
+description: Add new documents, links, or knowledge to train and expand bot capabilities
+user-invocable: true
+disable-model-invocation: false
+metadata: {"openclaw": {"always": true}}
+---
+
+# Train Prompt - Auto Learning System
+
+## Trigger Conditions
+
+Activate when user:
+- Says: "train", "learn", "add knowledge", "teach you"
+- Provides: URL, document link, file path
+- Requests: "remember this", "add this to your knowledge"
+- Commands: "/train", "/learn", "/add-doc"
+
+## Input Types Supported
+
+1. **URLs** - Web pages, documentation, articles
+2. **Files** - Markdown, PDF, text files
+3. **Inline content** - Direct text/instructions
+4. **GitHub repos** - Repository documentation
+
+## Workflow
+
+### Step 1: Detect Input Type
+
+```
+IF input contains URL → fetch_and_process_url
+IF input contains file path → read_and_process_file
+IF input is inline text → process_inline_content
+IF input is GitHub URL → clone_and_extract_docs
+```
+
+### Step 2: Process Content
+
+#### For URLs:
+1. Fetch URL content using `web_fetch` tool
+2. Extract main content (remove nav, ads, etc.)
+3. Convert to markdown format
+4. Identify key concepts and patterns
+
+#### For Files:
+1. Read file content
+2. Parse based on file type (md, pdf, txt)
+3. Extract structured information
+
+#### For Inline Content:
+1. Parse user's instructions
+2. Identify intent and knowledge type
+3. Structure as skill or reference
+
+### Step 3: Generate Skill/Reference
+
+Based on content type, create:
+
+**A) New Skill** (if content describes a workflow/process):
+```
+skills/<skill-name>/
+├── SKILL.md          ← Generated skill definition
+└── references/
+    └── source.md     ← Original content
+```
+
+**B) Reference Document** (if content is documentation):
+```
+skills/<parent-skill>/
+└── references/
+    └── <doc-name>.md ← Extracted knowledge
+```
+
+**C) Bootstrap Update** (if content is identity/rules):
+```
+Append to SOUL.md or AGENTS.md
+```
+
+### Step 4: Skill Generation Template
+
+For new skills, generate:
+
+```yaml
+---
+name: {extracted-name}
+description: {one-line-summary}
+user-invocable: true
+metadata: {"openclaw": {"always": true, "source": "{original-url-or-path}"}}
+---
+
+# {Skill Title}
+
+## Purpose
+{extracted-purpose}
+
+## Trigger Conditions
+Activate when user mentions:
+{extracted-keywords}
+
+## Workflow
+{extracted-steps}
+
+## Reference
+Source: {original-source}
+Added: {timestamp}
+```
+
+### Step 5: Confirm & Save
+
+1. Show preview of generated skill/reference
+2. Ask user to confirm or edit
+3. Save to appropriate location
+4. Update skill index
+
+## Commands
+
+### /train <url>
+Fetch and learn from a URL.
+
+Example:
+```
+/train https://docs.example.com/api-guide
+```
+
+### /train:file <path>
+Learn from a local file.
+
+Example:
+```
+/train:file ./docs/coding-standards.md
+```
+
+### /train:inline
+Learn from inline content.
+
+Example:
+```
+/train:inline
+When handling API errors:
+1. Log the error with context
+2. Return appropriate HTTP status
+3. Never expose internal details
+```
+
+### /train:github <repo-url>
+Extract knowledge from GitHub repository.
+
+Example:
+```
+/train:github https://github.com/example/repo
+```
+
+### /train:list
+Show all trained knowledge sources.
+
+### /train:remove <skill-name>
+Remove a trained skill.
+
+## Output Format
+
+After training:
+
+```markdown
+## Training Complete
+
+**Source:** {url-or-path}
+**Type:** {skill|reference|bootstrap}
+**Location:** {saved-path}
+
+### Generated Knowledge
+
+**Skill:** {skill-name}
+**Description:** {description}
+**Triggers:** {keyword-list}
+
+### Next Steps
+- Test with: "{example-trigger}"
+- Edit at: {file-path}
+- View all: /train:list
+```
+
+## Storage Structure
+
+```
+.discord/
+├── skills/
+│   ├── trained/                    ← Auto-generated skills
+│   │   ├── api-docs-example/
+│   │   │   ├── SKILL.md
+│   │   │   └── references/
+│   │   │       └── source.md
+│   │   └── coding-standards/
+│   │       └── SKILL.md
+│   └── train-prompt/               ← This skill
+│       └── SKILL.md
+├── knowledge/                      ← Reference documents
+│   ├── sources.json               ← Index of all sources
+│   └── docs/
+│       ├── doc-001.md
+│       └── doc-002.md
+└── SOUL.md                        ← Updated with rules
+```
+
+## Knowledge Index (sources.json)
+
+```json
+{
+  "sources": [
+    {
+      "id": "src-001",
+      "type": "url",
+      "source": "https://docs.example.com/api",
+      "skill": "api-docs-example",
+      "added": "2024-01-15T10:30:00Z",
+      "keywords": ["api", "rest", "endpoints"]
+    }
+  ],
+  "stats": {
+    "total_skills": 5,
+    "total_references": 12,
+    "last_updated": "2024-01-15T10:30:00Z"
+  }
+}
+```
+
+## Advanced Features
+
+### Auto-Refresh
+For URLs, optionally set up periodic refresh:
+```
+/train <url> --refresh=daily
+```
+
+### Merge Knowledge
+Combine multiple sources into one skill:
+```
+/train:merge skill-a skill-b --into=combined-skill
+```
+
+### Export Training
+Export all trained knowledge:
+```
+/train:export --format=zip
+```
+
+## Security Notes
+
+- Only fetch from trusted URLs
+- Sanitize all external content
+- Don't execute code from external sources
+- Review generated skills before enabling
+
+## Examples
+
+### Example 1: Train from API Documentation
+```
+User: /train https://stripe.com/docs/api
+
+Bot: Fetching Stripe API documentation...
+
+Training Complete!
+
+**Skill:** stripe-api
+**Triggers:** "stripe", "payment", "checkout", "subscription"
+**Capabilities:**
+- Create payment intents
+- Handle webhooks
+- Manage subscriptions
+
+Test with: "How do I create a Stripe checkout session?"
+```
+
+### Example 2: Train Custom Workflow
+```
+User: /train:inline
+Our deployment process:
+1. Run tests: npm test
+2. Build: npm run build
+3. Deploy staging: ./deploy.sh staging
+4. Smoke test staging
+5. Deploy prod: ./deploy.sh prod
+
+Bot: Training Complete!
+
+**Skill:** deployment-workflow
+**Triggers:** "deploy", "release", "staging", "production"
+
+Test with: "Help me deploy to staging"
+```
+
+### Example 3: Train from GitHub
+```
+User: /train:github https://github.com/company/styleguide
+
+Bot: Cloning repository...
+Found: README.md, CONTRIBUTING.md, docs/*.md
+
+Training Complete!
+
+**Skills Generated:**
+1. code-style (from style-guide.md)
+2. git-workflow (from CONTRIBUTING.md)
+3. project-setup (from README.md)
+
+Test with: "What's our code style for TypeScript?"
+```

package/templates/discord/start-bot.sh

@@ -0,0 +1,47 @@
+#!/bin/bash
+# Start OpenClaw gateway with Gemini CLI OAuth plugin
+# Uses google-gemini-cli-auth plugin for authentication
+
+set -e
+
+# Check if openclaw is installed
+if ! command -v openclaw &> /dev/null; then
+    echo "❌ OpenClaw CLI not found. Install: npm install -g openclaw"
+    exit 1
+fi
+
+# Check if Gemini CLI is installed
+if ! command -v gemini &> /dev/null; then
+    echo "❌ Gemini CLI not found. Install: npm install -g @anthropic-ai/gemini-cli"
+    echo "   Then login: gemini auth login"
+    exit 1
+fi
+
+# Check Gemini CLI auth status
+GEMINI_CREDS="$HOME/.gemini/oauth_creds.json"
+if [ ! -f "$GEMINI_CREDS" ]; then
+    echo "⚠️  Gemini CLI not logged in. Running: gemini auth login"
+    gemini auth login
+fi
+
+# Enable Gemini CLI auth plugin if not already enabled
+echo "🔧 Ensuring Gemini CLI auth plugin is enabled..."
+openclaw plugins enable google-gemini-cli-auth 2>/dev/null || true
+
+# Check if already authenticated with Gemini CLI provider
+AUTH_STATUS=$(openclaw models auth status --provider google-gemini-cli 2>/dev/null || echo "not-configured")
+
+if [[ "$AUTH_STATUS" == *"not-configured"* ]] || [[ "$AUTH_STATUS" == *"expired"* ]]; then
+    echo "🔑 Setting up Gemini CLI OAuth as default provider..."
+    openclaw models auth login --provider google-gemini-cli --set-default
+fi
+
+echo "✅ Using Gemini CLI OAuth (via plugin)"
+echo "🦞 Starting OpenClaw gateway..."
+
+# Kill existing gateway
+pkill -f "openclaw-gateway" 2>/dev/null || true
+sleep 2
+
+# Start gateway
+openclaw gateway "$@"

package/templates/gemini/settings.json

@@ -0,0 +1,12 @@
+{
+  "$schema": "https://geminicli.com/schemas/settings.json",
+  "experimental": {
+    "plan": true,
+    "enableAgents": true
+  },
+  "general": {
+    "plan": {
+      "directory": "plans"
+    }
+  }
+}

package/templates/hooks/.python-cache.json

@@ -0,0 +1 @@
+{"version":"Python 3.12.10","timestamp":1767230959174}