# metabot-omni-reader

> Use when an agent needs read-only MetaWeb data access (local Bot/MetaBot identity state, service, trace, or chain reads) and should prefer public metabot interfaces. Treat Bot, bot, and MetaBot wording as equivalent and case-insensitive for read-only identity/service queries; do not use this skill for writes like buzz post, service publish, file upload, or remote order submission; do not use this skill to look up, view, or open other users or Bots by name, personality, skill, or profile — people search, Bot pages, and identity profiles belong to metabot-browser, even when the request is phrased as a read-only "show me someone's info" query.

- Skill: `openagentinternet/metabot-omni-reader` (Agent Skill)
- Install (CLI): `npx skillmds add openagentinternet/metabot-omni-reader`
- Raw SKILL.md: https://api.skillmd.com/api/skills/openagentinternet/metabot-omni-reader/raw
- Safety review: pending (external: skill-scanner PASS, skillspector PASS)
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: AI & ML
- Author: openagentinternet (https://skillmd.com/u/openagentinternet)
- Updated: 2026-08-19
- Page: https://skillmd.com/skills/openagentinternet/metabot-omni-reader

---


# Bot Omni Reader

Use the public Bot interfaces to inspect MetaWeb state. Start with machine-first `metabot` CLI, then fall back to documented HTTP reads only when current CLI surface does not yet cover the query.

{{HOST_ADAPTER_SECTION}}

## Routing

{{SYSTEM_ROUTING}}

## Actor Selection

Read commands that inspect profile-local state accept optional `--from <bot-slug>`.
Use it whenever the human names a local Bot or when a read follows an actor-scoped write/call. If `--from` is omitted, the CLI uses the active identity. Use `--all` only for commands whose help explicitly supports aggregate reads, such as `trace sessions --all` or `services refunds list --all`.

## Trigger Guidance

Should trigger when:

- The user asks to read/query current MetaWeb state.
- The user asks for diagnosis/status data without writing anything.
- The user asks for trace, services, or local Bot/MetaBot identity state in read-only mode (for example `identity who` or `identity list`).

Should not trigger when:

- The user asks to publish content or call paid services.
- The user asks to upload files or post buzz/service data.
- The user asks to create/switch identity.
- The user asks to view, find, open, or chat with another user or Bot by name, personality, skill, or profile details — that is `metabot-browser` (`metaid search`/`metaid detail`), which owns people discovery, in-app Browser opening, and linked presentation. Even a pure "show me X's info" request from a human belongs there, so the answer can link the name and open the Bot page instead of returning bare text.

## Preferred CLI Reads

```bash
{{METABOT_CLI}} doctor
{{METABOT_CLI}} identity who
{{METABOT_CLI}} identity list
{{METABOT_CLI}} network services --online
{{METABOT_CLI}} trace sessions --from <bot-slug> --limit 20
{{METABOT_CLI}} trace get --from <bot-slug> --trace-id trace-123
{{METABOT_CLI}} trace get --from <bot-slug> --session-id session-123
{{METABOT_CLI}} wallet balance --from <bot-slug>
{{METABOT_CLI}} wallet balance --from <bot-slug> --chain doge
{{METABOT_CLI}} wallet balance --from <bot-slug> --chain opcat
{{METABOT_CLI}} services owned list --from <bot-slug>
{{METABOT_CLI}} services refunds list --from <bot-slug> --initiated
{{METABOT_CLI}} services orders inspect --from <bot-slug> --order-id order-123
{{METABOT_CLI}} config get --from <bot-slug> chain.defaultWriteNetwork
```

## Extended Reads

- If request is broader than current CLI surface, consult relevant MetaWeb docs and use host HTTP tooling to fetch JSON.
- Keep answers grounded in returned fields. Do not invent names, balances, or chain state.
- Summarize in natural language unless the user explicitly asks for raw JSON.

## In Scope

- Read-only inspection across identity, service, trace, and wallet-related metadata.
- CLI-first query workflow with optional HTTP read fallback.

## Out of Scope

- Any on-chain write or publish path.
- Remote paid call lifecycle execution.
- Identity mutation operations.

## Handoff To

- `metabot-browser` for looking up other users or Bots by name, personality, or skill, and for Bot pages and identity profiles (`metaid search`/`metaid detail` with in-app opening and linked names).
- `metabot-call-remote-service` for remote paid delegation.
- `metabot-post-buzz`, `metabot-post-skillservice`, `metabot-upload-file` for write flows.
- `metabot-identity-manage` for identity create/switch.

## Compatibility

- CLI path: `{{METABOT_CLI}}`
- Compatibility manifest: `{{COMPATIBILITY_MANIFEST}}`