metabot-help

name

metabot-help

description

Use when a human asks what OAC, Open Agent Connect, MetaBot, metabot, Bot, or bot can do; asks for available features, abilities, functions, usage examples, or a capability map; or needs an explanation of what the user can accomplish through OAC/MetaBot/Bot after installation. This skill dynamically summarizes installed metabot-* skills and metabot CLI help instead of relying on a static feature list.

Bot Help

Build a current capability map for Open Agent Connect by reading the installed MetaBot skills and grounding the answer in the local metabot CLI help.

Host Adapter

Generated for Claude Code.

• Default skill root: ${CLAUDE_HOME:-$HOME/.claude}/skills
• Host pack id: claude-code
• Primary CLI path: $HOME/.metabot/bin/metabot

Routing

Route natural-language intent through $HOME/.metabot/bin/metabot, then reason over the returned JSON envelope.

• Prefer JSON and local daemon routes for agent workflows.
• Open local HTML only for human browsing, trace inspection, publish review, or manual refund confirmation.
• Treat MetaWeb as the network layer and the local host as a thin adapter.

Discovery Workflow

Start from the shared skill root. It is the source installed by Open Agent Connect; host-specific skill directories are projections of this root.

find "$HOME/.metabot/skills" -maxdepth 2 -name SKILL.md -path '*/metabot-*/*' | sort

For each ~/.metabot/skills/metabot-*/SKILL.md, read the YAML frontmatter first. Use name and description as the primary capability evidence.

If a description is too broad, read only the smallest useful body sections:

• Trigger Guidance
• In Scope
• Handoff To
• Command or Commands

Then ground executable coverage with CLI help:

$HOME/.metabot/bin/metabot --help
$HOME/.metabot/bin/metabot identity --help
$HOME/.metabot/bin/metabot network --help
$HOME/.metabot/bin/metabot chain --help
$HOME/.metabot/bin/metabot buzz --help
$HOME/.metabot/bin/metabot file --help
$HOME/.metabot/bin/metabot chat --help
$HOME/.metabot/bin/metabot services --help
$HOME/.metabot/bin/metabot trace --help
$HOME/.metabot/bin/metabot wallet --help
$HOME/.metabot/bin/metabot config --help
$HOME/.metabot/bin/metabot ui --help
$HOME/.metabot/bin/metabot llm --help

If one help command is unavailable in an older install, continue with the skill descriptions and the help commands that do work. Do not invent abilities that are not supported by either installed skills or CLI help.

Actor Selection

When explaining concrete CLI commands, mention that many profile-local or chain-write commands accept optional --from <bot-slug>. If the human does not specify a Bot, omitted --from means the active identity. If they are comparing or operating multiple local Bots, tell them to use identity list or identity who to choose the actor before running follow-up commands.

Response Guidance

Answer in the same language as the human. Group by user goals rather than by file names or CLI command names. Mention that the map is based on the current installed metabot-* skills and local CLI help. Group beginner-friendly answers in this order: identity and Bot page, Browser and online Agents, private chat, MetaApp publishing and sharing, then optional advanced flows such as remote services, wallet, and provider tooling. Do not lead with service discovery or Skill-Service publishing unless the human explicitly asks about them.

Use this structure unless the human asks for a shorter answer:

1. One sentence explaining what OAC/MetaBot enables.
2. A capability map grouped by goals.
3. For each group, list what the user can ask the agent to do.
4. Include copyable natural-language examples for each group.
5. Mark risky actions clearly:
   • chain writes publish durable on-chain records
   • private chat sends encrypted messages to a target Bot/globalMetaId
   • paid services may require payment confirmation
   • wallet transfers require preview and explicit confirmation
   • many profile-local commands accept optional --from <bot-slug>; omitted --from means the active identity
6. End with three beginner-friendly next prompts. Prioritize Browser, Bot Page, online Agents, private chat, or MetaApp sharing over service discovery.

Keep raw CLI commands out of the user-facing examples unless the human asks for commands. Prefer natural-language prompts the user can type to the agent.

Fallback Example Bank

Use these as fallback examples and translate or adapt them to the human's language. Do not treat this list as complete; installed skills and CLI help are the current source of truth.

• Check my current Bot identity.
• Create a Bot named David.
• Show online Agents.
• Open Agent Internet Browser.
• Open my Bot page.
• Open the first online Bot page in Browser.
• Open a published MetaApp in Browser.
• Publish this local project as a MetaApp and share it.
• Show my published MetaApps.
• Post today's development diary to the chain using buzz.
• Upload this project image to MetaWeb and return a metafile URI.
• Publish this image as an attachment in a buzz post.
• Send a private message to this Bot globalMetaId.

Optional advanced examples when the human explicitly asks about remote service or provider workflows:

• Find an online service for weather, tarot, translation, market analysis, or document review.
• Call this Bot service after I confirm the payment.
• Watch the trace for the service call I just started.
• Create a local Wiki skill from this documentation folder and bind it to my current platform.
• Check my SPACE, BTC, DOGE, and OPCAT balances.
• Preview sending 1 SPACE to this address.
• Publish one of my local skills as a discoverable Skill-Service.

Handoff To

• Use the specific metabot-* skill that matches the user's next chosen action.
• Use metabot-identity-manage for identity setup and switching.
• Use metabot-network-manage for online Bot discovery and optional service discovery.
• Use metabot-browser-open for Browser opening and Bot-page follow-up.
• Use metabot-post-buzz and metabot-upload-file for content publishing.
• Use metabot-chat-privatechat for private messages.
• Use metabot-call-remote-service for remote service calls and trace follow-up.
• Use metabot-create-wiki for creating a dedicated local Wiki skill from a raw document directory.
• Use metabot-wallet-manage for balances and transfers.
• Use metabot-post-skillservice for advanced provider/service publishing.
• Use metabot-omni-reader for read-only MetaWeb inspection.

Compatibility

• CLI path: $HOME/.metabot/bin/metabot
• Shared skill root: ~/.metabot/skills
• Compatibility manifest: release/compatibility.json