Use this skill when implementation is complete — a feature or bugfix is functionally finished, tests pass, or you are about to commit / open a PR / merge — or when a spec is finalized. At that moment, proactively OFFER an independent second-harness review even if the user did not ask, because a fresh, separate…
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.
This skill should be used when you are planning or discovering the SHAPE of a work item — that it breaks into sub-tasks (a parent and its parts), or that one piece must land before another (a blocks / blocked-by dependency) — and you want that structure recorded so it shows up in Kurrent Capacitor's Home "Blockers &…
Agent skills and migration tooling for KurrentDB and the legacy EventStoreDB stack. Covers SDK usage, server operations, Kurrent Cloud, the esc CLI, and TCP-to-gRPC client migrations.
Pre-built skills and agents for KurrentDB: building and operating apps with the current client SDKs, running the self-hosted server, deploying on Kurrent Cloud, and migrating off legacy EventStoreDB clients (TCP, esdb:// rebrand, smoke tests).
2 1mo agoA
tokens not measured
copy · 86%Apache-2.0
Use when asked to review KurrentDB client code, after writing or modifying SDK call sites, as the post-migration check dispatched by migration-specialist, or as a pre-PR gate. Reviews application code that uses the KurrentDB / EventStoreDB client SDKs for idiomatic usage, anti-patterns, and (in post-migration mode)…
Use when asked to migrate off the TCP client, retire EventStoreConnection, move from esdb:// to kurrentdb://, or upgrade an intermediate gRPC client to KurrentDB.Client. Orchestrates KurrentDB / EventStoreDB client SDK migrations: detects the current client and connection scheme, routes to the matching flavour of the…
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…
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 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…
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…