slate-ar-fast

Slate v2 fastest-safe mini-skill. Picks or creates the hottest perf target, runs slate-ar-perf with no-regression checks, and stops at target, plateau, or correctness blocker.

Quality

76%

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

Quality

Content

85%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A tight, expert-only mini-skill: excellently concise with a clear sequenced workflow and an explicit no-regression feedback loop. The main gap is actionability, which stays at 2 because concrete executable commands (the benchmark invocation, metric, and packet format) are named but not shown.

Suggestions

Add one concrete example of the benchmark command and the primary-metric/checks packet format so the guidance is copy-paste ready rather than named-but-not-shown.

Optionally show a one-line example of a kept vs checks_failed packet so the no-regression routing is unambiguous in practice.

Dimension	Reasoning	Score
Conciseness	Lean and efficient throughout; no padding, no explanation of concepts Claude already knows, and every section (Contract, No-Regression Rule, Stop Rules, Handoff) earns its tokens with actionable, expert-level guidance.	3 / 3
Actionability	It gives concrete direction (named commands slate-ar-status / slate-ar-perf / slate-plan / slate-patch, explicit target-priority ranking, stop thresholds) but provides no executable benchmark command, metric definition, or packet schema; guidance is instructive but not copy-paste ready.	2 / 3
Workflow Clarity	Multi-step flow is clearly sequenced (load status → pick target → run perf with no-regression checks → stop rules) with an explicit correctness feedback loop that routes regressions to checks_failed/slate-patch and requires an oracle before optimizing.	3 / 3
Progressive Disclosure	A short single-file skill (~50 lines) with well-organized sections and no external bundle files to navigate; under the simple-skill rule this is appropriately self-contained with clear section structure.	3 / 3
	Total	11 / 12 Passed

Description

67%

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 specific, third-person description that names concrete actions and a clear niche, but it omits an explicit 'Use when...' trigger clause, relying on implied timing, so completeness is capped at 2. Trigger terms lean on Slate jargon over natural user phrasing.

Suggestions

Append an explicit 'Use when the user says make it fast, fastest, or perf, or wants the highest-value Slate v2 performance target' clause to the description so both 'what' and 'when' are explicit.

Add a few natural user-facing trigger terms (e.g., 'make it fast', 'speed up Slate') alongside the Slate-specific jargon to broaden keyword coverage.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions in third person: 'Picks or creates the hottest perf target, runs slate-ar-perf with no-regression checks, and stops at target, plateau, or correctness blocker.'	3 / 3
Completeness	The description clearly answers 'what does this do' but lacks an explicit 'Use when...' clause equivalent; the 'when' trigger is only implied via 'fastest-safe' and must be inferred, which caps completeness at 2 per the judging guidelines.	2 / 3
Trigger Term Quality	Includes some natural terms ('perf', 'fastest-safe', 'hottest perf target') but is heavier on Slate-specific jargon ('slate-ar-perf', 'correctness blocker') than on phrases a user would naturally say, and 'make it fast'/'fastest' triggers live only in the body, not the description.	2 / 3
Distinctiveness Conflict Risk	The Slate v2 / slate-ar-perf framing carves a clear niche with domain-specific triggers unlikely to fire for unrelated skills.	3 / 3
	Total	10 / 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-fast/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.