Index of every page on this site: llms.txt
All skills
jeremylongshore avatar

/mistral-install-auth

@820dfc8
Run it yourself

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".

Use this Skill: https://skilld.dev/gh/jeremylongshore/tons-of-skills-marketplace/mistral-install-auth

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈69 tokens for metadata: the name and description. ≈789 when used: this file. ≈248 more on demand in 1 file.

Description uses 3.4% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈275 characters, or 3.4%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

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 MISTRAL_API_KEY 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.

Approval Boundaries

Require explicit approval for key creation or revocation, billing or role changes, live requests, deployments, or customer-derived content.

Error Handling

  • A 401 usually indicates a missing, malformed, revoked, or wrong-environment key.
  • A valid key can still fail because the workspace is suspended or at a current rate/spend boundary.
  • Any browser or log exposure is an incident: revoke, rotate consumers, and verify history removal.

Output

Return workspace, environment, secret-reference name, host, client pin, owner, validation state, evidence IDs, risks, and rollback. Exclude credentials and content.

Examples

  • Prepare a Python service with an injected production secret and no live request.
  • Report environment=staging; auth=Bearer; live_smoke=awaiting-approval.

Validation

Confirm host/header, scan tracked output for secrets, prove no browser exposure, and verify the owner can revoke the key.

Resources

  • Current first-party evidence map — recheck dated sources before relying on mutable endpoints, models, limits, prices, preview status, or retention.
  • Record live account observations as environment-specific evidence, not universal Mistral guarantees.

Source: SKILL.md on GitHub

No rule matched.

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

No alerts2mo3 checks · Risk SAFE
  • Gen Agent Trust Hub2mo

    This skill provides standard and secure instructions for installing the Mistral AI SDK and configuring authentication. It follows best practices by recommending environment variables, .env files, or official secret management services for API key handling.

  • Socket2mo

    No alerts

  • Snyk2mo

    Risk: LOW · No issues

Signed by skilld at 820dfc8. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub 20 hours ago.

Activeupdated 2 months ago
What it can do
Reads files Edits files
Modelinherit
argument-hint
<runtime> <workspace> <environment>
version
1.14.0
author
Jeremy Longshore <jeremy@intentsolutions.io>
All 5 allowed tools
ReadGlobGrepWriteEdit
Other metadata
tags
[
  "saas",
  "mistral",
  "authentication"
]
model
inherit
effort
high
compatibility
Designed for Claude Code; live or external Mistral actions require network access and explicit approval

README badge

README badge for jeremylongshore/tons-of-skills-marketplace/mistral-install-auth