Agent skill · software engineering · jeremylongshore
cohere-debug-bundle
Collect a minimal redacted Cohere diagnostic bundle with versions, request shape, timing, status, and reproduction evidence. Use when escalating a persistent Cohere problem. Trigger with "Cohere debug bundle", "Cohere support evidence", or "collect Cohere diagnostics".
Why this skill is useful
Adds an executable script for collecting comprehensive debug information specific to the Cohere API, which the AI cannot generate on its own.
What it needs
Requires cohere-ai, curl, jq installed locally. Requires cohere account access. About 2k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Cohere Support-Ready Debug Bundle Overview Produce evidence that support can act on without copying credentials, prompts, customer data, or an unrestricted environment dump. 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 Collect only allowlisted environment-variable names and redact values. Record endpoint, SDK/runtime versions, model ID, status, latency, retry count, and provider request identifier when available. Represent request and response structures with synthetic or hashed content. Keep the bundle local until a human approves its recipients and data classification. 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. Create a dedicated output directory with restrictive permissions and a retention deadline. 2. Capture runtime, SDK, lockfile, network path, timestamp, and Cohere status metadata. 3. Serialize a redacted request-shape summary and the smallest synthetic reproduction. 4. Include bounded probe output, application correlation ID, and sanitized stack trace. 5. Scan the bundle for key formats, authorization headers, emails, prompts, and customer identifiers. 6. Return the manifest and checksum for human review; do not transmit it automatically. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/cohere-debug-bundle--7a6a39