slate-ar-stabilize

Slate v2 behavior-stability mini-skill. Runs existing editor behavior gates, routes repeated failures to slate-patch, and keeps looping until the surface is stable or blocked.

Quality

80%

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-ar-stabilize/SKILL.md

Quality

Content

100%

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 lean, highly actionable stabilization runbook with a clear numbered workflow, explicit fail-fix-rerun feedback loops, and well-organized sections. It earns the top score across all four content dimensions.

Dimension	Reasoning	Score
Conciseness	The body is terse with no concept padding — it assumes Claude's competence and every line earns its place (e.g. the numbered Contract steps and the bulleted Completion criteria), matching the 'lean and efficient' anchor.	3 / 3
Actionability	It gives concrete, executable guidance with specific commands (`slate-ar-status`, `slate-ar-gate`, `slate-patch`, `autogoal`, `tdd`) and a numbered procedure, matching the 'fully executable commands; copy-paste ready' anchor.	3 / 3
Workflow Clarity	The numbered sequence includes explicit validation checkpoints and a feedback loop — 'if the same valid gate fails twice, stop gating and fix', 'rerun the focused gate after each fix', 'broaden ... only after focused proof is green' — plus a Completion checklist, matching the top anchor.	3 / 3
Progressive Disclosure	At under 50 lines with no need for external references, the well-organized Contract/Completion/Handoff sections meet the rubric's allowance for simple skills to score 3 on progressive disclosure without bundle files.	3 / 3
	Total	12 / 12 Passed

Description

60%

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 states concrete, specific actions and is written in proper third person, but it omits an explicit 'Use when...' trigger and leans on internal jargon rather than natural user phrasing. These gaps leave completeness and trigger-term quality at the mid level rather than the top.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user wants editor behavior regressions (selection, typing, copy/paste, IME, undo/redo) gone'.

Replace internal jargon ('behavior gates', 'slate-patch') with natural user-facing terms alongside the technical names so trigger matching improves.

Include the concrete behavior surfaces (selection, typing, IME, focus, undo/redo) in the description to sharpen distinctiveness from general stabilization skills.

Dimension	Reasoning	Score
Specificity	Names multiple concrete actions in third person — 'Runs existing editor behavior gates, routes repeated failures to slate-patch, and keeps looping until the surface is stable or blocked' — matching the 'lists multiple specific concrete actions' anchor.	3 / 3
Completeness	It clearly states what the skill does but lacks any 'Use when...' clause or equivalent explicit trigger guidance, so completeness is capped at 2 per the rubric guideline.	2 / 3
Trigger Term Quality	Terms like 'behavior gates', 'slate-patch', and 'stable or blocked' are internal jargon a user would rarely say; common natural phrasings (e.g. 'editor regressions', 'fix selection/typing bugs') are missing, matching the 'some relevant keywords but missing common variations' anchor.	2 / 3
Distinctiveness Conflict Risk	The 'Slate v2 behavior-stability' framing carves a niche, but without explicit user-facing triggers it could still overlap with general fix/stabilize skills, matching the 'somewhat specific but could still overlap' anchor rather than the distinct-trigger level 3.	2 / 3
	Total	9 / 12 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-ar-stabilize/SKILL.md
Commit: 45116fd

Reviewed: about 14 hours 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.