Add integrations/hermes.mdx and integrations/nanoclaw.mdx (v2-only)

[armandokun]

Part of tracking issue openmailsh/openmail#90.

Summary

Add two new integration pages — Hermes Agent and NanoClaw v2 — that explain the auto-discovery install mechanism. Both pages mirror the structure of integrations/claude-code.mdx but adapt to each framework's skill location and credential model.

Changes

integrations/hermes.mdx (new)

Mirror the structure of integrations/claude-code.mdx:

• Frontmatter: title: "Hermes Agent", description: "Give your Hermes agent a real email address in three steps.", icon: feather (or bot)
• 3-step <Steps>: install CLI → openmail setup --agent hermes → openmail status
• Installed files table:
  • ~/.hermes/skills/openmail/SKILL.md — agent instructions
  • ~/.hermes/.env — OPENMAIL_* vars appended to existing file
• Embed the full SKILL.md (claude-code body + Hermes frontmatter variant)
• Note: Hermes skills system auto-discovers ~/.hermes/skills/ — no /plugin install needed
• Related links to /quickstart and /guides/api-integration

integrations/nanoclaw.mdx (new) — v2 only

• Frontmatter: title: "NanoClaw", description: "Give your NanoClaw v2 agent a real email address.", icon: shield
• Lead callout: "OpenMail installs as an operational skill at `/.claude/skills/openmail/SKILL.md` — auto-discovered by Claude Code, no marketplace or plugin install required. Credentials live in the OneCLI Agent Vault by default (or `/.env` if you've run `/use-native-credential-proxy`)."
• 3-step <Steps>:
  1. npm install -g @openmail/cli
  2. cd /path/to/nanoclaw && openmail setup --agent nanoclaw
  3. openmail status
• Section "How it works" (the key explainer):
  • The skill at <repo>/.claude/skills/openmail/SKILL.md is a plain markdown file with YAML frontmatter (name, description, license) and an instruction body telling the agent how to send/receive/search email via the openmail CLI.
  • Claude Code (which NanoClaw v2 builds on) auto-discovers any .claude/skills/<name>/SKILL.md at the project root and hot-loads it. No /plugin install step exists for this kind of skill — it just works the next time Claude Code starts in the directory.
  • Credentials: OPENMAIL_API_KEY, OPENMAIL_INBOX_ID, OPENMAIL_ADDRESS registered with OneCLI Agent Vault via onecli secrets create --host-pattern api.openmail.sh. The CLI reads them at runtime.
  • Re-running openmail setup --agent nanoclaw is idempotent — the skill is overwritten in place; credential lines are strip-and-rewritten.
• Installed files / state table:
  • <repo>/.claude/skills/openmail/SKILL.md — operational skill
  • OneCLI vault entry OPENMAIL_API_KEY (host-pattern api.openmail.sh) — OR <repo>/.env fallback
• Section "After install" — /openmail is immediately available; example invocations
• Manual cleanup section:
  • rm -rf <repo>/.claude/skills/openmail
  • onecli secrets delete OPENMAIL_API_KEY (or strip OPENMAIL_* lines from <repo>/.env)
• Related links

docs.json (1 line change)

Update the "Integrations" group's pages array (current order: openclaw, claude-code, agent-frameworks):

"pages": [
  "integrations/openclaw",
  "integrations/claude-code",
  "integrations/hermes",
  "integrations/nanoclaw",
  "integrations/agent-frameworks"
]

Out of scope

• NanoClaw v1 forks — explicitly excluded; the page commits to v2 conventions.
• Documenting reset/cleanup as an automated command (openmail setup --reset doesn't yet know about hermes/nanoclaw paths). Manual cleanup is documented inline.

Test plan

• Both new pages render in Mintlify preview without errors.
• integrations/hermes and integrations/nanoclaw appear in the Integrations sidebar in correct order.
• All code samples (bash, json, YAML frontmatter) are copy-paste-runnable.
• Cross-links from the new pages back to /quickstart and other integrations resolve.