CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

formally-verify-cua-driver

Model-check the Cua Driver's state machines with TLA+ (element tokens, session lifecycle, permission admission, macOS foreground restore, recording, Windows typing and serve drain, invoke_menu cancel) after a change to the code they cover. Use when a diff touches a file in the coverage table, when a race or ordering bug is suspected there, or to add a new machine.

Quality

91%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

88%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

An exceptionally dense, actionable verification skill: every section carries operative instructions, the commands are copy-paste ready, and the workflow has explicit validation and feedback loops most skills lack. The two deductions are small — a little justificatory/history prose that could be trimmed, and the fact that the models/ specs and models.tsv the whole document pivots on are missing from the bundle as provided.

Suggestions

Ship the referenced bundle files: the body's run instructions and coverage table point to models/*.tla, models/*.cfg, and models.tsv, none of which are present — scripts/check-models.sh fails immediately because it reads $SKILL/models.tsv.

Trim the 'Where the specs used to live' migration table to one sentence (the old paths only matter for git archaeology) and tighten the intro's rhetorical framing ('the places where a bug does the most harm and tests reach it least') to save ~10 lines of tokens.

The '/statechart' dependency is mentioned only in passing mid-Run section; either move it to a short 'Dependencies' note up front or drop it, so readers know before running whether that skill is required.

DimensionReasoningScore

Conciseness

The body never explains concepts Claude already knows (no 'what is TLA+' or 'what is a lock' padding) and is dense throughout — e.g. the coverage table carries code paths, rules, and harm in one row. Minor trim candidates keep it below a 5: the rhetorical framing 'the places where a bug does the most harm and tests reach it least' and the historical 'Where the specs used to live' migration table are justificatory rather than operative.

4 / 5

Actionability

Fully executable, copy-paste-ready commands cover the common cases: '.cursor/skills/formally-verify-cua-driver/scripts/check-models.sh session' with filter example and env vars (JAVA, TLA2TOOLS, TLC_SECONDS), a by-hand TLC invocation 'java -XX:+UseParallelGC -cp ~/.cache/cua-driver-tla/tla2tools-1.7.4.jar tlc2.TLC -workers 1 -config session.cfg session.tla', and an exact 'git log --oneline cc67e715d1..HEAD -- …' drift command listing every covered file. Counterexample validation gives three concrete checks per replayed step.

5 / 5

Workflow Clarity

The multi-step process is explicitly sequenced with validation checkpoints and feedback loops: match the diff against the coverage table, rerun affected rows, interpret row kinds ('A variant that starts passing means the model lost the step that guard covers. Fix the model, not the row'), replay counterexamples one action at a time against the named functions, reproduce with 'std::sync::Barrier' tests or the verify-cua-driver lane, and 'Do not move it [the sync commit] on a green run alone.'

5 / 5

Progressive Disclosure

The design is 5-level: an overview-first SKILL.md with clearly signaled, one-level-deep references ('Every spec and config lives in this skill's models/ directory', '[models.tsv](models.tsv) lists every config'). But scored against the actual bundle, only scripts/check-models.sh exists — the referenced models/ directory and models.tsv are absent (the script itself reads '$SKILL/models.tsv'), so the primary references dangle; that is more than a minor organization gap, landing between the 3 and 5 anchors.

4 / 5

Total

18

/

20

Passed

Description

92%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A model description: concrete what, an explicit three-condition when-clause, and a narrowly scoped, conflict-free trigger surface. The only improvement space is synonym coverage in the trigger terms.

DimensionReasoningScore

Specificity

'Model-check the Cua Driver's state machines with TLA+' is a concrete action, and the parenthetical enumerates all eight covered machines ('element tokens, session lifecycle, permission admission, macOS foreground restore, recording, Windows typing and serve drain, invoke_menu cancel') plus when it applies ('after a change to the code they cover'). Not 4: there is no coverage gap — the enumeration matches the skill's full scope; not lower since nothing is vague.

5 / 5

Completeness

Explicitly answers both questions: what ('Model-check the Cua Driver's state machines with TLA+ (…) after a change to the code they cover') and when with three concrete triggers ('Use when a diff touches a file in the coverage table, when a race or ordering bug is suspected there, or to add a new machine'). This matches the 5 anchor's 'concrete trigger phrases' exactly.

5 / 5

Trigger Term Quality

Natural phrases a user would actually say are present: 'a diff touches a file', 'a race or ordering bug is suspected', 'model-check', 'state machines', 'TLA+'. Not 5 because common synonyms are missing — 'concurrency', 'formal verification', 'deadlock', 'interleaving' would all plausibly appear in a request; not 3 because the terms included are the natural ones, not jargon-only.

4 / 5

Distinctiveness Conflict Risk

'Cua Driver's state machines with TLA+' names a specific subsystem and a specific method — a clear niche with distinct triggers. It would not plausibly fire for unrelated skills; the only conceivable neighbor is a generic TLA+ or the sibling verify-cua-driver skill, and the coverage-table trigger keeps it separate.

5 / 5

Total

19

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 2 missing

Warning

Total

15

/

16

Passed

Repository

trycua/cua

Path

.cursor/skills/formally-verify-cua-driver/SKILL.md

Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.