slate-patch

Fix Slate v2 bugs in one pass with reproduction, behavior tests, architecture/DX/perf pressure, proactive rearchitecture when the patch is not the cleanest long-term shape, and final autoreview.

Quality

70%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/slate-patch/SKILL.md

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 is a well-sequenced, highly actionable workflow with strong validation feedback loops, though it is somewhat verbose and monolithic. Its weakest point is progressive disclosure: substantial reference-grade detail is inlined rather than split into bundled reference files.

Suggestions

Move the Editor Selection Navigation Coverage matrix spec (command×direction×topology×starting-state rows) into a bundled reference doc and link to it one level deep, keeping only the decision rule inline.

Trim redundancy between the Hard Rules section and the Workflow steps so each rule is stated once in its authoritative location.

Replace the hardcoded `/Users/zbeyens/git/plate-2/.agents/skills/autoreview/scripts/autoreview` path with a checkout-relative invocation so the command is portable.

Dimension	Reasoning	Score
Conciseness	The body is dense and assumes Claude's competence without explaining basics, but the Hard Rules section restates guidance elaborated later in the Workflow (reproduce-first, breaking changes), creating noticeable redundancy that could be tightened.	3 / 5
Actionability	Concrete executable commands appear throughout (`pnpm bench:targets:check`, `bun check`, `rg`, the autoreview invocation), but the hardcoded `/Users/zbeyens/git/plate-2/...` path is environment-specific rather than copy-paste portable.	4 / 5
Workflow Clarity	Eight numbered steps are clearly sequenced with explicit validation checkpoints — a failing red test, the keep/rework/escalate pressure verdict, verify gates, and a 'rerun until no findings' autoreview feedback loop — plus checklists for a complex process.	5 / 5
Progressive Disclosure	Section headers give good internal structure and external doc paths are clearly signaled, but the monolithic body inlines reference-grade material (the command×direction×topology selection matrix, the bug-class taxonomy) with no bundled reference files to offload it to.	3 / 5
	Total	15 / 20 Passed

Description

71%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 specific and distinctive, naming a concrete multi-action pipeline for Slate v2 bug fixing. Its main weakness is the absence of an explicit 'when to use' clause, which caps completeness.

Suggestions

Append an explicit 'Use when...' clause naming concrete user triggers (e.g., 'Use when the user reports a Slate v2 browser/editor bug or regression and wants a fix, not a plan').

Add natural trigger synonyms like 'regression' or 'editor bug' to broaden keyword coverage.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — "reproduction, behavior tests, architecture/DX/perf pressure, proactive rearchitecture... and final autoreview" — giving comprehensive coverage of what the skill does rather than vague abstraction.	5 / 5
Completeness	The WHAT is clear (fix Slate v2 bugs via a defined one-pass pipeline), but there is no explicit "Use when..." trigger clause, so per the missing-trigger guideline completeness is capped at 3.	3 / 5
Trigger Term Quality	Natural terms like "Slate v2 bugs", "fix", and "one pass" are present, but common user synonyms such as "regression" or "editor bug" are missing from the description.	4 / 5
Distinctiveness Conflict Risk	The Slate v2 + one-pass + rearchitecture framing carves a clear niche, with only minor overlap risk against the related slate-plan/autoreview/slate-ar family.	4 / 5
	Total	16 / 20 Passed

Validation

81%

Warnings & errors only

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

Criteria	Description	Result
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/slate-patch/SKILL.md
Commit: d76efae

Reviewed: 3 days ago

Table of Contents

Discovery Implementation Validation

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.