CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

delete-paste-ranges

Check that Backspace, Delete, Return, typing, paste, cut and bold keep the text outside their range in order over every caret and range of every small document, with a link, a read-only inline, a required title and a one-text code block among them, that the result stays canonical and that one undo gives back the document. Use before and after changing packages/plitejs/src/transforms-text/delete-text.ts, merge-nodes.ts, slice landing or another file in its coverage record, when the delete-paste-ranges step of pnpm check fails, or when fixing a delete, join or paste bug a tester found.

Quality

89%

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.

An exceptionally dense, deeply actionable verification skill: every command, flag, exit code, and triage decision is concrete, and the workflow has genuine validation and feedback loops. Its weaknesses are that all reference-grade material (findings catalogs, deep-run statistics, coverage tables) is inlined in one large file, and the body carries time-sensitive dates, timings, and load averages that inflate tokens without aiding action.

Suggestions

Move the Findings catalogs (the 13 gate causes, 3 code-block causes, and 2 deep-run causes with their counts and example identities) into a references/ file, keeping only the cause summaries and a pointer in SKILL.md.

Drop or relocate the historical performance data ('209 s of processor time', '26 s at a load average of 42', '703 s at a load average near 130') and the fix-date ranges into a baseline/maintenance note, since they are time-sensitive and not needed to run or triage the check.

Consider moving the coverage-record table and its sync procedure to a separate file referenced from SKILL.md, so the main file reads as an overview of run, triage, and update flows.

DimensionReasoningScore

Conciseness

The telegraphic style assumes competence and never explains known concepts, but it carries substantial time-sensitive data outside any deprecated section (fix dates '2026-10-24 and 2026-11-02', timings like '209 s of processor time... 26 s at a load average of 42', '703 s at a load average near 130') and a 13-cause findings catalog with per-cause counts that could be tightened or trimmed. This fits 'mostly efficient but could be tightened' rather than anchor 4, where the trimmable material would be minor.

3 / 5

Actionability

Guidance is fully executable: 'pnpm check:delete-paste-ranges', '--blocks=3 --lines=3', '--lower', "--case='<identity or part of one>'", '--jobs=<n>', exit codes 0/1/2, and copy-paste git commands ('git log --oneline -1 --grep "range check over a code block and bold"'). Concrete failure identities to reuse are given, matching the copy-paste-ready anchor.

5 / 5

Workflow Clarity

The batch-verification workflow is fully sequenced with explicit validation and feedback loops: gate exit codes and baseline case-count pins ('fails when either baseline's documents give a case count other than its pin'), a three-way failure classification (real bug / modeling error / intended change), '--case' for error recovery, and the loop where 'the gate fails until you run --lower'. The batch-operation cap does not apply because validation checkpoints are thorough.

5 / 5

Progressive Disclosure

No bundle files exist, so all content sits inline in one ~23KB SKILL.md with clear headers but no references. Reference-grade material — the 13-cause findings catalog with counts, deep-run statistics, mutant results, and the coverage-record table — is inlined rather than split out, matching the anchor 'content that should be separate is inline'. Not anchor 4 because the split-worthy material is substantial, not a minor gap.

3 / 5

Total

16

/

20

Passed

Description

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

The description is a model example: it states a precise, multi-part verification capability in third person, and pairs it with an explicit use-when clause covering file changes, check failure, and bug fixes with concrete file paths and command names. Trigger terms are exactly the natural language a developer would use, and conflict risk is minimal given the named files and check step.

DimensionReasoningScore

Specificity

It enumerates concrete commands ('Backspace, Delete, Return, typing, paste, cut and bold') and the exact properties checked ('keep the text outside their range in order', 'the result stays canonical', 'one undo gives back the document') over 'every caret and range of every small document', with named document features (link, read-only inline, required title, one-text code block). Coverage is comprehensive with no gaps, matching the top anchor rather than anchor 4.

5 / 5

Completeness

The first sentence explicitly states what the skill does (the full property check) and the second gives an explicit 'Use before and after changing...' clause with three concrete triggers: editing the named source files, 'when the delete-paste-ranges step of pnpm check fails', and 'when fixing a delete, join or paste bug a tester found'. Both what and when are explicit with concrete trigger phrases, matching the top anchor exactly.

5 / 5

Trigger Term Quality

Natural terms a developer would actually say are all present: 'Backspace', 'Delete', 'paste', 'cut', 'bold', 'undo', 'delete, join or paste bug', alongside synonyms ('join', 'slice landing') and concrete file paths with extensions ('delete-text.ts', 'merge-nodes.ts'). This matches comprehensive coverage including synonyms and file references.

5 / 5

Distinctiveness Conflict Risk

The niche is precisely scoped to delete/paste range verification in the plitejs editor, with triggers naming exact files and a named check step, so it is clearly distinguishable from any other skill and unlikely to fire for the wrong one.

5 / 5

Total

20

/

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/delete-paste-ranges/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.