Prodinfos CLI

Use This Skill When

querying product analytics for a Prodinfos project
validating whether SDK instrumentation landed correctly
answering onboarding, paywall, survey, retention, or export questions without raw SQL

Supported Versions

Skill pack: 1.0.0
Target package: @prodinfos/cli
Supported range: ^0.1.0
If a future CLI major changes commands or flags in incompatible ways, split to a sibling skill such as prodinfos-cli-v1

See Versioning Notes.

Non-Goals

Do not generate raw SQL.
Do not request unbounded raw event dumps.
Do not include debug data unless the user explicitly asks for it.

Safety Rules

Always scope by project: --project <id>.
Always scope by time: --last or explicit since/until.
Prefer high-level query endpoints over raw exports.
Keep groupings and result sets bounded.
Treat release-only data as the default.

Query Priorities

Prefer these command families first:

funnel
conversion-after
paths-after
retention
survey
timeseries
breakdown
generic

Only use events export when the user explicitly needs raw CSV.

Data Fidelity Rules

CLI and dashboard both query the API. There is no separate CLI-only analytics source.
Sequence-sensitive and cohort-sensitive queries stay on raw events.
Aggregate-backed reads are acceptable only when the API reports that plan shape.
runtimeEnv is auto-attached by the SDK. Do not invent a separate mode field.

One-Time Setup

Preferred:

npm i -g @prodinfos/cli
prodinfos setup --token <readonly_token>

Alternatives:

prodinfos login --readonly-token <readonly_token>
prodinfos login --clerk-jwt <clerk_jwt>

Output Mode

Prefer --format json for automation or agent reasoning.
Use --format text for short human summaries.
Use timeseries --viz table when exact values matter.
Use timeseries --viz chart or svg when a trend scan is enough.

Validation Loop

After SDK rollout or query changes, validate with a few stable reads:

prodinfos schema events --project <id> --limit 200
prodinfos goal-completion --project <id> --start onboarding:start --complete onboarding:complete --last 30d
prodinfos get onboarding-journey --project <id> --last 30d --format text

Missing Capability Loop

If the requested fetch is impossible with the current CLI surface:

State that the capability is missing.
Do not pretend another command is equivalent if it is not.
Submit CLI feedback with a reproducible gap report.

PRODINFOS_CLI_ENABLE_WRITE_COMMANDS=true prodinfos feedback submit \
  --category feature \
  --message "Missing CLI functionality: <short capability>" \
  --context "Requested fetch: <what user asked>; attempted command: <command>" \
  --meta '{"expected":"<expected output>","actual":"CLI has no command or endpoint"}'

prodinfos-cli