Individual skill
transaction-protocol-reasoning
Teaches how to reason from a transaction protocol’s rules to a working model. Use when analyzing a concurrency-control paper, spec, or algorithm to identify state, metadata, invariants, operation rules, examples, counterexamples, guarantees, false aborts, unsafe commits, or tradeoffs before inspecting concrete traces.
tasks/tictoc-unnecessary-abort-detection/environment/skills/transaction-protocol-reasoning/SKILL.md
Source commit f860ecf02ef53412a030f8661c83d644b739ff01
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- Yes
- Observed behavior
- Instructions only
- Last checked
- Nov 9, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 1,911
- Repository last updated
- Nov 4, 2026
- License
- Apache-2.0
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- benchmark Repository topic
- skillsbench Repository topic
- research Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 4,145 bytesreferences/counterexample-construction.mddoc · 3,185 bytesreferences/example-construction.mddoc · 2,206 bytesreferences/invariant-extraction.mddoc · 2,565 bytesreferences/operation-rule-analysis.mddoc · 3,660 bytesreferences/protocol-analysis-workflow.mddoc · 5,075 bytesreferences/protocol-comparison.mddoc · 2,396 bytesreferences/state-and-metadata-modeling.mddoc · 3,757 bytes
Read excerpt
# Transaction Protocol Reasoning
Use this skill when **a protocol is already given** (paper, spec, pseudocode, implementation notes) and you need to understand what it guarantees and how its rules imply commit/abort behavior.
This skill does **not** ask you to invent a protocol. It teaches how to read a protocol description as a set of rules, turn those rules into checkable predicates/invariants, and then reason about safety vs conservatism.
## What “done” looks like
By the end you should have:
- a one-page **Protocol Ledger** (state + rules + invariants)
- a minimal **example pack** (3–6 tiny histories) that exercises boundaries
- a clear statement of:
- the protocol’s **proof object** (what metadata it relies on), and