Agent skill · software engineering · jeremylongshore
cohere-reference-architecture
Design a governed Cohere architecture for Chat, RAG, tools, streaming, evaluation, and provider operations. Use when planning or reviewing a Cohere system. Trigger with "Cohere architecture", "Cohere RAG design", or "Cohere service layout".
Why this skill is useful
Provides a structured reference architecture for Cohere API v2 applications, including specific project layouts and service patterns that the AI wouldn't reliably generate on its own.
What it needs
Requires cohere-ai 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 Reference Architecture Overview Define clear boundaries between clients, policy, retrieval, provider access, tools, evaluation, and operations so model behavior cannot bypass application controls. 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 Keep a typed Cohere provider adapter behind an application service boundary. Apply tenant authorization and metadata filters before retrieval, then preserve document IDs through Rerank and citations. Dispatch tools through a policy-enforcing registry with schemas, approvals, timeouts, and audit evidence. Resolve model, lifecycle, capacity, and platform IDs through environment configuration and current provider sources. 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. Capture users, tenants, data classes, quality objectives, latency targets, side effects, and failure tolerance. 2. Draw trust boundaries for clients, API, policy, retrieval, vector store, Cohere, tools, logs, and secret stores. 3. Define request, result, citation, tool, error, and telemetry contracts at each boundary. 4. Choose synchronous, streaming, queued, or degraded paths with bounded retries and cancellation. 5. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/cohere-reference-architecture