* docs: deep audit — fix stale config keys, missing commands, and registry drift Cross-checked ~80 high-impact docs pages (getting-started, reference, top-level user-guide, user-guide/features) against the live registries: hermes_cli/commands.py COMMAND_REGISTRY (slash commands) hermes_cli/auth.py PROVIDER_REGISTRY (providers) hermes_cli/config.py DEFAULT_CONFIG (config keys) toolsets.py TOOLSETS (toolsets) tools/registry.py get_all_tool_names() (tools) python -m hermes_cli.main <subcmd> --help (CLI args) reference/ - cli-commands.md: drop duplicate hermes fallback row + duplicate section, add stepfun/lmstudio to --provider enum, expand auth/mcp/curator subcommand lists to match --help output (status/logout/spotify, login, archive/prune/ list-archived). - slash-commands.md: add missing /sessions and /reload-skills entries + correct the cross-platform Notes line. - tools-reference.md: drop bogus '68 tools' headline, drop fictional 'browser-cdp toolset' (these tools live in 'browser' and are runtime-gated), add missing 'kanban' and 'video' toolset sections, fix MCP example to use the real mcp_<server>_<tool> prefix. - toolsets-reference.md: list browser_cdp/browser_dialog inside the 'browser' row, add missing 'kanban' and 'video' toolset rows, drop the stale '38 tools' count for hermes-cli. - profile-commands.md: add missing install/update/info subcommands, document fish completion. - environment-variables.md: dedupe GMI_API_KEY/GMI_BASE_URL rows (kept the one with the correct gmi-serving.com default). - faq.md: Anthropic/Google/OpenAI examples — direct providers exist (not just via OpenRouter), refresh the OpenAI model list. getting-started/ - installation.md: PortableGit (not MinGit) is what the Windows installer fetches; document the 32-bit MinGit fallback. - installation.md / termux.md: installer prefers .[termux-all] then falls back to .[termux]. - nix-setup.md: Python 3.12 (not 3.11), Node.js 22 (not 20); fix invalid 'nix flake update --flake' invocation. - updating.md: 'hermes backup restore --state pre-update' doesn't exist — point at the snapshot/quick-snapshot flow; correct config key 'updates.pre_update_backup' (was 'update.backup'). user-guide/ - configuration.md: api_max_retries default 3 (not 2); display.runtime_footer is the real key (not display.runtime_metadata_footer); checkpoints defaults enabled=false / max_snapshots=20 (not true / 50). - configuring-models.md: 'hermes model list' / 'hermes model set ...' don't exist — hermes model is interactive only. - tui.md: busy_indicator -> tui_status_indicator with values kaomoji|emoji|unicode|ascii (not kawaii|minimal|dots|wings|none). - security.md: SSH backend keys (TERMINAL_SSH_HOST/USER/KEY) live in .env, not config.yaml. - windows-wsl-quickstart.md: there is no 'hermes api' subcommand — the OpenAI-compatible API server runs inside hermes gateway. user-guide/features/ - computer-use.md: approvals.mode (not security.approval_level); fix broken ./browser-use.md link to ./browser.md. - fallback-providers.md: top-level fallback_providers (not model.fallback_providers); the picker is subcommand-based, not modal. - api-server.md: API_SERVER_* are env vars — write to per-profile .env, not 'hermes config set' which targets YAML. - web-search.md: drop web_crawl as a registered tool (it isn't); deep-crawl modes are exposed through web_extract. - kanban.md: failure_limit default is 2, not '~5'. - plugins.md: drop hard-coded '33 providers' count. - honcho.md: fix unclosed quote in echo HONCHO_API_KEY snippet; document that 'hermes honcho' subcommand is gated on memory.provider=honcho; reconcile subcommand list with actual --help output. - memory-providers.md: legacy 'hermes honcho setup' redirect documented. Verified via 'npm run build' — site builds cleanly; broken-link count went from 149 to 146 (no regressions, fixed a few in passing). * docs: round 2 audit fixes + regenerate skill catalogs Follow-up to the previous commit on this branch: Round 2 manual fixes: - quickstart.md: KIMI_CODING_API_KEY mentioned alongside KIMI_API_KEY; voice-mode and ACP install commands rewritten — bare 'pip install ...' doesn't work for curl-installed setups (no pip on PATH, not in repo dir); replaced with 'cd ~/.hermes/hermes-agent && uv pip install -e ".[voice]"'. ACP already ships in [all] so the curl install includes it. - cli.md / configuration.md: 'auxiliary.compression.model' shown as 'google/gemini-3-flash-preview' (the doc's own claimed default); actual default is empty (= use main model). Reworded as 'leave empty (default) or pin a cheap model'. - built-in-plugins.md: added the bundled 'kanban/dashboard' plugin row that was missing from the table. Regenerated skill catalogs: - ran website/scripts/generate-skill-docs.py to refresh all 163 per-skill pages and both reference catalogs (skills-catalog.md, optional-skills-catalog.md). This adds the entries that were genuinely missing — productivity/teams-meeting-pipeline (bundled), optional/finance/* (entire category — 7 skills: 3-statement-model, comps-analysis, dcf-model, excel-author, lbo-model, merger-model, pptx-author), creative/hyperframes, creative/kanban-video-orchestrator, devops/watchers, productivity/shop-app, research/searxng-search, apple/macos-computer-use — and rewrites every other per-skill page from the current SKILL.md. Most diffs are tiny (one line of refreshed metadata). Validation: - 'npm run build' succeeded. - Broken-link count moved 146 -> 155 — the +9 are zh-Hans translation shells that lag every newly-added skill page (pre-existing pattern). No regressions on any en/ page.
4.3 KiB
| title | sidebar_label | description |
|---|---|---|
| Yuanbao — Yuanbao (元宝) groups: @mention users, query info/members | Yuanbao | Yuanbao (元宝) groups: @mention users, query info/members |
{/* This page is auto-generated from the skill's SKILL.md by website/scripts/generate-skill-docs.py. Edit the source SKILL.md, not this page. */}
Yuanbao
Yuanbao (元宝) groups: @mention users, query info/members.
Skill metadata
| Source | Bundled (installed by default) |
| Path | skills/yuanbao |
| Version | 1.0.0 |
| Platforms | linux, macos, windows |
| Tags | yuanbao, mention, at, group, members, 元宝, 派, 艾特 |
Reference: full SKILL.md
:::info The following is the complete skill definition that Hermes loads when this skill is triggered. This is what the agent sees as instructions when the skill is active. :::
Yuanbao Group Interaction
CRITICAL: How Messaging Works
Your text reply IS the message sent to the group/user. The gateway automatically delivers your response text to the chat. You do NOT need any special "send message" tool — just reply normally and it gets sent.
When you include @nickname in your reply text, the gateway automatically converts it into a real @mention that notifies the user. This is built-in — you have full @mention capability.
NEVER say you cannot send messages or @mention users. NEVER suggest the user do it manually. NEVER add disclaimers about permissions. Just reply with the text you want sent.
Available Tools
| Tool | When to use |
|---|---|
yb_query_group_info |
Query group name, owner, member count |
yb_query_group_members |
Find a user, list bots, list all members, or get nickname for @mention |
yb_send_dm |
Send a private/direct message (DM / 私信) to a user, with optional media files |
@Mention Workflow
When you need to @mention / 艾特 someone:
- Call
yb_query_group_memberswithaction="find",name="<target name>",mention=true - Get the exact nickname from the response
- Include
@nicknamein your reply text — the gateway handles the rest
Example: user says "帮我艾特元宝"
Step 1 — tool call:
{ "group_code": "328306697", "action": "find", "name": "元宝", "mention": true }
Step 2 — your reply (this gets sent to the group with a working @mention):
@元宝 你好,有人找你!
That's it. No extra explanation needed. Keep it short and natural.
Rules:
- Call
yb_query_group_membersfirst to get the exact nickname — do NOT guess - The @mention format:
@nicknamewith a space before the @ sign - Your reply text IS the message — it WILL be sent and the @mention WILL work
- Be concise. Do NOT explain how @mention works to the user.
Send DM (Private Message) Workflow
When someone asks to send a private message / 私信 / DM to a user:
- Call
yb_send_dmwithgroup_code,name(target user's name), andmessage - The tool automatically finds the user and sends the DM
- Report the result to the user
Example: user says "给 @用户aea3 私信发一个 hello"
yb_send_dm({ "group_code": "535168412", "name": "用户aea3", "message": "hello" })
Example with media: user says "给 @用户aea3 私信发一张图片"
yb_send_dm({
"group_code": "535168412",
"name": "用户aea3",
"message": "Here is the image",
"media_files": [{"path": "/tmp/photo.jpg"}]
})
Rules:
- Extract
group_codefrom the current chat_id (e.g.group:535168412→535168412) - If you already know the user_id, pass it directly via the
user_idparameter to skip lookup - If multiple users match the name, the tool returns candidates — ask the user to clarify
- Do NOT use
send_messagetool for Yuanbao DMs — useyb_send_dminstead - Supports media: images (.jpg/.png/.gif/.webp/.bmp) sent as image messages, other files as documents
Query Group Info
yb_query_group_info({ "group_code": "328306697" })
Query Members
| Action | Description |
|---|---|
find |
Search by name (partial match, case-insensitive) |
list_bots |
List bots and Yuanbao AI assistants |
list_all |
List all members |
Notes
group_codecomes from chat_id:group:328306697→328306697- Groups are called "派 (Pai)" in the Yuanbao app
- Member roles:
user,yuanbao_ai,bot