Agent skill · data analytics · jeremylongshore
mistral-data-handling
Govern Mistral prompts, outputs, embeddings, files, OCR, audio, batch, stateful resources, and deletion evidence. Use when sensitive or retained data is involved. Trigger with "Mistral data retention", "upload a file to Mistral", or "review Mistral privacy".
Why this skill is useful
Adds executable scripts for PII redaction and GDPR compliance that are specific to Mistral AI integrations.
What it needs
Requires @mistralai/mistralai 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 Data Lifecycle Governance Overview Map every data class through provider transit, app storage, derived artifacts, state, retention, and deletion. Never infer privacy from one endpoint or account feature. Prerequisites A data inventory, lawful purpose, tenant boundary, retention requirements, and privacy owner. Current endpoint/account evidence including ZDR applicability. Deletion, subject-request, incident, and derived-data policies. Current Contract ZDR covers supported stateless paid-plan calls but excludes stateful products/APIs including Agents, Batch processing files, Conversations, Libraries, and /v1/files. Each workload needs review. Authentication Authorize data independently of the provider key. Never put credentials or customer content in logs, receipts, or diagnostics. Instructions 1. Classify prompts, outputs, embeddings, files, transcripts, OCR, batch artifacts, state IDs, and derived records. 2. Map endpoint, account controls, transit, provider state, app stores, logs, backups, and subprocessors. 3. Verify ZDR for the exact stateless operation; mark excluded/unknown stateful surfaces. 4. Minimize/redact, isolate tenants, bound purpose/retention, and authorize before transmission. 5. Track resource IDs and derived artifacts for cross-system deletion reconciliation. 6. Test access, expiry, deletion, restore/backups, subject requests, and incident evidence. 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 Sensitive data, uploads, batch/stateful use, retention, region changes, training/fine-tuning, and deletion require privacy/security approval. Deprecated fine-tuning docs do not establish a current supported workflow. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/mistral-data-handling--82fedc