Agent skill · software engineering · jeremylongshore
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".
Why this skill is useful
Provides a specific CI/CD pipeline configuration for Cohere API applications that includes automated testing workflows not commonly found in public documentation.
What it needs
Requires cohere-ai installed locally. Requires github account access. About 2k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
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 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. 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. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/cohere-ci-integration