Groq Production Checklist

VerifiedCaution

Complete checklist for deploying Groq integrations to production, including rollback procedures.

Sby Skills Guide Bot
DevOpsIntermediate
7/25/2026
Claude Code
#groq#deployment#rollback#kubernetes#production-checklist

Recommended for

Automated summary

This skill walks through deploying a Groq integration to production using a sequential checklist covering configuration, code quality, infrastructure, documentation, and a gradual rollout with rollback.

Strengths

  • Actionable five-step checklist from API key handling through canary deployment
  • Ready-to-run kubectl commands for staged rollout (10%, 50%, 100%) and immediate rollback
  • Error handling table mapping alert conditions to severity levels
  • Includes a TypeScript health check example that reports Groq connectivity and latency

Limitations

  • Assumes an existing Kubernetes setup and deployment pipeline
  • Does not ship full automation scripts; the checklist must be executed manually
  • Alert thresholds and canary wait times are generic and need tuning per service
When to use it

Use it when shipping a staging-verified Groq integration to production and preparing rollback and incident procedures.

When not to use it

Avoid it for local development environments or when your goal is upgrading to a newer Groq SDK version, which belongs to the upgrade skill.

Security analysis

Caution
Quality score76/100

The skill is a deployment runbook: kubectl and curl usage is legitimate and scoped to rollout, health-check, and rollback operations. There is no exfiltration, obfuscation, credential reading, or destructive filesystem command, and the curl examples only touch a staging health endpoint and Groq's public status page. Risk comes solely from the broad kubectl/curl tool grants, which can materially alter a production cluster if run against the wrong context, so 'caution' rather than 'safe' or 'risky'.

Findings
  • •Declares Bash(kubectl:*) allowing arbitrary cluster mutations against whatever context is active (apply, set image, rollout resume/undo)
  • •Declares Bash(curl:*) allowing outbound network requests to arbitrary URLs, though examples only hit staging health and status.groq.com
  • •Canary/rollout steps run unattended with `sleep` gates and no verification command, so a wrong kube-context could push changes to production
How this analysis is made

Examples

Go-live checklist
Run the Groq production go-live checklist for our integration — we've finished staging testing and need to verify keys, monitoring, and rollback docs before launch.
Gradual canary rollout
Deploy the groq-integration to production with a gradual canary rollout: 10% first, check error rates and latency, then continue to 100%.
Emergency rollback
We're seeing 5xx errors from Groq in production — walk me through rolling back the groq-integration deployment and verifying the rollback status.

name: groq-prod-checklist description: | Execute Groq production deployment checklist and rollback procedures. Use when deploying Groq integrations to production, preparing for launch, or implementing go-live procedures. Trigger with phrases like "groq production", "deploy groq", "groq go-live", "groq launch checklist". allowed-tools: Read, Bash(kubectl:), Bash(curl:), Grep version: 1.0.0 license: MIT author: Jeremy Longshore jeremy@intentsolutions.io

Groq Production Checklist

Overview

Complete checklist for deploying Groq integrations to production.

Prerequisites

  • Staging environment tested and verified
  • Production API keys available
  • Deployment pipeline configured
  • Monitoring and alerting ready

Instructions

Step 1: Pre-Deployment Configuration

  • [ ] Production API keys in secure vault
  • [ ] Environment variables set in deployment platform
  • [ ] API key scopes are minimal (least privilege)
  • [ ] Webhook endpoints configured with HTTPS
  • [ ] Webhook secrets stored securely

Step 2: Code Quality Verification

  • [ ] All tests passing (npm test)
  • [ ] No hardcoded credentials
  • [ ] Error handling covers all Groq error types
  • [ ] Rate limiting/backoff implemented
  • [ ] Logging is production-appropriate

Step 3: Infrastructure Setup

  • [ ] Health check endpoint includes Groq connectivity
  • [ ] Monitoring/alerting configured
  • [ ] Circuit breaker pattern implemented
  • [ ] Graceful degradation configured

Step 4: Documentation Requirements

  • [ ] Incident runbook created
  • [ ] Key rotation procedure documented
  • [ ] Rollback procedure documented
  • [ ] On-call escalation path defined

Step 5: Deploy with Gradual Rollout

# Pre-flight checks
curl -f https://staging.example.com/health
curl -s https://status.groq.com

# Gradual rollout - start with canary (10%)
kubectl apply -f k8s/production.yaml
kubectl set image deployment/groq-integration app=image:new --record
kubectl rollout pause deployment/groq-integration

# Monitor canary traffic for 10 minutes
sleep 600
# Check error rates and latency before continuing

# If healthy, continue rollout to 50%
kubectl rollout resume deployment/groq-integration
kubectl rollout pause deployment/groq-integration
sleep 300

# Complete rollout to 100%
kubectl rollout resume deployment/groq-integration
kubectl rollout status deployment/groq-integration

Output

  • Deployed Groq integration
  • Health checks passing
  • Monitoring active
  • Rollback procedure documented

Error Handling

| Alert | Condition | Severity | |-------|-----------|----------| | API Down | 5xx errors > 10/min | P1 | | High Latency | p99 > 5000ms | P2 | | Rate Limited | 429 errors > 5/min | P2 | | Auth Failures | 401/403 errors > 0 | P1 |

Examples

Health Check Implementation

async function healthCheck(): Promise<{ status: string; groq: any }> {
  const start = Date.now();
  try {
    await groqClient.ping();
    return { status: 'healthy', groq: { connected: true, latencyMs: Date.now() - start } };
  } catch (error) {
    return { status: 'degraded', groq: { connected: false, latencyMs: Date.now() - start } };
  }
}

Immediate Rollback

kubectl rollout undo deployment/groq-integration
kubectl rollout status deployment/groq-integration

Resources

Next Steps

For version upgrades, see groq-upgrade-migration.

From the file to a first result

The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.

View the source and supporting files

This download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.

1. Download the file

Download SKILL.md

From the root of a test project, save the file as .skill-downloads/groq-production-checklist-mrzxuqs3/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.

Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.

mkdir -p '.skill-downloads/groq-production-checklist-mrzxuqs3' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/groq-production-checklist-mrzxuqs3/download' --output '.skill-downloads/groq-production-checklist-mrzxuqs3/SKILL.md.part' && mv '.skill-downloads/groq-production-checklist-mrzxuqs3/SKILL.md.part' '.skill-downloads/groq-production-checklist-mrzxuqs3/SKILL.md'

2. Check prerequisites

Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.

Tools declared by the author (check availability in your agent): Read, Bash(kubectl:*), Bash(curl:*), Grep

Original excerpt: Prerequisites
  • Staging environment tested and verified
  • Production API keys available
  • Deployment pipeline configured
  • Monitoring and alerting ready

The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.

3. Load the skill

After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.

Claude Code
test -f '.skill-downloads/groq-production-checklist-mrzxuqs3/SKILL.md' && test -s '.skill-downloads/groq-production-checklist-mrzxuqs3/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/groq-prod-checklist' && cp -R '.skill-downloads/groq-production-checklist-mrzxuqs3' '.claude/skills/groq-prod-checklist'

OpenSkills

OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.

Official OpenSkills installation
openskills install './.skill-downloads/groq-production-checklist-mrzxuqs3'

openskills read 'groq-production-checklist-mrzxuqs3'

Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.

For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.

openskills sync

Manual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.

4. Try a first task

Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:

Read .skill-downloads/groq-production-checklist-mrzxuqs3/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.

Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.

Related skills