Claude Skill

aai-openpanel

Use aai-cli to read OpenPanel projects, raw event exports, aggregated insights (metrics, pages, referrers, devices, geo), and user profiles.

LLM Mart · 0 points · 1 views 0 listing impressions 0 install-command copies
Download aai-labs-agent-barn-api_domains_agents_aai_cli_skills_bundled_skills_aai-openpanel-a013ede.zip · 10 KB

Install

skills CLI npx skills add https://github.com/aai-labs/agent-barn/tree/main/api/domains/agents/aai_cli_skills/bundled/skills/aai-openpanel
Claude Code claude plugin marketplace add https://llmmart.ai/marketplace.json && claude plugin install aai-labs-agent-barn@llmmart
Git git clone https://github.com/aai-labs/agent-barn.git

The skills CLI installs just this skill, for any of its supported agents. Claude Code installs the whole aai-labs/agent-barn collection as a plugin from our marketplace. Git is the plain clone.

Skill manifest

aai-cli OpenPanel

Use this skill when working with OpenPanel analytics through aai-cli openpanel.

This is a read-only integration — there are no write endpoints (no identify/track calls, no project or client management). Always pass the intended profile with --profile unless the active default profile is already known.

OpenPanel clients are typed write, read, or root server-side, and this matters for which commands work with a given profile:

  • projects list / projects get (the Manage API) require a root client.
  • events export, all insights * commands, and profiles * commands require a read or root client.
  • A project's default write client fails every command here with 401/403.

insights * and profiles * commands need a project ID in the URL — pass --project-id or set profile.project_id to avoid repeating it. events export's --project-id is optional: omit it when the profile's client is already scoped to a single project.

insights pages/referrers/devices/geo accept --limit/--cursor but the provider ignores them — those four always return every breakdown row for the date range, unsorted. To answer a "top N" question, fetch all rows, then sort and slice client-side. Only events export really paginates, and a { "name": null, ... } breakdown row is the "no value for this dimension" bucket, not an error.

Successful output is JSON on stdout, wrapped in an _aai.pagination metadata block added by this CLI. Errors are structured JSON on stderr. See the command reference for command shapes, response notes, and examples captured from a live OpenPanel workspace.

Files (agent-barn)
  • references
    • command-reference.md 27.2 KB
      Loading…
  • SKILL.md 1.9 KB
    ---
    name: aai-openpanel
    description: Use aai-cli to read OpenPanel projects, raw event exports, aggregated insights (metrics, pages, referrers, devices, geo), and user profiles.
    ---
    
    # aai-cli OpenPanel
    
    Use this skill when working with OpenPanel analytics through `aai-cli openpanel`.
    
    This is a **read-only** integration — there are no write endpoints (no `identify`/`track` calls, no project or client management). Always pass the intended profile with `--profile` unless the active default profile is already known.
    
    OpenPanel clients are typed `write`, `read`, or `root` server-side, and this matters for which commands work with a given profile:
    - `projects list` / `projects get` (the Manage API) require a `root` client.
    - `events export`, all `insights *` commands, and `profiles *` commands require a `read` or `root` client.
    - A project's default `write` client fails every command here with `401`/`403`.
    
    `insights *` and `profiles *` commands need a project ID in the URL — pass `--project-id` or set `profile.project_id` to avoid repeating it. `events export`'s `--project-id` is optional: omit it when the profile's client is already scoped to a single project.
    
    `insights pages`/`referrers`/`devices`/`geo` accept `--limit`/`--cursor` but the provider ignores them — those four always return every breakdown row for the date range, unsorted. To answer a "top N" question, fetch all rows, then sort and slice client-side. Only `events export` really paginates, and a `{ "name": null, ... }` breakdown row is the "no value for this dimension" bucket, not an error.
    
    Successful output is JSON on stdout, wrapped in an `_aai.pagination` metadata block added by this CLI. Errors are structured JSON on stderr. See [the command reference](references/command-reference.md) for command shapes, response notes, and examples captured from a live OpenPanel workspace.
    

Comments (0)

Sign in to join the conversation.

No comments yet.

Reviews (0)

No reviews yet.