Agent skill · software engineering · jeremylongshore
mistral-reference-architecture
Design a Mistral integration from policy gateway through adapter, queues, state reconciliation, and audited output. Use when establishing architecture. Trigger with "design a Mistral architecture", "review a Mistral platform", or "standardize Mistral services".
Why this skill is useful
Adds a complete reference architecture with executable code examples and best practices for Mistral AI integrations that the AI wouldn't generate on its own.
What it needs
Requires @mistralai/mistralai, typescript, vitest, zod installed locally. About 2k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Mistral Governed Reference Architecture Overview Create a workload-aware architecture separating identity, policy, transport, state, and side effects. Route each job to the simplest stable surface and isolate preview/stateful APIs. Prerequisites A workload inventory for chat, embeddings, classifiers, files/OCR, audio, batch, FIM, and orchestration. Identity, tenant, data, retention, spend, SLO, and incident requirements. Current endpoint/model evidence and owners for stateful stores. Current Contract Mistral exposes distinct stateless and stateful surfaces including chat, embeddings, classifiers, files, OCR, audio, batch, Workflows, and Public Preview Agents/Conversations. Their contracts are not interchangeable. Authentication Terminate app identity/authorization at a policy gateway; inject provider keys only in trusted adapters. Use approved service identity patterns when supported. Instructions 1. Map each workload to data class, latency, state, side effects, endpoint, and stability. 2. Place auth, tenancy, moderation, budgets, and bounds in the gateway. 3. Isolate provider calls behind typed adapters and preview APIs behind versioned boundaries. 4. Use queues/idempotency for async work; reconcile Files, Batch, Workflows, and app state. 5. Store approved data with tenant keys, provenance, retention, deletion, and audit. 6. Define observability, failure modes, rollout, rollback, provider exit, and test ownership. Tool Discipline Use Read, Glob, and Grep to inspect code, locks, configuration, tests, and evidence. Use Write and Edit only for approved repository changes. Invocation alone does not authorize network calls, paid usage, uploads, stateful resources, admin mutations, deployments, or deletion. Approval Boundaries Preview selection, uploads, persistent stores, tools, infrastructure, and live traffic require approval. Architecture review alone does not provision or mutate any component. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/mistral-reference-architecture--32e74f