Skip to content
Skills Library
DevOps & cloud · Testing

cohere-ci-integration

/cohere-ci-integration

Configure offline Cohere contract tests plus a protected, bounded live verification lane in CI. Use when testing Cohere integrations in pull requests or releases. Trigger with "Cohere CI", "Cohere GitHub Actions", or "Cohere integration tests".

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

Configure offline Cohere contract tests plus a protected, bounded live verification lane in CI. Use when testing Cohere integrations in pull requests or releases. Trigger with "Cohere CI", "Cohere GitHub Actions", or "Cohere integration tests".

Triggers from the description

Cohere CICohere GitHub ActionsCohere integration tests

Arguments

/cohere-ci-integration [repository-path] [ci-provider]
Original author description

Configure offline Cohere contract tests plus a protected, bounded live verification lane in CI. Use when testing Cohere integrations in pull requests or releases. Trigger with "Cohere CI", "Cohere GitHub Actions", or "Cohere integration tests".

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, 492 words
SKILL.md preview
---
name: cohere-ci-integration
description: >-
  Configure offline Cohere contract tests plus a protected, bounded live verification lane in CI. Use when testing Cohere integrations in pull requests or releases. Trigger with "Cohere CI", "Cohere GitHub Actions", or "Cohere integration tests".
argument-hint: "[repository-path] [ci-provider]"
allowed-tools: Read, Glob, Grep, WebFetch, Write, Edit
version: 1.6.0
author: Jeremy Longshore <jeremy@intentsolutions.io>
license: MIT
tags:
- saas
- cohere
- ci
model: inherit
effort: high
compatibility: Designed for Claude Code; live verification requires network access and an approved Cohere API key
---
# Cohere Continuous Integration

## Overview

Make the required CI path deterministic and secret-free while preserving a trusted lane that detects real SDK and API drift.

## 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

- Required pull-request checks should mock the application provider port and make no Cohere network calls.
- Fork pull requests must never receive Cohere secrets.
- A trusted branch, schedule, or manual workflow may run one bounded live probe with explicit spend and timeout limits.
- Pin runtime, SDK, action, and lockfile versions so failures are reproducible.

## 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. Identify required checks, fork behavior, secret scopes, and the existing provider adapter.
2. Add offline request-mapping, response, stream, error, retry, and redaction fixtures.
3. Make the offline lane required and assert that no network fallback is possible.
4. Add a separate protected live job with concurrency control, one request, timeout, and model discovery.
5. Upload sanitized test metadata without prompts, credentials, or customer content.
6. Document who may trigger the live lane and how model/API drift is triaged.

## 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 unavailable | Skip only the optional live job; required offline tests must still run. |
| Fork event | Never switch to a privileged event that executes untrusted code with secrets. |
| Live `429` | Stop the probe and classify capacity rather than retrying repeatedly. |
| Fixture drift | Refresh from a reviewed redacted response. |

## Examples

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

Input:

```text
provider=github-actions; required=offline; live=protected-main; max-requests=1
```

Expected handoff:

```text
offline=required-pass; fork-secrets=none; live=bounded; artifacts=redacted
```

## Resources

- [Skill-specific official documentation](references/official-docs.md)
- [TypeScript SDK](https://github.com/cohere-ai/cohere-typescript)
- [Rate limits](https://docs.cohere.com/docs/rate-limits)
Files in this package (2)
  • SKILL.md 4 KB
  • references/official-docs.md 3 KB

Versions

The database has no other skills named cohere-ci-integration.

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

Database snapshot: 13.11.2026 · package version acd7c8e8343a (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-incident-runbook
    Analyze and mitigate Cohere integration incidents with provider, model, capacity, data, and application evidence plus reversible actions. Use when responding to an outage or serious degradation. Trigger with "Cohere incident", "Cohere outage", or "Cohere on-call".
  • 100cohere-prod-checklist
    Issue an evidence-backed Cohere production go or no-go decision covering capacity, quality, security, operations, and rollback. Use when preparing to launch a Cohere workload. Trigger with "Cohere production checklist", "Cohere go live", or "Cohere launch review".
  • 100cohere-command
    Select among Cohere Command A+ multimodal agents, Command A Reasoning, and Command A Vision for enterprise language and document tasks. WHEN: Command family exact IDs, vision versus reasoning, tool-use and RAG fit, context or licensing. Do NOT use for other model families,…
  • 100perplexity-ci-integration
    Configure Perplexity CI/CD integration with GitHub Actions and testing. Use when setting up automated testing, configuring CI pipelines, or integrating Perplexity tests into your build process. Trigger with phrases like "perplexity CI", "perplexity GitHub Actions", "perplexity…
  • 100cohere-api
    Cohere API for enterprise NLP — embeddings, reranking, RAG, and text generation. Use when building RAG pipelines, semantic search, document reranking, or enterprise NLP applications. The Command A models handle tool use and retrieval-augmented generation with citations; Embed…
  • 100exa-ci-integration
    Configure Exa CI/CD integration with GitHub Actions and testing. Use when setting up automated testing, configuring CI pipelines, or integrating Exa tests into your build process. Trigger with phrases like "exa CI", "exa GitHub Actions", "exa automated tests", "CI exa".

Feedback and reports

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