Agent skill · software engineering · jeremylongshore

mistral-install-auth

Establish Mistral API access with server-side credentials, workspace ownership, and revocation evidence. Use when installing or auditing a Mistral environment. Trigger with "set up Mistral", "configure a Mistral key", or "audit Mistral authentication".

Why this skill is useful

Adds specific installation commands and authentication setup for the Mistral AI SDK that the AI wouldn't reliably generate on its own.

What it needs

Requires node, npm, pip, 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 Authentication and Installation Overview Create a reviewable authentication boundary before any inference call. Separate workspace access, secret custody, application authorization, and billing so possession of a key never implies permission to spend or process arbitrary data. Prerequisites A named workspace administrator, application owner, and spend owner. An approved server-side secret manager and environment-specific rollback route. A runtime and official client selected from current first-party documentation. Current Contract Mistral API requests use Bearer authentication at https://api.mistral.ai. Studio-created keys are displayed once. Free mode can include usage; current billing and limits must be read from the account rather than encoded. Authentication Store the credential as MISTRALAPIKEY and send it only in the Authorization: Bearer header from a trusted server. Never place it in source, browser bundles, URLs, prompts, logs, screenshots, fixtures, or support archives. Instructions 1. Inventory the workspace, runtime, environment, data class, volume, and accountable owners. 2. Confirm the administrator permitted to create and revoke an environment-scoped key. 3. Capture the one-time key directly into the approved secret manager and configure only its reference. 4. Pin the client dependency and API host without recording the secret value. 5. Validate configuration offline; request approval before one synthetic live call. 6. Record ownership, creation date, rotation route, live-check receipt, and rollback readiness. 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. …

How to use it

Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:

@skills jeremylongshore/mistral-install-auth--05011e

View the source on GitHub

Browse the @skills marketplace