By featbit
Manage feature flags with FeatBit: deploy the platform on AWS (ECS/EKS) or locally with Docker Compose or Kubernetes, integrate SDKs across languages (Python, Node, React, Go, Java, .NET, React Native, etc.), and run A/B experiments with OpenTelemetry monitoring.
Guidance for deploying FeatBit on AWS, including ECS Fargate, EKS (Kubernetes), and Terraform. Use when user asks about deploying or running FeatBit on AWS. Do not use for Docker Compose deployments or Kubernetes deployments on non-AWS clouds.
Expert guidance for deploying FeatBit with Docker Compose across three tiers - Standalone (PostgreSQL only), Standard (PostgreSQL/MongoDB + Redis), and Professional (+ ClickHouse + Kafka). Use when user mentions "docker-compose", "deploy with Docker", "standalone vs standard vs pro", works with docker-compose.yml files, or asks about container configuration, environment variables, or production Docker setup. Do not use for Kubernetes, Helm, AWS ECS/EKS, or cloud-provider-specific deployments.
Deploys FeatBit to Kubernetes using Helm Charts. Use when user mentions "Kubernetes", "Helm", "K8s", "kubectl", works with values.yaml files, asks about "cloud deployment", "Azure Kubernetes", "AKS", "EKS", "GKE", "ingress", or needs production-grade container orchestration setup. Do not use for Docker Compose deployments or AWS-specific Terraform questions.
FeatBit documentation router that provides likely relevant docs.featbit.co URLs when other FeatBit skills cannot fully answer. Use when user asks about FeatBit features, concepts, deployment, SDKs, API, integrations, or architecture and the response should point to official documentation for deeper detail. Do not use when another FeatBit skill already provides a complete answer.
Expert guidance for using FeatBit's Flag Evaluation REST API and Track Insights REST API to build custom SDKs for platforms without an official FeatBit SDK. Use when user asks about "evaluation API", "flag evaluation endpoint", "evaluate feature flags via HTTP", "track insights", "insight tracking API", "build custom SDK", "Kotlin SDK", "Android SDK", "iOS SDK", "Swift SDK", "Unity SDK", "embedded SDK", "mobile feature flags", "sendToExperiment", or needs to call FeatBit evaluation server directly. Do not use for management API operations (projects, environments, flag CRUD) — use featbit-rest-api for those. Do not use when an official SDK exists for the target language.
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
Agent Skills compatible with Claude Code, Cursor, GitHub Copilot, Windsurf, and other tools supported by skills.sh.
Skills, deployment guides, and SDK integration knowledge for AI coding agents working with FeatBit — an open-source feature flags and A/B testing platform.
General-purpose coding agents know how to write application code, but they usually do not know FeatBit-specific terminology, deployment tradeoffs, or which official resource is authoritative for a given task.
This collection gives agents focused, low-noise guidance for the exact FeatBit workflow in front of them: choose the right SDK, deploy the platform, call the management APIs, or route to the right documentation page without loading unrelated context.
| 18 Skills | SDK integration, deployment, API, experimentation, and platform knowledge |
| 7 Languages | .NET, Node.js, Python, Java, Go, JavaScript, React / React Native |
| 3 Deployment targets | Docker Compose, Kubernetes/Helm, AWS ECS Fargate |
Use skills selectively. Loading all skills when only one is relevant wastes context tokens and dilutes agent attention.
| Category | Skill | Description |
|---|---|---|
| Platform | featbit-getting-started | First-run guide for onboarding, initial feature flags, and SDK handoff |
| Platform | featbit-documentation | Routes unanswered questions to the most relevant official FeatBit docs |
| Platform | featbit-opentelemetry | Configures FeatBit metrics, traces, and logs with OpenTelemetry |
| API | featbit-rest-api | Manages projects, environments, and feature flags via FeatBit REST APIs |
| API | featbit-evaluation-insights-api | Calls evaluation and track-insights APIs for custom SDKs and unsupported platforms |
| API | featbit-experimentation | Instruments flag exposures and metric events for FeatBit A/B tests and experimentation analysis |
| Deployment | featbit-deployment-docker | Deploys FeatBit with Docker Compose across Standalone, Standard, and Professional tiers |
| Deployment | featbit-deployment-kubernetes | Deploys FeatBit to Kubernetes with Helm across managed and self-managed clusters |
| Deployment | featbit-deployment-aws | Deploys FeatBit on AWS with ECS Fargate, ALB, and Terraform patterns |
| SDK Router | featbit-sdks | Routes FeatBit SDK questions to the correct language-specific skill |
| Server SDK | featbit-sdks-dotnet | Integrates the FeatBit .NET Server SDK with C# and ASP.NET Core applications |
| Server SDK | featbit-sdks-node | Integrates the FeatBit Node.js Server SDK in backend JavaScript or TypeScript services |
| Server SDK | featbit-sdks-python | Integrates the FeatBit Python Server SDK in backend Python applications |
| Server SDK | featbit-sdks-java | Integrates the FeatBit Java Server SDK in JVM backend services |
| Server SDK | featbit-sdks-go | Integrates the FeatBit Go Server SDK in Go services and APIs |
| Client SDK | featbit-sdks-javascript | Integrates the FeatBit JavaScript Client SDK in browser applications |
| Client SDK | featbit-sdks-react | Integrates the FeatBit React Client SDK with React and Next.js frontends |
| Client SDK | featbit-sdks-react-native | Integrates the FeatBit React Native SDK in React Native and Expo apps |
Prerequisite: Node.js v16+ is required to run
npx.
npx skills add featbit/featbit-skills
The wizard will detect your installed AI agents (Claude Code, Cursor, GitHub Copilot, Windsurf, etc.) and let you select which skills to install. No configuration needed.
# Install specific skills only
npx skills add featbit/featbit-skills --skill featbit-sdks-dotnet --skill featbit-deployment-docker
# Install to a specific agent
npx skills add featbit/featbit-skills -a claude-code
# List all available skills without installing
npx skills add featbit/featbit-skills --list
npx claudepluginhub joshuarweaver/cascade-code-devops-misc-1 --plugin featbit-featbit-skillsLaunchDarkly agent skills and MCP servers for feature flag management, AgentControl, and metrics
DevsForge Enterprise Feature Flag Architect delivering comprehensive progressive rollout methodologies, A/B testing frameworks, canary deployment strategies, and experimentation platforms that transform risky releases into controlled, data-driven feature delivery systems
Claude Code skill pack for PostHog (24 skills)
PROACTIVELY use this agent when experiments are started, modified, or when results need analysis. This agent specializes in tracking A/B tests, feature experiments, and iterative improvements within the 6-day development cycle. Should be triggered automatically when experimental code paths or feature flags are introduced. Examples:\n\n<example>\nContext: When implementing feature flags or A/B test variants\nuser: "Add a feature flag to test the new onboarding flow"\nassistant: "I've implemented the feature flag for the onboarding flow A/B test. Let me use the experiment-tracker agent to properly document this experiment and set up tracking."\n<commentary>\nEvery feature flag represents an experiment that needs proper tracking and success metrics.\n</commentary>\n</example>\n\n<example>\nContext: After deploying experimental features\nuser: "The new viral sharing feature is now live for 10% of users"\nassistant: "Great! The viral sharing feature is deployed. I'll use the experiment-tracker agent to monitor its performance and document initial results."\n<commentary>\nLive experiments need immediate tracking setup to capture valuable data from the start.\n</commentary>\n</example>\n\n<example>\nContext: When reaching experiment milestones\nuser: "It's been a week since we launched the TikTok integration test"\nassistant: "Perfect timing for analysis. Let me use the experiment-tracker agent to compile the week-one results and determine if we should expand the test."\n<commentary>\nRegular experiment checkpoints ensure data-driven decisions about feature rollouts.\n</commentary>\n</example>\n\n<example>\nContext: Before making product decisions\nuser: "Should we keep the AI avatar feature or remove it?"\nassistant: "Let me analyze the experiment data to inform this decision. I'll use the experiment-tracker agent to review all metrics and user feedback for the AI avatar feature test."\n<commentary>\nProduct decisions should be backed by experiment data, not gut feelings.\n</commentary>\n</example>
Ship features end-to-end with launch checklists and rollout plans
End-to-end feature orchestration with testing, security, performance, and deployment