CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

undo-redo-history

Check that every undo gives back the document from before its step and every redo the one after, over every list of up to three short commands on every small document, under the grouping, skipping and restoration rules of Plite history. Use before and after changing packages/plitejs/src/history or another file in its coverage record, when the undo-redo-history step of pnpm check fails, or when fixing an undo or redo bug a seed or a tester found.

Quality

81%

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

70%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 delivers fully executable commands and tightly validated workflows (gate pins, exit codes, baseline discipline, a bug-triage decision tree), which is exemplary actionability and workflow clarity. But it concentrates ~45KB of findings catalogs, coverage records and mutant evidence into a single file with no reference files, hurting both token efficiency and progressive disclosure.

Suggestions

Move the 'Findings' failure-class catalogs (with their counts, commit hashes and case identities) into a reference file such as references/findings.md, keeping in SKILL.md only the summary counts and the instructions for reading a failure.

Extract the 'What a pass proves' mutant evidence and the coverage-record table into reference files, leaving a short 'when to re-sync' procedure inline with a one-level-deep pointer to the detail.

Tighten 'What it checks' items 4-6 by replacing the exhaustive mode/law enumerations with a pointer to the script's own flags (`--help` output or a references/laws.md), trimming the inline detail to the gate-relevant subset.

DimensionReasoningScore

Conciseness

The body is a ~45KB monolith where sections like 'Findings' catalog dozens of failure classes with exact counts, commit hashes and case identities and 'What a pass proves' lists mutant-by-mutant finding counts — earned, project-specific information, but far beyond what the workflow needs inline, matching 'noticeably verbose; several padded sections'. It avoids the 1 anchor because none of it explains concepts Claude already knows.

2 / 5

Actionability

Commands are copy-paste ready throughout: `pnpm check:undo-redo-history`, `--size=5`, `--case='Enter at b|0 ; undo ; remote delete block 0.1'`, `git log --oneline -1 --grep "let another peer run every letter command"`, with timings, exit-code semantics and worked failure-reading examples covering the common cases — the 5 anchor.

5 / 5

Workflow Clarity

Workflows are clearly sequenced with explicit validation checkpoints and feedback loops: exit codes 0/1/2, the case-count pin ('fails when it compares other than 18,017 cases'), 'the gate fails until you run `--lower`', the real-bug / modeling-error / intended-change decision tree, and the coverage-sync procedure gated on a check plus a gate run. Baseline writes are guarded ('The baseline never grows', 'Never weaken a law'), so the destructive-operation cap does not apply.

5 / 5

Progressive Disclosure

There are no bundle files at all, and content that clearly belongs in separate reference files — the findings catalog, the coverage-record table, the mutant evidence — is inlined in one document. Section headers keep it navigable, matching the 3 anchor's 'some structure but content that should be separate is inline', rather than the 2 anchor's buried or unstructured material.

3 / 5

Total

15

/

20

Passed

Description

87%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 dense, third-person description that states a precise verification capability and gives three concrete, explicit trigger conditions. Its only weakness is jargon-heavy phrasing ('coverage record', 'a seed or a tester') that narrows natural keyword coverage and makes a single checking action read as a long, packed sentence.

DimensionReasoningScore

Specificity

Quotes like "Check that every undo gives back the document from before its step and every redo the one after... under the grouping, skipping and restoration rules" name several concrete checked behaviors with explicit scope, but it elaborates a single checking action rather than listing multiple distinct actions, so it sits just below the comprehensive 5 anchor and clearly above the 1-2-action anchor at 3.

4 / 5

Completeness

It explicitly answers both questions: the first sentence states what it does, and "Use before and after changing packages/plitejs/src/history... when the undo-redo-history step of pnpm check fails, or when fixing an undo or redo bug" gives three concrete trigger phrases, matching the 5 anchor exactly. The 4 anchor's weaker 'when' clearly under-describes this level of explicitness.

5 / 5

Trigger Term Quality

Natural phrases a repo developer would say are present — "undo", "redo", "the undo-redo-history step of pnpm check", "changing packages/plitejs/src/history", "an undo or redo bug" — giving good coverage, but insider jargon like "its coverage record" and "a seed or a tester" plus few synonyms keep it below the comprehensive 5 anchor.

4 / 5

Distinctiveness Conflict Risk

Triggers are tied to a named check step, a specific source path, and Plite's history plugin — a clear niche with minimal overlap risk, matching the 5 anchor; no neighboring anchor fits better.

5 / 5

Total

18

/

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/undo-redo-history/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.