slate-ar-recipe

Slate v2 Autoresearch recipe picker. Lists/recommends Codex Autoresearch recipes, produces read-only setup plans, and maps non-perf loops such as test runtime, typecheck, bundle size, memory, command latency, and quality-gap.

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

Quality

Content

93%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 tight, executable, well-organized recipe-picker skill: concrete commands, clear guardrails, a validation checkpoint, and a defined handoff. The only minor gap is that the multi-step flow is conveyed by section ordering rather than an explicit numbered sequence.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Claude's competence — tight sections (Contract, Built-In Recipe Uses, Commands, Handoff) with no padding or explanation of concepts Claude already knows, and every line carries operational value.	5 / 5
Actionability	Provides five copy-paste-ready, executable CLI commands with the concrete project path and flags, plus per-recipe routing guidance; the common cases (list, recommend, show, setup-plan, doctor) are all covered explicitly.	5 / 5
Workflow Clarity	The flow (recommend/list -> show -> setup-plan -> optional packet -> handoff) is clear and includes an explicit validation checkpoint ("run benchmark-lint before any packet") plus read-only guardrails; not a 5 because the sequence is implied by section order rather than an explicit numbered workflow with feedback loops.	4 / 5
Progressive Disclosure	At under 50 lines with no need for external references, the content is organized into four well-signaled sections with no nested references, matching the simple-skill exception for a clean 5.	5 / 5
	Total	19 / 20 Passed

Description

58%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 well-targeted to a clear niche, naming multiple concrete capabilities and loop types. Its main weakness is the missing explicit "Use when..." trigger clause, which caps completeness and slightly weakens trigger-term quality.

Suggestions

Add an explicit 'Use when...' clause naming natural user phrasings, e.g. 'Use when the user asks which Autoresearch loop to run or mentions test runtime, typecheck, bundle size, or memory bottlenecks.'

Soften jargon in the opening ('Autoresearch recipe picker', 'non-perf loops') with at least one plain-language synonym a user might actually say.

Clarify the activation boundary by contrasting with perf-oriented loops so it is unambiguous when this skill versus a perf skill should trigger.

Dimension	Reasoning	Score
Specificity	Lists several concrete actions — "Lists/recommends Codex Autoresearch recipes", "produces read-only setup plans", and "maps non-perf loops such as test runtime, typecheck, bundle size, memory, command latency, and quality-gap" — giving broad but not exhaustive coverage; not a 5 because it does not fully enumerate all recipe capabilities.	4 / 5
Completeness	The "what" is clear (lists/recommends recipes, produces setup plans, maps loops), but there is no explicit "Use when..." trigger clause, so per the judging guidelines completeness is capped at 3 with the "when" only weakly implied.	3 / 5
Trigger Term Quality	Domain terms like "test runtime", "typecheck", "bundle size", and "command latency" are relevant, but the framing leans on jargon ("Autoresearch recipe picker", "non-perf loops") and lacks the natural phrasings a user would actually say, with no synonyms or variations.	3 / 5
Distinctiveness Conflict Risk	The niche is highly specific ("Slate v2", "Codex Autoresearch recipes") with minimal overlap risk against other skills; not a 5 because the absent trigger guidance makes the activation boundary slightly less crisp.	4 / 5
	Total	14 / 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-recipe/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.