release-health-dashboard-review
Design and audit release health dashboards, rollout gates, canary metrics, crash/error monitoring, support signals, store release status, desktop auto-update adoption, rollback triggers, and post-release review for apps, SaaS, games, web, and desktop software. Use when launching releases, patches, experiments, or staged rollouts that need operational confidence.
Works with
--- name: release-health-dashboard-review description: Design and audit release health dashboards, rollout gates, canary metrics, crash/error monitoring, support signals, store release status, desktop auto-update adoption, rollback triggers, and post-release review for apps, SaaS, games, web, and desktop software. Use when launching releases, patches, experiments, or staged rollouts that need operational confidence. license: MIT --- # Release Health Dashboard Review Use this skill to turn a recurring product-operations problem into a concrete, reviewable artifact instead of generic advice. ## Workflow 1. Identify release type, audience, platform/channel, rollout mechanism, critical user journeys, and rollback capability. 2. Read `references/release-health-patterns.md`. 3. Define leading and lagging health signals across reliability, conversion, payments, support, reviews, and adoption. 4. Set gates for preflight, canary/staged rollout, expansion, hold, rollback, and post-release learning. 5. Produce dashboard spec, alert thresholds, owner rotation, and release decision table. ## When not to use - Do not use for generic advice the base model already handles without this skill's specific artifact contract. ## Guardrails - Do not rely on green deploy/build status as user health proof. - Do not average away platform, version, region, plan, or device-specific regressions. - Every rollback trigger needs an owner, communication path, and recovery check. - Use store review and auto-update constraints when release rollback is not instant. ## Output format ```text Release context: Platform / rollout / rollback capability: Dashboard spec: | Signal | Baseline | Threshold | Segment | Owner | Action | | --- | --- | --- | --- | --- | --- | Gate decision table: - <gate> -> <ship/hold/expand/rollback condition> Post-release review: - <learning, follow-up, docs/support update> ```
More Deployment & CI/CD skills
azure-enterprise-infra-planner
microsoft/azure-skills
Architect and provision enterprise Azure infrastructure from workload descriptions. For cloud architects and platform engineers planning networking, identity, security, compliance, and multi-resource topologies with WAF alignment. Generates Bicep or Terraform directly (no azd). WHEN: 'plan Azure infrastructure', 'architect Azure landing zone', 'design hub-spoke network', 'plan multi-region DR topology', 'set up VNets firewalls and private endpoints', 'subscription-scope Bicep deployment', 'Azure Backup for VM workloads'. PREFER azure-prepare FOR app-centric workflows.
azure-kubernetes-app-deploy
microsoft/azure-skills
Use when deploying an existing web application or API to an already-running Azure Kubernetes Service cluster. Detects the framework, generates a Dockerfile and Kubernetes manifests, validates against AKS Deployment Safeguards, and deploys with verification. WHEN: deploy app to AKS, deploy to existing AKS cluster, containerize app for Kubernetes, generate K8s manifests for Azure, set up CI/CD for AKS, my AKS deployment is failing safeguard checks, I have a Django/Express/Spring Boot app to run on AKS. DO NOT USE FOR: creating or provisioning an AKS cluster (use azure-kubernetes), assessing migration to AKS Automatic (use azure-kubernetes-automatic-readiness), or deploying to non-AKS targets like Web Apps, Container Apps, or Functions.
finetuning
microsoft/azure-skills
Fine-tune models on Microsoft Foundry using SFT (supervised), DPO (preference), or RFT (reinforcement with graders). Covers dataset preparation, training job submission, deployment, and evaluation. USE FOR: fine-tune, SFT, DPO, RFT, training data, grader, distillation, fine-tuned model, training job, large file upload, calibrate grader, deploy fine-tuned model, evaluate fine-tuned model. DO NOT USE FOR: general model deployment without fine-tuning (use deploy-model), agent creation (use agents), prompt optimization without training (use prompt-optimizer).
