mcpField
S
statsig-create-cloud-metric

statsig-create-cloud-metric

github.com/statsig-ioData & databases477 installsUpdated 4w ago
Repository

About statsig-create-cloud-metric

A skill for preparing Statsig Cloud metric creation requests. It guides users through required inputs, Cloud metric type mapping, filters, and validation with a dry run.

Key features

  1. 01Cloud metric input checklist
  2. 02Metric type enum mapping
  3. 03Filter and rollup guidance
  4. 04Dry-run request setup
  5. 05curl payload construction

Use cases

  1. 01Drafting a Cloud metric API request
  2. 02Validating a metric before creation
  3. 03Choosing supported filter conditions

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/statsig-io/agent-skills --skill statsig-create-cloud-metric

After installing, type/statsig-create-cloud-metricin Claude Code to confirm it loaded.

Bundled filesreferences/cloud-metric-creation.mdreferences/create-metric-api.md

Details

From the project README

Statsig Create Cloud Metric API

Quick Start

  1. Confirm the request is for a Cloud project.
  2. Collect required inputs: metric name, requested metric kind, and whether to dry run.
  3. Open shared contract guidance in references/create-metric-api.md.
  4. Open references/cloud-metric-creation.md.
  5. Map requested metric kind to API type enum using the Cloud reference.
  6. Draft a curl request with STATSIG-API-KEY and JSON body.

Required Inputs

  • Metric name (4-200 chars).
  • Requested metric kind and API type enum.
  • Event definitions.
  • Filters and optional rollup settings.
  • unitTypes when required by the selected Cloud metric type.

Build the Request

  • Always send POST /console/v1/metrics.
  • Always include Content-Type: application/json and STATSIG-API-KEY.
  • Use dryRun: true for validation-first workflows.
  • Prefer heredoc payloads (--data-binary @- <<'JSON') instead of inline -d '...' JSON when SQL filters include single quotes.
  • For Cloud metrics, set top-level fields such as metricEvents, funnelEventList, and metricComponentMetrics.
  • For criteria-based filters, only use API-supported condition enum values (see references/create-metric-api.md). Do not use aliases like eq.
  • Confirm enum mapping and required fields from the Cloud reference before finalizing.

References

  • Shared API contract and headers: references/create-metric-api.md
  • Cloud metric creation details: references/cloud-metric-creation.md

Comments

Markdown supported