kurrent-io

This skill should be used ONLY when the user explicitly asks to run a structured agent *flow* by name or definition id — e.g. "start a flow", "run the code-review flow", "run the X flow", "use flow definition X", "kick off an agent flow", or wants an iterative loop run by a separate hosted participant agent that continues until sign-off. It covers the same underlying tools as the `review-flows` skill (`start_review_flow` etc. are aliases of the generic tools documented here) — use `review-flows` for the two built-in review kinds (`spec-review`, `code-review`) and this skill for any other flow definition, or when the user names a `definition_id` explicitly. Do NOT use this skill (and do NOT call the flows MCP tools) for an ordinary request such as "review my PR", "do X for me", or "check this over" where the user just wants you to do the work yourself — perform that work directly instead.

This skill should be used ONLY when the user explicitly asks to run a structured review *flow* — e.g. "start a review flow", "submit this for review", "re-review after I address findings", or wants an iterative review loop run by a separate reviewer that continues until sign-off. Do NOT use this skill (and do NOT call the flows MCP tools) for an ordinary review request such as "review my PR", "review this diff/spec/design", or "code review" where the user just wants you to review it yourself — perform that review directly instead.

This skill should be used to read, search, or recall past Kurrent Capacitor sessions. Triggers include: "read a previous session", "get session history", "recap session", "what happened in session X", "load context from a previous session", "continue from session", "what did we do last time", "catch me up on session X", "summarize session", "show me what happened", "what have we been working on", "recently we implemented", "what was done in this repo", "recent changes", "recent sessions", or providing a session ID to review. Also covers search/recall asks: "find the session where we…", "which session discussed X", "did we ever debug Y", "look up the session about Z", "recall the session that…", "search past sessions for…". Provides instructions for retrieving and searching session history via the kcap CLI and the kcap-sessions MCP tools.

This skill should be used when the user asks to "disable recording", "stop recording", "delete this session", "don't record this", "remove my session data", "erase this session", "turn off tracking", "stop tracking", "disable kcap", "remove session", or wants to stop the current session from being recorded. Stops the watcher, prevents future hooks, and deletes server data.

This skill should be used when the user asks to "show errors", "extract errors", "what went wrong", "find tool errors", "review errors from session", "check session errors", "list failures", "what failed in session X", "error report", "show mistakes", or wants to review tool call errors from a recorded session. Provides instructions for extracting tool errors via the kcap CLI.

This skill should be used when the user asks to "hide this session", "make this private", "hide session", "owner only", "make private", "hide from others", "set private", "don't show this session", or wants to change the current session visibility to owner-only. Sets session visibility so only the owner can see it.

This skill should be used when the user asks to "validate plan", "verify plan", "check plan completion", "did I finish everything", "is the plan done", "what's left to do", "validate my work", or wants to verify that all planned items were completed.

Use when the user is working with KurrentDB, from writing application code against the client SDKs to operating the self-hosted server or running on Kurrent Cloud.

Use when installing, configuring, or operating the kcap CLI, aka the Kurrent Capacitor CLI / Capacitor CLI (npm @kurrent/kcap), which records Claude Code, Codex, and Cursor sessions to a Capacitor server. Covers install/setup/login, profiles, where its config and on-disk state live, importing and remapping past sessions, recap/eval/errors on a recorded session, visibility and privacy (hide, disable, ignoring or excluding repos and directory trees from recording), the daemon and hosted agents, MCP sessions/review and PR review, and plugin hooks.

Use when migrating an app onto the KurrentDB gRPC client from a legacy EventStoreDB client. Covers both the TCP rewrite and gRPC rebrand paths, plus the esdb to kurrentdb connection-string switch. NOT for code already on the KurrentDB client (use kurrent-docs) or server upgrades.

Use when inventorying an application's KurrentDB or EventStoreDB client surface before a migration or audit. NOT for server or cluster state (use kurrentdb-server-detection).

Use when working on, updating, or reviewing code that instantiates or configures a KurrentDB gRPC client across the supported SDKs. Covers connection-string parameters, single-node versus gossip discovery for clusters, node preference for read and write splits, HTTP/2 keepalive for long-lived connections behind NAT or load balancers, default deadlines, serverless client reuse, and triage of connection-related failures like discovery timeouts, deadline exceeded, keep-alive resets, and TLS verification errors. Do NOT use for authentication mechanics, certificate provisioning on the server, EventStoreDB to KurrentDB migration, or server-side cluster sizing.

Use when inventorying a deployed KurrentDB or EventStoreDB server for its version, cluster topology, license status, and deployment method by reading runtime endpoints, deployment manifests, and on-disk version banners. NOT for client SDK state (use kurrentdb-client-detection), Kurrent Cloud projects, or migration execution.

POES (Proof-Oriented Event Sourcing) API reference for verifying event-sourced aggregates with property-based testing, exhaustive state exploration, temporal properties, and KurrentDB persistence. Use when writing or verifying aggregates, invariants, transitions, or temporal properties.

Provides KurrentDB (EventStoreDB) client code for event sourcing and CQRS. Generates correct package names, connection strings, and API patterns for Python, Node.js, .NET, F#, Go, Java, Rust. Triggers on "kurrentdb", "eventstore", "event sourcing", "append events", "read stream", "subscription", "aggregate", "CQRS".

Single step only: audit a completed connector — implementation, testing & simulator validation, artifacts, security smells, cross-doc consistency — and produce a scored markdown review report. Read-mostly; does not modify connector code.