Agent skill · software engineering · jeremylongshore
cohere-webhooks-events
Handle Cohere v2 streaming events and convert application-owned asynchronous work into idempotent internal events without inventing provider webhooks. Use when building streaming UIs or event workflows. Trigger with "Cohere streaming", "Cohere SSE", or "Cohere events".
Why this skill is useful
Provides specific implementation patterns for handling Cohere's streaming events and webhooks 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 Streaming and Application Events Overview Separate response-stream events from durable business events and replace deprecated managed connectors with application-owned v2 tools. 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 Chat v2 streaming is a server-sent response stream, not an inbound signed webhook surface. Handle typed content, citation, tool-call, and terminal events and tolerate additive unknown event types. Managed v1 connectors are deprecated; v2 retrieval and web search use user-defined tools. If the application emits durable callbacks, define its own authentication, signing, idempotency key, retries, and dead-letter policy. 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. Choose response streaming, tool streaming, or an application-owned durable event; do not conflate them. 2. Implement an async iterator with cancellation, timeout, terminal-state validation, and unknown-event telemetry. 3. Buffer partial content only within explicit memory and latency bounds. 4. Correlate tool calls and results before continuing the v2 message loop. 5. For durable internal events, persist state before delivery and enforce signature and replay-window validation. 6. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/cohere-webhooks-events