CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

61

Quality

74%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/slate-ar-quality/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

86%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 concise, well-structured, and actionable with concrete commands and a real safety checkpoint for the batch apply step, with only minor gaps around placeholder commands and the absence of a full retry loop.

DimensionReasoningScore

Conciseness

Lean and efficient with no padding or explanation of concepts Claude already knows; every section (Contract, Commands, Routing, guardrail) earns its place and the quality_gap=0 clarification adds genuinely non-obvious state semantics.

5 / 5

Actionability

Provides concrete executable command templates with arguments and explicit routing rules, but uses placeholders (<autoresearch-cli>, <slug>, <goal>) rather than literal runnable commands, leaving a minor gap below fully copy-paste-ready.

4 / 5

Workflow Clarity

An implicit setup→list→candidates→apply→route sequence is present with an explicit validation gate ('Use gap-candidates --apply only after inspecting the candidates and deciding the write scope is safe'), but it lacks a numbered sequence and a full validate→fix→retry loop.

4 / 5

Progressive Disclosure

Under 50 lines with no bundle files, organized into clearly labeled sections (Contract, Commands, Routing) with no nested references, satisfying the simple-skill exception for a top score.

5 / 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 is specific and distinct, with clear capability and routing statements, but lacks an explicit 'Use when' trigger and leans on internal jargon rather than natural user phrases.

Suggestions

Add an explicit 'Use when...' clause stating the natural trigger phrases (e.g., 'Use when the user wants to perfect a Slate v2 surface beyond a single bug: API/DX/architecture gaps, missing coverage, or broad make-this-better research').

Replace or supplement jargon like 'Autoresearch shortcut' and 'slate-ar-gate' with user-facing terms so the trigger keywords match what a user would actually say.

Move the concrete gap categories (API/DX/architecture/test coverage, docs/reference holes, example quality) from the body into the description to raise specificity from 4 to 5.

DimensionReasoningScore

Specificity

Names the Slate v2 quality-gap domain and lists several concrete actions ('deep-research and quality-gap loops for API/DX/architecture/test coverage gaps') plus four routing destinations, but 'shortcut' is somewhat abstract so it falls just below the comprehensive 5.

4 / 5

Completeness

The 'what' is clear (runs research/quality-gap loops and routes findings), but the description lacks an explicit 'Use when...' trigger clause, which per the guidelines caps completeness at 3.

3 / 5

Trigger Term Quality

Relevant keywords like 'API/DX/architecture/test coverage gaps' and 'quality-gap' appear, but the phrasing is jargon-heavy ('Autoresearch shortcut', 'slate-ar-gate') and missing the natural phrases a user would actually say.

3 / 5

Distinctiveness Conflict Risk

Scoped to a clear niche (Slate v2 quality-gap autoresearch) and explicitly distinguishes routing to sibling skills (slate-patch, slate-plan, slate-ar-gate, slate-ar-perf), giving minimal conflict risk.

5 / 5

Total

15

/

20

Passed

Validation

81%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

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
Reviewed

Table of Contents

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.