slate-ar-perfect

Slate v2 broad improvement mini-skill. Uses Autogoal plus Slate AR routing to improve a named surface across quality, bugs, behavior proof, and perf without requiring the user to pick sub-skills.

Quality

75%

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

Quality

Content

88%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 content is a tight, well-sequenced routing workflow with explicit gates and feedback loops and no token waste. Its only soft spot is progressive disclosure, where a pointer to the referenced sub-skills' own docs would round out navigation.

Suggestions

Add one-line pointers to the sibling skills' SKILL.md docs (slate-ar-quality, slate-patch, slate-ar-gate, slate-ar-perf) so the routing owners are discoverable one level deep.

Optionally show the concrete autogoal invocation form in the Contract section so the 'use autogoal for durable work' instruction is copy-paste ready.

Dimension	Reasoning	Score
Conciseness	The body is lean across Contract, Routing, Completion, and Handoff sections with no padding or explanation of concepts Claude already knows; every line carries routing or decision content.	5 / 5
Actionability	It gives concrete routing order with named owner skills and explicit decision rules (e.g. 'Perf waits for behavior stability unless...'), but as an instruction-only routing skill it stops short of executable command forms, leaving minor gaps versus copy-paste-ready guidance.	4 / 5
Workflow Clarity	The routing is a numbered 1-6 sequence with explicit validation gates (slate-ar-gate), a feedback loop (perf exposes a bug -> route to slate-patch -> resume), and a concrete completion checklist with stop conditions.	5 / 5
Progressive Disclosure	The body is cleanly organized into well-signaled sections with no nested references and no bundle files to navigate, but it is slightly above the under-50-line simple-skill threshold and could optionally point to the sibling sub-skill docs for deeper detail.	4 / 5
	Total	18 / 20 Passed

Description

62%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 conveys a clear, distinctive niche and reasonable capability coverage, but it relies on domain jargon and lacks an explicit "Use when..." trigger. Adding a concrete user-facing trigger clause would lift completeness and trigger_term_quality.

Suggestions

Append an explicit 'Use when...' clause naming natural user phrases such as 'perfect pagination', 'fix huge document performance', or 'make editor behavior solid'.

Replace internal jargon ('Autogoal', 'Slate AR routing') in the lead with plain trigger terms a user would actually say, keeping the mechanism as a secondary detail.

Enumerate one or two more concrete actions per surface so capability coverage reads as comprehensive rather than category-level.

Dimension	Reasoning	Score
Specificity	Names the Slate v2 domain and multiple concrete improvement surfaces ("quality, bugs, behavior proof, and perf") plus the routing mechanism, but the actions are category-level rather than fully enumerated concrete operations, sitting just below the comprehensive 5 anchor.	4 / 5
Completeness	It clearly states what the skill does (improve a named surface across quality/bugs/behavior/perf via routing) but provides no explicit "Use when..." clause, and per the rubric a missing when-trigger caps completeness at 3 even though the what is clear.	3 / 5
Trigger Term Quality	Terms like "Slate v2", "pagination", "huge document", "editor behavior", and "API/DX" are relevant but lean toward internal jargon over the natural phrases a user would say, missing common variations and explicit natural triggers.	3 / 5
Distinctiveness Conflict Risk	It is tied to a clear Slate v2 niche and explicitly distinguishes itself from sibling lanes (slate-ar-fast, slate-ar-stabilize), giving minimal conflict risk with other skills.	5 / 5
	Total	15 / 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-ar-perfect/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.