@agenthippo-ai/agenthippo 1.110.9 → 1.110.19

package/out/base-prompts/skills/openclaw/SKILL.md

@@ -1,406 +0,0 @@
----
-name: openclaw
-description: Fast operational playbook for OpenClaw/HippoClaw: setup channels (especially Telegram), run external-agent gateway bridge, bind routing, verify health, and troubleshoot common failures with minimal commands, and integrate with Agenthippo (CLI + IDE)
----
-
-# OpenClaw / HippoClaw CLI Ops
-
-Use this skill when the user asks to set up, route, test, or debug OpenClaw/HippoClaw with Agenthippo CLI, especially for Telegram + external agent bridging.
-
-## Trigger examples
-
-- "Set up Telegram via hippoclaw"
-- "Route Telegram to agenthippo data-analyst"
-- "Use gateway bridge / external agent"
-- "OpenClaw agent id unknown / missing scope"
-- "Verify channel + routing quickly"
-- Connect my agenthippo server (cli) to telegram.
-
-## Goals
-
-1. Get channel configured and healthy.
-2. Get Agenthippo external agent registered over gateway WebSocket.
-3. Bind routing to target agent/channel.
-4. Prove end-to-end with one smoke test.
-5. Keep command count low and deterministic.
-
-## High-efficiency flow
-
-### 0) Ground truth checks (quick)
-
-If `hippoclaw` is not on PATH, resolve it  based on known install locations, then use that resolved executable for all commands:
-
-```bash
-resolve_hippoclaw() {
-  command -v hippoclaw 2>/dev/null && return 0
-  command -v openclaw 2>/dev/null && return 0
-
-  local c
-  for c in \
-    "$HOME/.npm-global/bin/hippoclaw" \
-    "$HOME/.npm-global/bin/openclaw" \
-    "$HOME/Library/pnpm/hippoclaw" \
-    "$HOME/Library/pnpm/openclaw" \
-    "$HOME/.local/share/pnpm/hippoclaw" \
-    "$HOME/.local/share/pnpm/openclaw"
-  do
-    [[ -x "$c" ]] && { printf '%s\n' "$c"; return 0; }
-  done
-
-  # Agent Anywhere bootstrapped Node global bins
-  while IFS= read -r d; do
-    [[ -x "$d/hippoclaw" ]] && { printf '%s\n' "$d/hippoclaw"; return 0; }
-    [[ -x "$d/openclaw" ]] && { printf '%s\n' "$d/openclaw"; return 0; }
-  done < <(find "$HOME/.agenthippo/tools/node" -maxdepth 4 -type f -path '*/bin/node' -print 2>/dev/null | xargs -I{} dirname "{}" 2>/dev/null | sort -u)
-
-  return 1
-}
-
-HIPPOCLAW_BIN="${AGENT_ANYWHERE_CLI_PATH:-$(resolve_hippoclaw || true)}"
-[[ -n "$HIPPOCLAW_BIN" ]] || { echo "hippoclaw/openclaw not found" >&2; exit 1; }
-```
-
-Run:
-
-```bash
-hippoclaw --version
-hippoclaw gateway status --json
-hippoclaw channels list
-hippoclaw agents bindings --json
-```
-
-Why: confirms active CLI/runtime, gateway reachability, existing channel config, and routing ownership.
-
----
-
-### 0.5) Plugin bootstrap (required before channel add/bind)
-
-Always ensure the target channel plugin is enabled **before** running channel add/bind commands.
-
-Single channel (Telegram):
-
-```bash
-hippoclaw plugins enable telegram
-```
-
-Popular channels bootstrap:
-
-```bash
-hippoclaw plugins enable telegram
-hippoclaw plugins enable whatsapp
-hippoclaw plugins enable discord
-hippoclaw plugins enable slack
-```
-
-Optional verification:
-
-```bash
-hippoclaw plugins list --json
-```
-
-## Gateway startup modes (important)
-
-Prefer explicit gateway startup checks before channel/bridge work.
-
-### A) Service/managed mode (normal daily use)
-
-```bash
-hippoclaw gateway status --json
-```
-
-If running and reachable, continue with channel/bridge steps.
-
-### B) Direct foreground run (debug/recovery)
-
-Use when service state is stale, port ownership is wrong, or you need deterministic local startup:
-
-```bash
-openclaw gateway run --bind loopback --port 18789 --force
-```
-
-Equivalent alias:
-
-```bash
-hippoclaw gateway run --bind loopback --port 18789 --force
-```
-
-Notes:
-- `--bind loopback` keeps gateway local-only (`127.0.0.1`).
-- `--force` clears existing listener conflicts on that port.
-- Keep this process running while testing bridge/routing.
-
-### Post-start verification
-
-```bash
-hippoclaw gateway status --json
-hippoclaw channels status --probe
-```
-
-### 1) Add a channel (plugin must already be enabled)
-
-#### 1.1)Add Telegram channel
-
-Primary command:
-
-```bash
-hippoclaw channels add --channel telegram --token '<BOT_TOKEN>'
-```
-
-If this fails with `Unknown channel: telegram`, enable plugin first:
-
-```bash
-hippoclaw plugins enable telegram
-hippoclaw channels add --channel telegram --token '<BOT_TOKEN>'
-```
-
-Validate:
-
-```bash
-hippoclaw channels status --probe
-```
-
-Expected: Telegram account shows configured/running/works.
-
----
-
-#### 1.2) Add Slack channel (Socket Mode, minimal)
-
-Use Socket Mode for local/dev gateways because it needs no public HTTPS URL. Create the Slack app from the distributed minimal manifest:
-
-```txt
-extensions/agentide/base-prompts/gateway/slack-socket-mode-minimal.manifest.json
-```
-
-Manifest defaults:
-- App DMs/messages tab enabled.
-- Channel mentions enabled.
-- No `/hippoclaw` slash command and no Slack assistant thread UI.
-
-After installing the Slack app at https://api.slack.com/apps, copy:
-- App-Level Token: `xapp-...` with `connections:write`.
-- Bot User OAuth Token: `xoxb-...`.
-
-Enable plugin and configure channel:
-
-```bash
-hippoclaw plugins enable slack
-hippoclaw config set channels.slack.enabled true --strict-json
-hippoclaw config set channels.slack.mode socket
-hippoclaw config set channels.slack.appToken '{"source":"env","provider":"default","id":"SLACK_APP_TOKEN"}' --strict-json
-hippoclaw config set channels.slack.botToken '{"source":"env","provider":"default","id":"SLACK_BOT_TOKEN"}' --strict-json
-```
-
-For initial validation only, open DM/channel access:
-
-```bash
-hippoclaw config set channels.slack.dmPolicy open
-hippoclaw config set channels.slack.allowFrom '["*"]' --strict-json
-hippoclaw config set channels.slack.groupPolicy open
-hippoclaw config set channels.slack.streaming off
-hippoclaw config set channels.slack.nativeStreaming false --strict-json
-hippoclaw config set channels.slack.slashCommand.enabled false --strict-json
-```
-
-Why: disabling Slack streaming avoids occasional duplicate visible replies where a live preview and final message both remain in the channel.
-
-Restart/probe with token env in the gateway process:
-
-```bash
-export SLACK_BOT_TOKEN='xoxb-...'
-export SLACK_APP_TOKEN='xapp-...'
-hippoclaw gateway run --bind loopback --port 18789 --force
-hippoclaw channels status --probe
-```
-
-Expected: Slack default shows enabled/configured/running/works.
-
-Slack smoke tests:
-- DM the app in its **Messages** tab.
-- Or invite it to a channel with `/invite @OpenClaw`, then send `@OpenClaw reply exactly slack channel ok`.
-- Do **not** use `/openclaw` unless slash-command routing has been explicitly wired; otherwise it may route to the gateway default agent instead of the bound external agent.
-
----
-
-### 2) Start Agenthippo serve with gateway bridge (recommended known-good launch)
-
-Use this launch pattern because it reliably passes both gateway token and model/provider env:
-
-```bash
-export OPENCLAW_GATEWAY_TOKEN="$(python3 -c "import json, pathlib; p = pathlib.Path.home() / '.openclaw' / 'openclaw.json'; c = json.loads(p.read_text()); t = c.get('gateway', {}).get('auth', {}).get('token', ''); print(t.strip() if isinstance(t, str) else '')")" && \
-set -a && [ -f "$HOME/.agent-hippo/.env" ] && . "$HOME/.agent-hippo/.env" && set +a && \
-cd "$HOME/dev/agenthippo-vscode/extensions/agentide" && \
-node out/cli/index.js serve --agent data-analyst -m claude-sonnet-4-5-20250929 --gateway-bridge -v -w "$HOME/dev/openclaw" -p 3000
-```
-
-Notes:
-- If port is in use, change `-p`.
-- `-w` should point to the workspace you want the agent operating in.
-- Keep process running (foreground) for active bridge handling.
-
----
-
-### 3) Verify external agent registration
-
-Smoke test through gateway:
-
-```bash
-hippoclaw agent --agent data-analyst --session-id smoke-data-analyst --message "Reply with exactly: data-analyst bridge ok"
-```
-
-Expected response: `data-analyst bridge ok`
-
-If you get `unknown agent id`, bridge is not registered (or process exited).
-
----
-
-### 4) Bind Telegram routing to external agent (plugin must already be enabled)
-
-Check current ownership:
-
-```bash
-hippoclaw agents bindings --json
-```
-
-If conflict exists (e.g. telegram already bound to another agent), unbind old owner, then bind target:
-
-```bash
-hippoclaw agents unbind --agent ide-agenthippo-vscode --bind telegram:default --json
-hippoclaw agents bind --agent data-analyst --bind telegram:default --json
-```
-
-Re-check:
-
-```bash
-hippoclaw agents bindings --json
-```
-
-Expected: telegram/default route points to `data-analyst`.
-
----
-
-### 5) Final verification bundle
-
-```bash
-hippoclaw channels status --probe
-hippoclaw agents bindings --json
-hippoclaw agent --agent data-analyst --session-id smoke-data-analyst-2 --message "1+1? reply exactly 2"
-```
-
-All three should pass.
-
-
-
-## Agenthippo IDE workflow (important)
-
-Use this path when user wants IDE-managed external agent handling (instead of running `agenthippo serve`).
-
-### IDE behavior model
-
-- Gateway still owns channels/sessions/delivery.
-- Agenthippo IDE extension opens a gateway WebSocket and registers external agent IDs (typically `ide-...`, e.g. `ide-agenthippo-vscode`).
-- Routing must point channel/account to the IDE-registered agent ID.
-
-### Fast IDE checks
-
-```bash
-hippoclaw agents list
-hippoclaw agents bindings --json
-```
-
-Look for an `ide-*` agent in list output. If absent, IDE is not connected to gateway yet.
-
-### Route Telegram to IDE agent
-
-Example for common ID:
-
-```bash
-hippoclaw agents bind --agent ide-agenthippo-vscode --bind telegram:default --json
-```
-
-If conflict exists, unbind current owner first, then bind IDE agent.
-
-### IDE smoke test
-
-```bash
-hippoclaw agent --agent ide-agenthippo-vscode --session-id smoke-ide --message "Reply with exactly: ide bridge ok"
-```
-
-If this fails with unknown agent id, reconnect gateway from IDE and retry.
-
-### Choosing CLI vs IDE route
-
-- Use **CLI bridge** (`agenthippo serve --gateway-bridge`) for headless/server automation.
-- Use **IDE bridge** for workspace-native debugging and interactive dev loops.
-- Never assume ownership: always verify with `hippoclaw agents bindings --json` before changing routes.
-
-
-## Bundled script
-
-For a one-command validation run, use:
-
-```bash
-./scripts/run-smoke.sh --agent data-analyst
-```
-
-Script steps:
-1. `hippoclaw gateway status --json`
-2. `hippoclaw channels status --probe`
-3. `hippoclaw agents bindings --json`
-4. `hippoclaw agent --agent <id> --session-id <id> --message <text>`
-
-Use `--help` for options, or env vars: `AGENT_ID`, `SESSION_ID`, `MESSAGE`.
-
-## Common failure signatures and fastest fix
-
-### A) `Unknown channel: telegram`
-Cause: telegram plugin disabled in runtime registry.
-Fix:
-```bash
-hippoclaw plugins enable telegram
-```
-Rule: run plugin enable before any `channels add` / `agents bind` on that channel.
-
-### B) `missing scope: operator.read` / `operator.admin`
-Cause: wrong gateway token/env context for bridge client.
-Fast fix:
-- Export `OPENCLAW_GATEWAY_TOKEN` from `~/.openclaw/openclaw.json` in same shell.
-- Launch using known-good pattern above.
-
-### C) `unknown agent id "data-analyst"`
-Cause: serve process not running/registered.
-Fix:
-- Restart `node out/cli/index.js serve ... --gateway-bridge`
-- Re-run smoke test.
-
-### D) Model/provider error (no API key or no access)
-Cause: provider env not loaded or unsupported model alias.
-Fix:
-- Source `~/.agent-hippo/.env`
-- Use a known-working model for environment (e.g. `claude-sonnet-4-5-20250929`)
-
-### E) `conflicts` on `agents bind`
-Cause: channel/account route already claimed.
-Fix:
-- `agents unbind` old agent for exact `channel:account` then re-bind target.
-
-## Operational guardrails
-
-- Prefer one-step validation after every mutation (add -> probe, bind -> list bindings).
-- For reproducibility, keep token/env exports in same shell invocation as serve launch.
-- Avoid guessing model access; immediately switch to known-working model if smoke test fails on model error.
-- When changing routing, always capture before/after `agents bindings --json`.
-
-## Minimal command set (copy/paste triage)
-
-```bash
-hippoclaw gateway status --json
-hippoclaw channels status --probe
-hippoclaw agents bindings --json
-hippoclaw agent --agent data-analyst --session-id smoke --message "ping"
-```
-
-Interpret quickly:
-- gateway down -> start/fix gateway
-- channel unhealthy -> fix channel/plugin/token
-- binding wrong -> unbind/bind
-- unknown agent -> restart bridge serve

package/out/base-prompts/skills/openclaw/scripts/run-smoke.sh

@@ -1,61 +0,0 @@
-#!/usr/bin/env bash
-set -euo pipefail
-
-AGENT_ID="${AGENT_ID:-data-analyst}"
-SESSION_ID="${SESSION_ID:-smoke-data-analyst}"
-MESSAGE="${MESSAGE:-Reply with exactly: data-analyst bridge ok}"
-
-while [[ $# -gt 0 ]]; do
-  case "$1" in
-    --agent)
-      AGENT_ID="${2:?missing value for --agent}"
-      shift 2
-      ;;
-    --session-id)
-      SESSION_ID="${2:?missing value for --session-id}"
-      shift 2
-      ;;
-    --message)
-      MESSAGE="${2:?missing value for --message}"
-      shift 2
-      ;;
-    -h|--help)
-      cat <<USAGE
-Usage: $(basename "$0") [--agent <id>] [--session-id <id>] [--message <text>]
-
-Runs a fast OpenClaw/HippoClaw operational smoke test:
-  1) gateway status
-  2) channel probe
-  3) routing bindings dump
-  4) external agent run smoke
-
-Env overrides:
-  AGENT_ID, SESSION_ID, MESSAGE
-USAGE
-      exit 0
-      ;;
-    *)
-      echo "Unknown argument: $1" >&2
-      exit 2
-      ;;
-  esac
-done
-
-if ! command -v hippoclaw >/dev/null 2>&1; then
-  echo "hippoclaw not found in PATH" >&2
-  exit 127
-fi
-
-echo "[1/4] gateway status"
-hippoclaw gateway status --json >/dev/null
-
-echo "[2/4] channels probe"
-hippoclaw channels status --probe
-
-echo "[3/4] routing bindings"
-hippoclaw agents bindings --json
-
-echo "[4/4] external agent smoke (agent=${AGENT_ID}, session=${SESSION_ID})"
-hippoclaw agent --agent "${AGENT_ID}" --session-id "${SESSION_ID}" --message "${MESSAGE}"
-
-echo "Smoke test passed."

package/out/base-prompts/skills/pdf/LICENSE.txt

@@ -1,30 +0,0 @@
-© 2025 Anthropic, PBC. All rights reserved.
-
-LICENSE: Use of these materials (including all code, prompts, assets, files,
-and other components of this Skill) is governed by your agreement with
-Anthropic regarding use of Anthropic's services. If no separate agreement
-exists, use is governed by Anthropic's Consumer Terms of Service or
-Commercial Terms of Service, as applicable:
-https://www.anthropic.com/legal/consumer-terms
-https://www.anthropic.com/legal/commercial-terms
-Your applicable agreement is referred to as the "Agreement." "Services" are
-as defined in the Agreement.
-
-ADDITIONAL RESTRICTIONS: Notwithstanding anything in the Agreement to the
-contrary, users may not:
-
-- Extract these materials from the Services or retain copies of these
-  materials outside the Services
-- Reproduce or copy these materials, except for temporary copies created
-  automatically during authorized use of the Services
-- Create derivative works based on these materials
-- Distribute, sublicense, or transfer these materials to any third party
-- Make, offer to sell, sell, or import any inventions embodied in these
-  materials
-- Reverse engineer, decompile, or disassemble these materials
-
-The receipt, viewing, or possession of these materials does not convey or
-imply any license or right beyond those expressly granted above.
-
-Anthropic retains all right, title, and interest in these materials,
-including all copyrights, patents, and other intellectual property rights.