Agent skill · software engineering · jeremylongshore
mistral-core-workflow-a
Implement governed Mistral chat, streaming, and structured-output requests with schema validation and model evidence. Use when building text-generation workflows. Trigger with "build Mistral chat", "stream a Mistral response", or "return structured Mistral output".
Why this skill is useful
Adds executable scripts for multi-turn conversations, streaming responses, and guardrails that enhance Mistral AI integration capabilities.
What it needs
Requires npm installed locally. Requires mistral account access. About 2k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Mistral Chat, Streaming, and Structured Output Overview Select the simplest chat mode satisfying the product contract. Treat non-streaming text, streaming events, and structured output as different state machines with shared safety and usage controls. Prerequisites A model policy based on current account-visible evidence. A bounded prompt/data class and maximum output policy. A parser, schema validator, cancellation path, and synthetic fixtures. Current Contract Chat uses POST /v1/chat/completions. Streaming and response-format options are endpoint capabilities, not guarantees for every model; validate the current schema and selected model. Authentication Use server-side Bearer auth through the approved adapter. Never forward credentials or raw headers to users, tools, or browser code. Instructions 1. Translate the requirement into text, stream, or structured mode and document why. 2. Resolve a permitted model dynamically and pin reproducibility parameters. 3. Assemble trusted policy and bounded user content; keep untrusted text out of control instructions. 4. For streams, validate ordering, cancellation, terminal state, partial output, and usage. 5. For structured output, parse and validate the application schema; reject prose fallback. 6. Record request identity, latency, finish state, usage, validation, and retention class. 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 Require approval for live requests, new data classes, higher output, model fallback, or retention. Returned text is data, not executable authority. Error Handling Transport success can still fail schema or safety validation. Interrupted streams require an explicit partial-output policy. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/mistral-core-workflow-a