bq-analytics-flags

Manage bq-analytics feature flags with Vercel Edge Config and the bq-flags CLI.

5|Updated Apr 27, 2026
One-click install
npx skills add https://github.com/johnkueh/bq-analytics --skill bq-analytics-flags
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: bq-analytics-flags
Source: https://github.com/johnkueh/bq-analytics/tree/main/claude-skills/flags
Command: npx skills add https://github.com/johnkueh/bq-analytics --skill bq-analytics-flags

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Centralizes and streamlines feature-flag governance for bq-analytics, enabling controlled rollouts, easy toggling, and clear exposure tracking.

Core Features & Use Cases

  • Flag provisioning and rollout with on/off states and gradual rollout percentages.
  • Edge Config-backed exposure tracking to measure flag impact in analytics.
  • Cross-runtime integration: server, browser, and CLI workflows with shared backend.

Quick Start

Run the installation steps to provision Edge Config, wire the SDK, and begin managing flag rollouts.

Frequently Asked Questions about bq-analytics-flags

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I manage feature flags for staged rollouts using Vercel Edge Config?▼

You can manage feature flags for staged rollouts using Vercel Edge Config by provisioning the config, wiring the SDK, and using a CLI to toggle on/off states and set gradual rollout percentages across server, browser, and CLI deployments.

What is feature flag exposure tracking and how does it work with Edge Config?▼

Feature flag exposure tracking records when a user encounters a specific flag state. With Edge Config, it measures flag impact in analytics by centralizing flag governance and tracking exposures across cross-runtime integrations like server and browser environments.

Do I need a bq-analytics project to use feature flag rollouts with Edge Config?▼

Yes, you need a bq-analytics project, access to Edge Config, and the bq-flags CLI to perform on/off toggles, allowlists, gradual rollouts, and exposure analytics. These prerequisites enable controlled flag management across deployments.

Can I use the same feature flags across server, browser, and CLI deployments?▼

Yes, you can share the same feature flags across server, browser, and CLI deployments. The system provides cross-runtime integration with a shared backend, allowing consistent flag evaluation and exposure tracking across all environments.

What's the best way to automate feature flag provisioning and evaluation?▼

The best way to automate feature flag provisioning and evaluation is to use a CLI tool to manage on/off states, allowlists, and rollout percentages. This centralizes governance and streamlines exposure tracking for analytics.