MI

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.zip

Installs 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.
75 charsno explicit “when” trigger
Advanced

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

You give it
Deployment commands, API keys, code quality checks, health check requests
You get back
Verified production deployment, health status, circuit breaker state, rollout status

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 typecheck passes
  • npm test passes (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 -latest aliases intentionally
  • maxTokens set to prevent runaway costs
  • temperature set 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

AlertConditionSeverity
API Down5xx errors > 10/minP1
High Latencyp95 > 5000ms for 5minP2
Rate Limited429 errors > 5/minP2
Auth FailureAny 401 errorP1
Circuit OpenBreaker triggeredP2
Cost SpikeSpend > $10/hourP3

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

IssueDetectionResolution
Deploy failurekubectl rollout statuskubectl rollout undo
Health check 503Alert triggeredCheck Mistral status, verify credentials
Circuit openMetrics alertInvestigate availability, wait for reset
High error rateMonitoring alertCheck logs, consider rollback

Resources

Prerequisites

Staging environment tested and verifiedProduction API keys from La PlateformeDeployment pipeline (CI/CD) configuredMonitoring and alerting ready (see `mistral-observability`)

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.

SkillInstallsUpdatedSafetyDifficulty
mistral-prod-checklist (this skill)127dCautionAdvanced
apollo-prod-checklist127dCautionIntermediate
electron-pro04moNo flagsAdvanced
electron-development04moReviewAdvanced

Try saying

Example prompts that trigger this skill in your AI assistant.

More by jeremylongshore

View all by jeremylongshore

analyzing-logs

jeremylongshore

Analyze application logs to detect performance issues, identify error patterns, and improve stability by extracting key insights.

14123

ollama-setup

jeremylongshore

Configure auto-configure Ollama when user needs local LLM deployment, free AI alternatives, or wants to eliminate hosted API costs. Trigger phrases: "install ollama", "local AI", "free LLM", "self-hosted AI", "replace OpenAI", "no API costs". Use when appropriate context detected. Trigger with relevant phrases based on skill purpose.

1167

backtesting-trading-strategies

jeremylongshore

Backtest crypto and traditional trading strategies against historical data. Calculates performance metrics (Sharpe, Sortino, max drawdown), generates equity curves, and optimizes strategy parameters. Use when user wants to test a trading strategy, validate signals, or compare approaches. Trigger with phrases like "backtest strategy", "test trading strategy", "historical performance", "simulate trades", "optimize parameters", or "validate signals".

1071

generating-database-seed-data

jeremylongshore

Process this skill enables AI assistant to generate realistic test data and database seed scripts for development and testing environments. it uses faker libraries to create realistic data, maintains relational integrity, and allows configurable data volumes. u... Use when working with databases or data models. Trigger with phrases like 'database', 'query', or 'schema'.

1033

cursor-codebase-indexing

jeremylongshore

Execute set up and optimize Cursor codebase indexing. Triggers on "cursor index setup", "codebase indexing", "index codebase", "cursor semantic search". Use when working with cursor codebase indexing functionality. Trigger with phrases like "cursor codebase indexing", "cursor indexing", "cursor".

885

testing-mobile-apps

jeremylongshore

Execute mobile app testing on iOS and Android devices/simulators. Use when performing specialized testing. Trigger with phrases like "test mobile app", "run iOS tests", or "validate Android functionality".

810

Search skills

Search the agent skills registry