跳转到内容
Agent Analytics

Hermes

此内容尚不支持你的语言。

For Hermes, the cleanest path is the hosted ClawHub skill. It keeps setup agent-native while using the same underlying Agent Analytics CLI and API surface as the other install paths.

If you are setting this up from a 📎Paperclip company workflow, start with Set up Agent Analytics for your Paperclip company. Use this page when you want the raw Hermes install flow itself.

The important detail: Hermes should use the official pinned CLI through npx --yes @agent-analytics/[email protected] .... The skill gives Hermes the right workflow and guardrails around that CLI.

Prerequisites

Section titled “Prerequisites”
  • Hermes installed and working in the environment where you want Agent Analytics
  • npx available in that runtime
  • Access to the Google or GitHub sign-in you want to connect when Hermes sends the approval link
Section titled “Recommended: ask Hermes to install it for you”

The easiest path is to tell the user: here, copy this prompt and ask Hermes to install the skill.

Install the Agent Analytics skill for me from ClawHub. Use the hosted skill at https://clawhub.ai/dannyshmueli/agent-analytics, install the regular Agent Analytics skill, and tell me when it is ready to use.

The hosted listing is here:

If someone wants the direct command instead, use the source-qualified form:

Terminal window
hermes skills install clawhub/agent-analytics

That is more reliable than the short name alone.

Once installed, Hermes can create projects, generate tracking snippets, query stats, inspect funnels, and manage experiments from the same conversation loop.

Optional: use an Agent Analytics Hermes skin

Section titled “Optional: use an Agent Analytics Hermes skin”

If you want the Hermes CLI itself to match the Agent Analytics palette, the easiest path is to tell the user: here, copy this prompt and ask Hermes to install the skin.

Install the Agent Analytics Hermes skin for me. Download https://docs.agentanalytics.sh/downloads/agent-analytics-hermes-skin.yaml into ~/.hermes/skins/agent-analytics.yaml, switch my current skin to agent-analytics, and tell me when it is active.

If someone wants the manual path instead, install the custom skin YAML built from the shared UI colors:

Terminal window
mkdir -p ~/.hermes/skins
curl -fsSL https://docs.agentanalytics.sh/downloads/agent-analytics-hermes-skin.yaml -o ~/.hermes/skins/agent-analytics.yaml

Then activate it in Hermes:

Terminal window
/skin agent-analytics

Or make it your default in ~/.hermes/config.yaml:

display:
  skin: agent-analytics

Agent Analytics Hermes skin screenshot

The skin uses the core Agent Analytics screenshot palette:

  • primary green: #0f9f5b
  • warm accent: #f06a19
  • dark base: #111412
  • raised dark surface: #171b18
  • light text: #f3efe4
  • muted text: #8d958d

This version intentionally avoids blue accents so it matches the live Hermes skin look more closely.

If you want to tweak it, start from the downloadable YAML:

The Hermes skin system itself is documented here:

The public skill repo also includes agent-analytics-autoresearch, which is the growth-loop skill for producing experiment candidates from analytics data. Use the regular Agent Analytics skill for setup and reporting; use the autoresearch skill when you want the loop to generate, critique, judge, and rerun variants from measured evidence.

Verify the CLI path

Section titled “Verify the CLI path”

Run:

Terminal window
npx --yes @agent-analytics/[email protected] --help

This confirms that the pinned CLI path works in the Hermes runtime before you start login or project setup.

Start login with detached approval

Section titled “Start login with detached approval”

The normal Hermes path is detached browser approval:

Terminal window
npx --yes @agent-analytics/[email protected] login --detached

That command prints:

  • an approval URL
  • an approval code
  • a follow-up login --auth-request ... --exchange-code ... command

Use detached login when Hermes is running remotely, in a managed runtime, or in any workflow where the agent should hand you a browser approval link and then continue after your reply.

Important: web preview vs CLI scanner

Section titled “Important: web preview vs CLI scanner”

Anonymous website-analysis preview is available on the public web scanner:

In Hermes and other CLI runtimes, website analysis is an authenticated setup workflow. Sign in first, then run scans only for sites you own or manage as part of Agent Analytics setup.

For authenticated CLI scans, Hermes should create or identify the matching project first, because the project allowed_origins domain must match the scanned hostname.

First setup flow in Hermes

Section titled “First setup flow in Hermes”

Use this order:

Terminal window
npx --yes @agent-analytics/[email protected] login --detached
npx --yes @agent-analytics/[email protected] create my-site --domain https://mysite.com
npx --yes @agent-analytics/[email protected] scan https://mysite.com --project my-site --json
npx --yes @agent-analytics/[email protected] events my-site --event <first_useful_event> --days 7 --limit 20

That gives Hermes a project-scoped website analysis, the first recommended instrumentation, and a concrete event verification step.

Example Hermes prompt

Section titled “Example Hermes prompt”

After installing the skill, tell Hermes:

Set up Agent Analytics for this project. If approval is needed, send me the login link and wait. I will sign in with Google or GitHub, then reply with the finish code. After that, create or identify the matching Agent Analytics project, run website analysis for this site so you know what my agent should track first, install only the high-priority minimum viable instrumentation, explain what each event enables, and verify the first useful recommended event.

For deeper product analysis, extend it with owned surfaces:

If this product has other owned public websites or pages that shape the growth loop, scan those too and tell me what data we are not collecting yet before you install events.

Demo mode first if you want a no-login proof

Section titled “Demo mode first if you want a no-login proof”

If you want to prove the CLI flow before connecting a real account, run:

Terminal window
npx --yes @agent-analytics/[email protected] demo
npx --yes @agent-analytics/[email protected] --demo stats agentanalytics-demo --days 30
npx --yes @agent-analytics/[email protected] --demo funnel agentanalytics-demo --steps "page_view,signup_started,signup"

Demo mode is read-only, uses seeded sample data, and does not touch your saved CLI login.

Troubleshooting

Section titled “Troubleshooting”
  • If hermes skills install agent-analytics does not resolve correctly, use hermes skills install clawhub/agent-analytics.
  • If scan <url> tells you to sign in first, that is expected in CLI. Use the public web scanner for anonymous preview.
  • If Hermes says --project is required for website analysis, create or identify the matching Agent Analytics project first, then rerun the scan.
  • If login worked earlier but later says “Not logged in”, run auth status and confirm Hermes is using the config directory you expect.
  • If you intentionally use a compatibility API key for direct HTTP debugging, keep it in the runtime environment rather than pasting it into chat.
Section titled “Related”