consistency-model-selector
Installation
SKILL.md
When to Use
Use this skill when you need to decide how strongly consistent a distributed operation must be, and what mechanism enforces that guarantee.
Invoke it for:
- Any operation where two nodes could disagree on the current value (leader election, uniqueness check, account balance enforcement, distributed lock)
- Cross-service or cross-database transactions where atomic commit is required
- Systems where stale reads cause incorrect application behavior (not just stale UI)
- Designing coordination infrastructure (service registry, job scheduler, partition assignment)
- Evaluating whether a Dynamo-style leaderless database is strong enough for a given workload
Do not invoke it for single-node transaction isolation tuning — that is the domain of transaction-isolation-selector.
Context and Input Gathering
Before selecting a model, collect the following per operation or component: