slate-ar-quality

Slate v2 quality-gap Autoresearch shortcut. Runs deep-research and quality-gap loops for API/DX/architecture/test coverage gaps, then routes accepted findings to slate-patch, slate-plan, slate-ar-gate, or slate-ar-perf.

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-quality/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 tight, well-structured instruction set: concrete commands with real flags, an explicit safety gate on the destructive apply operation, and a clear routing table. It assumes Claude's competence and adds only what is non-obvious.

Dimension	Reasoning	Score
Conciseness	The body is lean (~40 lines) with no padding and no explanation of concepts Claude already knows; every line states a contract, command, or routing rule that earns its place.	3 / 3
Actionability	It gives concrete CLI subcommands with real flags (research-setup/quality-gap/gap-candidates with --cwd, --slug, --goal, --research-slug, --list/--apply) and a concrete gap-type→skill routing table; only the wrapper binary and runtime args are templated.	3 / 3
Workflow Clarity	The command order conveys the research-setup → quality-gap → gap-candidates → apply sequence, and the destructive --apply has an explicit validation gate ('only after inspecting the candidates and deciding the write scope is safe'), so it is not capped at 2.	3 / 3
Progressive Disclosure	This is a sub-50-line skill with no need for external references, and the content is well-organized into Contract, Commands, and Routing sections, which per the scoring notes warrants a 3.	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 is specific and action-oriented, clearly stating what the skill runs and where it routes findings. Its main weaknesses are the absence of an explicit 'Use when…' trigger clause and trigger terms that lean technical rather than natural.

Suggestions

Add a 'Use when…' clause naming natural triggers, e.g. 'Use when the user wants to broaden Slate v2 coverage beyond a single bug — API/DX gaps, architecture gaps, missing behavior coverage, or broad make-this-better research.'

Soften jargon in the description ('Autoresearch shortcut', 'deep-research and quality-gap loops') toward phrasings users would actually say, such as 'researches quality gaps' or 'finds coverage gaps'.

Sharpen distinctiveness from the sibling slate-ar skill by stating up front that this is the orchestrator that researches gaps and routes them, versus slate-ar's generic measured-loop role.

Dimension	Reasoning	Score
Specificity	The description lists multiple concrete actions: "Runs deep-research and quality-gap loops" and "routes accepted findings to slate-patch, slate-plan, slate-ar-gate, or slate-ar-perf", naming both the core mechanics and four specific downstream targets.	3 / 3
Completeness	It clearly answers what the skill does, but there is no "Use when…" clause or equivalent explicit trigger guidance, which per the judging guidelines caps completeness at 2.	2 / 3
Trigger Term Quality	Relevant terms like "quality-gap" and "API/DX/architecture/test coverage gaps" are present, but the phrasing leans technical ("Autoresearch shortcut", "deep-research and quality-gap loops") and omits common natural variations a user might actually say.	2 / 3
Distinctiveness Conflict Risk	It carves out a clear Slate v2 niche (research + routing), but the dense slate-ar family (slate-ar, slate-ar-gate, slate-ar-perf, slate-patch, slate-plan) creates real overlap risk with closely related skills.	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-quality/SKILL.md
Commit: 45116fd

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