Agent skill · marketing growth · jeremylongshore
cohere-data-handling
Govern data sent to Cohere with classification, minimization, tenant controls, redaction, retention mapping, and contractual evidence. Use when processing sensitive or regulated data. Trigger with "Cohere privacy", "Cohere PII", or "Cohere data retention".
Why this skill is useful
Provides specific PII redaction patterns and compliance workflows for Cohere API that the AI wouldn't reliably generate on its own.
What it needs
Requires cohere-ai installed locally. About 2k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Cohere Data Handling and Privacy Overview Decide what may cross the provider boundary from the signed agreement and application purpose, then enforce that decision before each request. Prerequisites The target repository, runtime, environment, and accountable owner An approved Cohere team and key for any live verification Current quality, security, privacy, capacity, and change-control requirements Tool Discipline Use Read, Glob, and Grep to inspect code, configuration, and evidence. Use WebFetch only for current Cohere primary documentation. Use Write or Edit only when the user requested implementation and the exact target files are known; never write credentials or customer content. Current Contract Cohere's public privacy policy distinguishes enterprise Customer Data from general personal information and points to enterprise commitments. Do not infer retention, residency, training use, deletion, or subprocessors from a generic policy when a contract governs the workload. Embeddings and logs can encode sensitive information even when raw text is absent. Data minimization and tenant authorization must happen before Chat, Embed, Rerank, or tool calls. Authentication Use an environment-specific key injected from an approved secret manager. Never print, persist, commit, or place COAPIKEY in an example. Confirm access with the least costly bounded operation appropriate to the task, and treat key creation, rotation, revocation, role changes, and production-capacity requests as owner-approved actions. Instructions 1. Classify inputs, retrieved documents, outputs, embeddings, logs, and tool data by tenant and jurisdiction. 2. Map each data class to the signed terms, approved region, retention, deletion, access, and incident requirements. 3. Block disallowed classes and minimize, tokenize, or redact approved inputs before the provider call. 4. Apply tenant filters before retrieval and keep document identifiers safe for citation auditing. 5. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/cohere-data-handling