CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

effect-ledger

Check that the effect ledger, the internal judge of native sync, never calls a merge held when it lost work, over every merge the real rebase writes for short command lists on small documents and the intake's queue cases. Eleven planted mutations must read lost, an intent oracle written apart from the ledger must agree, held verdicts must compose, and every merge must reopen as a valid document through createEditor. Use before and after changing packages/plitejs/src/core/change/effect-ledger.ts, the rebase or another file in its coverage record, when the effect-ledger step of pnpm check fails, or when fixing a broken merge the native sync plan's M0.6 names.

Quality

86%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

77%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.

The body is an exceptionally rigorous, fully executable verification manual with a clear failure-triage workflow and built-in validation loops — near the ceiling on actionability and workflow clarity. Its weaknesses are volume and monolithic structure: historical findings, timing measurements, and world inventories are inlined where reference files would keep the acting core lean.

Suggestions

Move the "Findings" section (per-world invalid-merge counts, M0.6 named merges, sync-commit history) and the scratch-break table under "What a pass proves" into a references/findings.md, keeping only the failure-signature samples inline that the triage decision tree actually uses.

Split the world/command/mutant inventories in "What it checks" into a references/worlds.md so SKILL.md keeps the property statement, the rule taxonomy, and the run/triage workflow at the top level.

Trim time-sensitive operational numbers (CPU seconds, load-average anecdotes, exact leaf pins) into the baseline file's documentation or a short 'pins' reference, so the acting instructions stay valid as the counts drift.

DimensionReasoningScore

Conciseness

The prose is information-dense with no padding or explanation of concepts Claude already knows, but the body is a ~45KB monolith whose historical sections ("Findings" counts from the sync commit, scratch-break tables, CPU-second measurements, pinned counts like 813,356 leaves) carry time-sensitive operational record beyond what the acting workflow needs. It fits anchor 3 — mostly efficient but could be tightened — rather than 4, since substantial material could be trimmed or moved without losing actionability.

3 / 5

Actionability

Guidance is fully executable: exact commands with flags ("pnpm check:effect-ledger --all --world=<shard>", "--case='<identity or part of one>'", "--record-baseline"), concrete failure identities to paste back (e.g. "internal blocks/pp | accepted retype 1 | own enter 1 mid"), and a worked reading of each example. This matches the copy-paste-ready, common-cases-covered level-5 anchor.

5 / 5

Workflow Clarity

The workflow is clearly sequenced with pervasive validation and feedback loops: run a lane, print a single case with --case, classify the failure under the explicit six-way decision tree (broken merge / ledger hole / modeling error / law failure / changed pin / intended change), fix, re-run, then re-record the baseline. The coverage-record section adds a literal three-item checklist before moving the sync commit, matching the level-5 anchor including for this batch/destructive context.

5 / 5

Progressive Disclosure

The body has strong internal structure (numbered rule taxonomy, tables, headers) and points to real repo artifacts (effect-ledger-classes.json, the scripts, the plan doc) instead of duplicating them, but there is no bundle at all — findings history, world definitions, and the coverage record are all inlined in one file that clearly could be split into reference files. This lands on anchor 3 (content that should be separate is inline) rather than 2, because the structure and navigation within the file are genuinely good.

3 / 5

Total

16

/

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.

An unusually strong description: it states exactly what the verification guarantees, over what input space, and gives an explicit, multi-trigger 'Use when' clause tied to specific files, commands, and plan steps. Its only weakness is dense, jargon-bound phrasing with little synonym coverage for how a user might casually phrase the need.

DimensionReasoningScore

Specificity

The description enumerates multiple concrete verification actions — "Eleven planted mutations must read lost, an intent oracle written apart from the ledger must agree, held verdicts must compose, and every merge must reopen as a valid document through createEditor" — leaving no ambiguity about what the skill does. It matches the level-5 anchor of comprehensive, specific concrete actions, not merely naming the domain.

5 / 5

Completeness

Both halves are explicit: the "what" ("Check that the effect ledger ... never calls a merge held when it lost work, over every merge the real rebase writes ...") and an explicit "Use before and after changing ... when the effect-ledger step of pnpm check fails, or when fixing a broken merge ..." clause with concrete triggers. This matches the level-5 example structure exactly.

5 / 5

Trigger Term Quality

Trigger phrases are concrete and natural for this repo's developers: "packages/plitejs/src/core/change/effect-ledger.ts", "the effect-ledger step of pnpm check fails", "the native sync plan's M0.6", "fixing a broken merge". Coverage is good but jargon-heavy and offers few synonyms or user-level variations, sitting between anchors 4 and 3 and clearly not at comprehensive anchor 5.

4 / 5

Distinctiveness Conflict Risk

The description names a precise niche — the effect ledger as "the internal judge of native sync" — anchored by an exact file path, a named check step, and a plan milestone (M0.6). No other skill would plausibly trigger on these terms, matching the clear-niche level-5 anchor.

5 / 5

Total

19

/

20

Passed

Validation

81%

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

Validation — 13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

metadata_field

'metadata' should map string keys to string values

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

13

/

16

Passed

Repository

udecode/plate

Path

.agents/skills/effect-ledger/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.