Skip to content
Skills Library
AI & agents · Analysis

cohere-debug-bundle

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

Licence
MIT
Last repository change
26.10.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
2
Scripts
0
HTML comments
0
URLs in SKILL.md
2
Deprecation

No signals detected. Repository changed on 26.10.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

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

Triggers from the description

Cohere debug bundleCohere support evidencecollect Cohere diagnostics

Arguments

/cohere-debug-bundle [incident-id] [output-directory]
Original author description

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

How it works

  1. Overview
  2. Prerequisites
  3. Tool Discipline
  4. Current Contract
  5. Authentication
  6. Instructions
  7. Approval Boundaries
  8. Output
  9. Error Handling
  10. Examples
Original SKILL.md headings · 75 lines, 479 words
SKILL.md preview
---
name: cohere-debug-bundle
description: >-
  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".
argument-hint: "[incident-id] [output-directory]"
allowed-tools: Read, Glob, Grep, WebFetch, Write, Edit
version: 1.6.0
author: Jeremy Longshore <jeremy@intentsolutions.io>
license: MIT
tags:
- saas
- cohere
- diagnostics
model: inherit
effort: high
compatibility: Designed for Claude Code; live verification requires network access and an approved Cohere API key
---
# 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 `CO_API_KEY` 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.

## Approval Boundaries

Do not expose or rotate keys, change Cohere Team roles, accept commercial terms, enable sensitive production data, increase spend or capacity, switch production models, send a support bundle, or execute model-proposed side effects without the accountable owner's approval. Keep diagnosis read-only unless implementation was requested.

## Output

Return the resolved API and model contract, files or settings inspected, evidence collected, validation result, remaining risk, owner, and rollback or next action. Redact keys, authorization headers, prompts, retrieved documents, embeddings, customer identifiers, and unrestricted environment output.

## Error Handling

| Condition | Response |
|---|---|
| Secret detected | Stop packaging, remove the value, and rotate if exposure occurred. |
| Customer text present | Replace it with a synthetic reproducer or approved hash. |
| Oversized bundle | Drop unrelated logs and narrow the time window. |
| No reproduction | Document observed evidence and mark the failure intermittent. |

## Examples

Use this compact handoff shape to keep the selected scope, validation evidence, and operational result reviewable.

Input:

```text
incident=INC-42; window=10m; reproduction=synthetic; destination=local-only
```

Expected handoff:

```text
bundle=ready; secrets=0; customer-content=0; checksum=recorded
```

## Resources

- [Skill-specific official documentation](references/official-docs.md)
- [Error reference](https://docs.cohere.com/reference/errors)
- [Cohere support guidance](https://docs.cohere.com/docs/cohere-faqs)
Files in this package (2)
  • SKILL.md 4 KB
  • references/official-docs.md 3 KB

Versions

The database has no other skills named cohere-debug-bundle.

Identical content appears in 1 other GitHub folders. We show one copy with the highest score.

Database snapshot: 13.11.2026 · package version 4c1154bd5082 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100cohere-common-errors
    Diagnose Cohere v2 authentication, validation, model, quota, transport, and provider failures from redacted evidence. Use when a Cohere request fails. Trigger with "Cohere error", "Cohere 429", or "debug Cohere API".
  • 100clickup-debug-bundle
    Collect a minimal redacted ClickUp connectivity and contract bundle without task bodies, tokens, or webhook secrets. Use when escalating a ClickUp API incident. Trigger with "ClickUp debug bundle", "ClickUp diagnostics", or "collect ClickUp evidence".
  • 100langchain-debug-bundle
    Collect LangChain debug evidence for troubleshooting and support. Use when preparing bug reports, collecting traces, or gathering diagnostic information for complex issues. Trigger with phrases like "langchain debug bundle", "langchain diagnostics", "langchain support info",…
  • 100clay-debug-bundle
    Collect Clay debug evidence for support tickets and troubleshooting. Use when encountering persistent issues, preparing support tickets, or collecting diagnostic information for Clay problems. Trigger with phrases like "clay debug", "clay support bundle", "collect clay logs", "clay diagnostic".

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.