/kb-guide
Search, read, create, and update knowledge base entries via MCP-connected KB tools. Use when the user asks to look up documentation, find existing articles, check if docs exist on a topic, create a new KB entry, update an existing document, or when domain questions should be
$ npx -y skills add 0xranx/golembot --skill kb-guide --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
- Slash command
/kb-guide
Context preview
The summary Claude sees to decide when to auto-load this skill.
Search, read, create, and update knowledge base entries via MCP-connected KB tools. Use when the user asks to look up documentation, find existing articles, check if docs exist on a topic, create a new KB entry, update an existing document, or when domain questions should be
SKILL.md
kb-guide.SKILL.mdname: kb-guide
description: "Search, read, create, and update knowledge base entries via MCP-connected KB tools. Use when the user asks to look up documentation, find existing articles, check if docs exist on a topic, create a new KB entry, update an existing document, or when domain questions should be answered from the knowledge base first."
Knowledge Base Integration Guide
When MCP knowledge base servers are configured, you can use their tools to search, read, create, and update knowledge entries.
Common MCP Knowledge Base Tools
MCP KB servers typically expose tools with these patterns:
Search / Query
- `search_documents(query, limit?)` -- full-text search across the knowledge base
- `search_notes(query)` -- search personal notes or wiki entries
- `query_knowledge(query, filters?)` -- filtered search with metadata constraints
Read
- `get_document(id)` -- retrieve a document by ID
- `read_page(path)` -- read a wiki page by path
- `list_documents(folder?, tag?)` -- list documents in a folder or by tag
Create / Update
- `create_document(title, content, metadata?)` -- create a new entry
- `update_document(id, content)` -- update an existing document
- `create_note(title, body)` -- create a quick note
Example Tool Call
When a user asks "do we have docs on deployment?", search the KB first:
Tool: search_documents
Arguments: { "query": "deployment", "limit": 5 }Present matching results with titles and snippets. If no results are found, offer to create a new entry.
When to Use Knowledge Base
- **Before answering domain questions**: Search the KB first -- it may contain authoritative answers
- **When the user asks "do we have docs on..."**: Search the KB and return results
- **After resolving an issue**: Suggest creating a KB entry to capture the solution
- **For onboarding/FAQ questions**: Check if there's an existing KB article
Usage Pattern
1. Identify the user's intent (search, read, write) 2. Call the appropriate MCP tool by name 3. If a tool is not available, inform the user that no KB server is configured 4. Present results clearly -- include titles, snippets, and links when available
Notes
- MCP server configuration is defined in `golem.yaml` under the `mcp` key
- Available MCP tools depend on which servers are configured -- use tool discovery to check
- Always prefer searching the KB before generating answers from your own training data
Read more
name: kb-guide description: "Search, read, create, and update knowledge base entries via MCP-connected KB tools. Use when the user asks to look up documentation, find existing articles, check if docs exist on a topic, create a new KB entry, update an existing document, or when domain questions should be answered from the knowledge base first."
Knowledge Base Integration Guide
When MCP knowledge base servers are configured, you can use their tools to search, read, create, and update knowledge entries.
Common MCP Knowledge Base Tools
MCP KB servers typically expose tools with these patterns:
Search / Query
- `search_documents(query, limit?)` -- full-text search across the knowledge base
- `search_notes(query)` -- search personal notes or wiki entries
- `query_knowledge(query, filters?)` -- filtered search with metadata constraints
Read
- `get_document(id)` -- retrieve a document by ID
- `read_page(path)` -- read a wiki page by path
- `list_documents(folder?, tag?)` -- list documents in a folder or by tag
Create / Update
- `create_document(title, content, metadata?)` -- create a new entry
- `update_document(id, content)` -- update an existing document
- `create_note(title, body)` -- create a quick note
Example Tool Call
When a user asks "do we have docs on deployment?", search the KB first:
Tool: search_documents
Arguments: { "query": "deployment", "limit": 5 }Present matching results with titles and snippets. If no results are found, offer to create a new entry.
When to Use Knowledge Base
- **Before answering domain questions**: Search the KB first -- it may contain authoritative answers
- **When the user asks "do we have docs on..."**: Search the KB and return results
- **After resolving an issue**: Suggest creating a KB entry to capture the solution
- **For onboarding/FAQ questions**: Check if there's an existing KB article
Usage Pattern
1. Identify the user's intent (search, read, write) 2. Call the appropriate MCP tool by name 3. If a tool is not available, inform the user that no KB server is configured 4. Present results clearly -- include titles, snippets, and links when available
Notes
- MCP server configuration is defined in `golem.yaml` under the `mcp` key
- Available MCP tools depend on which servers are configured -- use tool discovery to check
- Always prefer searching the KB before generating answers from your own training data
Any Agent × Any Provider × Anywhere. Connect Cursor, Claude Code, OpenCode, or Codex to Slack, Telegram, Discord, Feishu, DingTalk, WeCom, WeChat — with any LLM provider.
Repo: 0xranx/golembot
Other skills on golembot.
- /escalation
Escalate unresolvable or sensitive requests to a human agent by recording an escalation entry. Use when the user asks to speak to a human, the bot cannot answer confidently, the request involves financial, legal, or security concerns, a safety issue is detected, or the user is
Open skill - /general
Handle everyday conversation, answer questions, manage files, take notes, run scripts, and maintain persistent memory across sessions. Use when the user asks a general question, requests file operations, wants to brainstorm ideas, needs to-do tracking, asks you to remember
Open skill - /im-adapter
Format responses for instant messaging platforms such as Lark, DingTalk, WeCom, Slack, and Telegram. Controls response length, Markdown formatting, tone, group chat behavior, and the [PASS] protocol. Use when replying through an IM channel, composing a group chat message, or
Open skill - /message-push
Send proactive messages to IM groups or individual users via the gateway Send API. Use when the user says to send, post, notify, forward, or tell someone a message on Feishu, Slack, Telegram, Discord, DingTalk, or WeCom.
Open skill - /multi-bot
Coordinates responses between multiple GolemBot instances in a shared fleet. Use when the bot operates in a group chat with other bots, needs to decide whether to respond or pass, or must call a peer bot's API to fetch cross-domain data.
Open skill - /task-manager
Creates and manages scheduled tasks, cron jobs, recurring reminders, and timers via the Task HTTP API. Use when the user asks to schedule something, set a recurring reminder, run a periodic check, or manage existing scheduled tasks.
Open skill

