Agent skill

mistral-observability

Set up comprehensive observability for Mistral AI with metrics, traces, and alerts. Use when implementing monitoring for Mistral AI operations, setting up dashboards, or configuring alerting for integration health. Trigger with phrases like "mistral monitoring", "mistral metrics", "mistral observability", "monitor mistral", "mistral alerts". '

intentsolutions.io2,596★ · 1 repos on radarProfile →
claude-codecan modify filesMIT
Install
npx skills add jeremylongshore/claude-code-plugins-plus-skills --skill mistral-observability --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 1
SKILL.md size: 8 KB
Bundled scripts: none
Version: 1.12.0
Declared author: Jeremy Longshore <jeremy@intentsolutions.io>
Allowed tools: ReadWriteEdit
Requires: Designed for Claude Code, also compatible with Codex and OpenClaw
Path: plugins/saas-packs/mistral-pack/skills/mistral-observability/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 2,630
Language: Python
Read our review of the source →

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Mistral AI Observability ## Overview Monitor Mistral AI API usage, latency, token consumption, error rates, and costs. Covers instrumented client wrapper, Prometheus metrics, Grafana dashboard panels, alerting rules, and structured logging. ## Prerequisites - Mistral API integration in production - Prometheus or OpenTelemetry-compatible metrics backend - Alerting system (Alertmanager, PagerDuty, or similar) ## Instructions ### Step 1: Instrumented Client Wrapper ```typescript import { Mistral } from '@mistralai/mistralai'; const PRICING: Record<string, { input: number; output: number }> = { 'mistral-small-latest': { input: 0.10, output: 0.30 }, 'mistral-large-latest': { input: 0.50, output: 1.50 }, 'codestral-latest': { input: 0.30, output: 0.90 }, 'mistral-embed': { input: 0.10, output: 0 }, }; interface MetricsEvent { model: string; endpoint: string; durationMs: number; status: 'success' | 'error'; statusCode?: number; inputTokens?: number; outputTokens?: number; costUsd?: number; } function emitMetrics(event: MetricsEvent): void { // Push to your metrics backend (Prometheus, Datadog, etc.) console.log(JSON.stringify({ type: 'mistral_metric', ...event })); } async function inst

What's inside
Steps it walks through
  1. Overview
  2. Prerequisites
  3. Instructions
  4. Step 1: Instrumented Client Wrapper
  5. Step 2: Prometheus Metrics
  6. Step 3: Alerting Rules
  7. Step 4: Grafana Dashboard Panels
  8. Step 5: Structured Log Format
  9. Error Handling
  10. Resources
  11. Output
More from claude-code-plugins-plus-skills
All skills →
About this skill
What does the mistral-observability skill do?

Set up comprehensive observability for Mistral AI with metrics, traces, and alerts. Use when implementing monitoring for Mistral AI operations, setting up dashboards, or configuring alerting for integration health. Trigger with phrases like "mistral monitoring", "mistral metrics", "mistral observability", "monitor mistral", "mistral alerts". '

How do I install it?

Run `npx skills add jeremylongshore/claude-code-plugins-plus-skills --skill mistral-observability --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From jeremylongshore/claude-code-plugins-plus-skills, a repository with 2,630 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going