Agent skill · software engineering · jeremylongshore
mistral-hello-world
Validate one minimal Mistral chat request with pinned inputs, usage evidence, and zero sensitive data. Use when proving a new integration path. Trigger with "Mistral hello world", "test my Mistral setup", or "make a first Mistral request".
Why this skill is useful
Adds executable scripts for Mistral AI chat completions and demonstrates multi-turn conversation patterns not readily available in public documentation.
What it needs
Requires node, python 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 Bounded First Request Overview Prove the smallest useful chat path without turning a quickstart into production authority. Build offline, use synthetic text, capture content-free evidence, and stop after one approved response. Prerequisites A configured server-side MISTRALAPIKEY reference. A current model identifier selected from account-visible evidence. Approval for one billable request and a non-sensitive synthetic prompt. Current Contract The current chat surface is POST /v1/chat/completions. A request includes a model and messages; response and usage shapes come from the current endpoint schema. Model aliases and availability are mutable. Authentication Resolve the key only at runtime through the trusted client boundary. Do not print the key, headers, prompt, or response content in the receipt. Instructions 1. Inspect runtime and dependency lock before selecting the official client. 2. Resolve an allowed model dynamically; do not rely on an old price or context table. 3. Construct one deterministic message containing no secrets, personal data, or customer content. 4. Review parameters and maximum output before authorizing the live call. 5. Execute once after approval; record status, latency, returned model, finish reason, and usage. 6. Dispose of response content unless the approved plan explicitly retains the synthetic sample. 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 the live call, model, output bound, and retained response. Do not add retries, tools, files, or stateful resources. Error Handling 401 is a configuration problem, not a reason to reveal a credential. 429 requires current workspace evidence, not immediate repeated calls. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/mistral-hello-world--b84046