mistral-prod-checklist
A deployment checklist for Mistral AI apps, covering security, resilience, and rollback procedures.
Install
mkdir -p .claude/skills/mistral-prod-checklist && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/6897" && unzip -o skill.zip -d .claude/skills/mistral-prod-checklist && rm skill.zipInstalls to .claude/skills/mistral-prod-checklist
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Execute Mistral AI production deployment checklist and rollback procedures.Key capabilities
- →Verify production API keys and model configurations
- →Ensure code quality gates pass before deployment
- →Implement a health check endpoint for Mistral AI services
- →Integrate a circuit breaker for resilience against API failures
- →Perform gradual rollouts and emergency rollbacks
How it works
This skill provides a checklist and code examples for deploying Mistral AI integrations to production, covering credential verification, code quality, health monitoring, resilience patterns, and deployment strategies.
Inputs & outputs
When to use mistral-prod-checklist
- →Verify production credentials
- →Check error handling and backoff patterns
- →Perform production health checks
- →Prepare rollback procedures
About this skill
Mistral AI Production Checklist
Overview
Complete checklist for deploying Mistral AI integrations to production. Covers credential management, code quality gates, health endpoints, circuit breaker resilience, gradual rollout, and rollback procedures.
Prerequisites
- Staging environment tested and verified
- Production API keys from La Plateforme
- Deployment pipeline (CI/CD) configured
- Monitoring and alerting ready (see
mistral-observability)
Instructions
Step 1: Pre-Deployment Verification
Credentials
- Production API key stored in secret manager (never in env files or code)
- Key tested with
curl -H "Authorization: Bearer $KEY" https://api.mistral.ai/v1/models - Key has appropriate model access scope
- Fallback key available for rotation
Code Quality
-
npm run typecheckpasses -
npm testpasses (unit + integration) - No hardcoded keys:
grep -r "MISTRAL_API_KEY\|sk-" src/ --include="*.ts" - Error handling covers 401, 429, 500+ status codes
- Rate limiting/backoff implemented
- Logging excludes message content and API keys
Model Configuration
- Using versioned model IDs or
-latestaliases intentionally -
maxTokensset to prevent runaway costs -
temperatureset appropriately (0 for deterministic, 0.7 for creative) - Token budget alerts configured
Step 2: Health Check Endpoint
import { Mistral } from '@mistralai/mistralai';
interface HealthStatus {
status: 'healthy' | 'degraded' | 'unhealthy';
provider: 'mistral';
latencyMs: number;
model?: string;
error?: string;
}
export async function checkHealth(): Promise<HealthStatus> {
const start = performance.now();
try {
const client = new Mistral({ apiKey: process.env.MISTRAL_API_KEY! });
const models = await client.models.list();
const latencyMs = Math.round(performance.now() - start);
return {
status: latencyMs > 5000 ? 'degraded' : 'healthy',
provider: 'mistral',
latencyMs,
model: models.data?.[0]?.id,
};
} catch (error: any) {
return {
status: 'unhealthy',
provider: 'mistral',
latencyMs: Math.round(performance.now() - start),
error: error.message,
};
}
}
// Express route
app.get('/health', async (req, res) => {
const health = await checkHealth();
res.status(health.status === 'unhealthy' ? 503 : 200).json(health);
});
Step 3: Circuit Breaker
class MistralCircuitBreaker {
private failures = 0;
private lastFailure = 0;
private state: 'closed' | 'open' | 'half-open' = 'closed';
private readonly threshold = 5;
private readonly resetMs = 60_000;
async execute<T>(fn: () => Promise<T>, fallback?: () => T): Promise<T> {
if (this.state === 'open') {
if (Date.now() - this.lastFailure > this.resetMs) {
this.state = 'half-open';
} else if (fallback) {
return fallback();
} else {
throw new Error('Circuit breaker open — Mistral unavailable');
}
}
try {
const result = await fn();
if (this.state === 'half-open') {
this.state = 'closed';
this.failures = 0;
}
return result;
} catch (error: any) {
if (error.status >= 500 || error.status === 429) {
this.failures++;
this.lastFailure = Date.now();
if (this.failures >= this.threshold) {
this.state = 'open';
}
}
throw error;
}
}
}
Step 4: Gradual Rollout
set -euo pipefail
# Deploy to canary (10% traffic)
kubectl set image deployment/mistral-app app=mistral-app:v2
kubectl rollout pause deployment/mistral-app
# Monitor for 10 minutes
echo "Monitoring canary..."
for i in $(seq 1 10); do
curl -sf https://yourapp.com/health | jq '.services.mistral'
sleep 60
done
# If healthy, resume rollout
kubectl rollout resume deployment/mistral-app
kubectl rollout status deployment/mistral-app
Step 5: Post-Deployment Verification
set -euo pipefail
# 1. Health check
curl -sf https://yourapp.com/health | jq '.'
# 2. Smoke test
curl -X POST https://yourapp.com/api/chat \
-H "Content-Type: application/json" \
-d '{"messages":[{"role":"user","content":"ping"}]}' | jq '.choices[0].message.content'
# 3. Check error rate in monitoring
echo "Check Grafana/Datadog for mistral_errors_total"
Step 6: Emergency Rollback
set -euo pipefail
# Immediate rollback
kubectl rollout undo deployment/mistral-app
kubectl rollout status deployment/mistral-app
# Verify
curl -sf https://yourapp.com/health | jq '.'
Alert Configuration
| Alert | Condition | Severity |
|---|---|---|
| API Down | 5xx errors > 10/min | P1 |
| High Latency | p95 > 5000ms for 5min | P2 |
| Rate Limited | 429 errors > 5/min | P2 |
| Auth Failure | Any 401 error | P1 |
| Circuit Open | Breaker triggered | P2 |
| Cost Spike | Spend > $10/hour | P3 |
Documentation Requirements
- Incident runbook created (see
mistral-incident-runbook) - Key rotation procedure documented
- Rollback procedure tested
- On-call escalation path defined
- API usage limits documented
Output
- Production deployment with verified credentials
- Health check endpoint with latency monitoring
- Circuit breaker for graceful degradation
- Gradual rollout procedure
- Emergency rollback tested
Error Handling
| Issue | Detection | Resolution |
|---|---|---|
| Deploy failure | kubectl rollout status | kubectl rollout undo |
| Health check 503 | Alert triggered | Check Mistral status, verify credentials |
| Circuit open | Metrics alert | Investigate availability, wait for reset |
| High error rate | Monitoring alert | Check logs, consider rollback |
Resources
Prerequisites
Limitations
- →Deployment failures can occur during rollout
- →Health check 503 errors indicate issues with Mistral status or credentials
- →Circuit open state prevents requests to Mistral AI
How it compares
This skill offers a structured, production-ready deployment and operational framework for Mistral AI, providing more reliability than a basic deployment.
Compared to similar skills
mistral-prod-checklist side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| mistral-prod-checklist (this skill) | 1 | 27d | Caution | Advanced |
| apollo-prod-checklist | 1 | 27d | Caution | Intermediate |
| electron-pro | 0 | 4mo | No flags | Advanced |
| electron-development | 0 | 4mo | Review | Advanced |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by jeremylongshore
View all by jeremylongshore →You might also like
apollo-prod-checklist
jeremylongshore
Execute Apollo.io production deployment checklist. Use when preparing to deploy Apollo integrations to production, doing pre-launch verification, or auditing production readiness. Trigger with phrases like "apollo production checklist", "deploy apollo", "apollo go-live", "apollo production ready", "apollo launch checklist".
electron-pro
jshsakura
Use when a task needs Electron-specific implementation or debugging across main/renderer/preload boundaries, packaging, and desktop runtime behavior.
electron-development
wegonbeok45
Master Electron desktop app development with secure IPC, contextIsolation, preload scripts, multi-process architecture, electron-builder packaging, code signing, and auto-update.
cloudflare-manager
qdhenry
Comprehensive Cloudflare account management for deploying Workers, KV Storage, R2, Pages, DNS, and Routes. Use when deploying cloudflare services, managing worker containers, configuring KV/R2 storage, or setting up DNS/routing. Requires CLOUDFLARE_API_KEY in .env and Bun runtime with dependencies installed.
azure-functions
aj-geddes
Create serverless functions on Azure with triggers, bindings, authentication, and monitoring. Use for event-driven computing without managing infrastructure.
flow-nexus-platform
ruvnet
Comprehensive Flow Nexus platform management - authentication, sandboxes, app deployment, payments, and challenges