CtrlK
BlogDocsLog inGet started
Tessl Logo

slate-ar-next

Slate v2 Autoresearch daily driver. Reads current state, chooses the best next owner, and runs one safe next step without making the user pick quality/gate/perf/patch/finalize details.

65

Quality

80%

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-next/SKILL.md
SKILL.md
Quality
Evals
Security

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 routing skill: lean content, concrete skill-invocation guidance, a sequenced default workflow with an explicit read-only safety checkpoint, and clean section organization. No bundle files are present or needed.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence with no concept-overexplaining; every section is operational routing guidance, fitting the lean-and-efficient anchor rather than the padded anchor 2.

3 / 3

Actionability

Provides concrete executable guidance via specific skill names (e.g., `slate-ar-status`, `slate-ar-perfect`, `slate-patch`) and a numbered procedure; absence of code is appropriate for an instruction-only routing skill.

3 / 3

Workflow Clarity

The 'Default behavior' gives a clear 5-step sequence with an explicit safety checkpoint ('inspect read-only status before choosing any mutating owner') and a verification/report step, fitting the clear-sequence-with-validation anchor.

3 / 3

Progressive Disclosure

A single self-contained file under ~50 content lines with well-organized sections (Contract, Routing, Handoff) and no need for external references, satisfying the simple-skill allowance for a top score.

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 names a clear domain and three concrete actions but omits any explicit 'when to use' trigger and leans on Slate-internal jargon rather than natural user language. It also overlaps conceptually with the sibling skills it routes to.

Suggestions

Add an explicit 'Use when...' clause (e.g., 'Use when the user wants the next useful Slate v2 AR step without picking the specific owner').

Replace or supplement jargon like 'next owner' and 'quality/gate/perf/patch/finalize' with natural trigger terms a user would actually say.

Sharpen distinctiveness by stating what makes this skill the entry point versus the sibling slate-ar-* skills it routes to.

DimensionReasoningScore

Specificity

Lists multiple concrete actions ('Reads current state, chooses the best next owner, and runs one safe next step'), matching the multiple-specific-actions anchor rather than the single-action anchor 2.

3 / 3

Completeness

Clearly states what the skill does, but lacks any 'Use when...' or equivalent explicit trigger guidance, so completeness is capped at 2 per the rubric guideline.

2 / 3

Trigger Term Quality

Contains relevant domain keywords ('Slate v2 Autoresearch', 'quality/gate/perf/patch/finalize') but they are jargon rather than natural user phrasing, and no common variations are covered.

2 / 3

Distinctiveness Conflict Risk

The Slate v2 AR niche is specific, but the description explicitly routes among sibling slate-ar-* skills (perfect, status, ship, etc.), creating overlap risk with those similar skills.

2 / 3

Total

9

/

12

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.