statsig-create-cloud-metric

Create Statsig Cloud metrics via the Console API POST /console/v1/metrics. Use when drafting or executing Create Metric requests for Cloud projects, including required fields and metric type differences.

Safety Notice

This listing is imported from skills.sh public index metadata. Review upstream SKILL.md and repository scripts before running.

Copy this and send it to your AI assistant to learn

Install skill "statsig-create-cloud-metric" with this command: npx skills add statsig-io/agent-skills/statsig-io-agent-skills-statsig-create-cloud-metric

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

Source Transparency

This detail page is rendered from real SKILL.md content. Trust labels are metadata-based hints, not a safety guarantee.

Related Skills

Related by shared tags or category signals.

Automation

statsig-dashboard

No summary provided by upstream source.

Repository SourceNeeds Review
Automation

statsig

No summary provided by upstream source.

Repository SourceNeeds Review
Automation

vercel-composition-patterns

React composition patterns that scale. Use when refactoring components with boolean prop proliferation, building flexible component libraries, or designing reusable APIs. Triggers on tasks involving compound components, render props, context providers, or component architecture. Includes React 19 API changes.

Repository Source
86.2K23Kvercel
Automation

vercel-react-native-skills

React Native and Expo best practices for building performant mobile apps. Use when building React Native components, optimizing list performance, implementing animations, or working with native modules. Triggers on tasks involving React Native, Expo, mobile performance, or native platform APIs.

Repository Source
60.5K23Kvercel