Agent skill · software engineering · jeremylongshore
cohere-local-dev-loop
Build a deterministic local Cohere development loop with a provider adapter, fixtures, and an opt-in live smoke test. Use when developing or testing Cohere features locally. Trigger with "Cohere local dev", "mock Cohere", or "Cohere test loop".
Why this skill is useful
Adds executable scripts for setting up a local development environment with Cohere API v2, including mocking and testing workflows.
What it needs
Requires node 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 Local Development Loop Overview Keep normal development offline and deterministic while preserving one tightly bounded path that proves the real v2 contract. 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 Mock the application-owned provider interface, not generated SDK internals. Store representative v2 Chat, Embed, Rerank, stream, error, and tool-call fixtures with secrets removed. Gate real calls behind an explicit environment switch and a protected evaluation key. Treat model IDs and SDK response types as external contracts covered by adapter tests. 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. Locate the provider boundary and existing test framework before adding files. 2. Define a narrow Cohere port for the operations the application actually needs. 3. Add sanitized fixtures for success, rate limit, timeout, and malformed response paths. 4. Write offline contract tests for request mapping, response parsing, and redaction. 5. Add one opt-in live smoke test with a single request and hard timeout. 6. Document the exact offline and live commands and ensure the default test command makes no network call. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/cohere-local-dev-loop