CtrlK
BlogDocsLog inGet started
Tessl Logo

slate-ar-status

Read-only status shortcut for Slate v2 Autoresearch. Shows current session state, dashboard URL, next recommended action, blockers, and latest metric evidence without running packets or editing files.

68

Quality

83%

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

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 operator contract with concrete commands, explicit boundaries, and no wasted tokens. As a simple read-only skill it satisfies the relaxed bars for workflow clarity and progressive disclosure at the top level.

DimensionReasoningScore

Conciseness

The body is lean with no padding or explanations of concepts Claude already knows — every line ('Handle $ARGUMENTS...', the Contract bullets, the closing framing) earns its place.

3 / 3

Actionability

Gives concrete, executable guidance: specific commands ('state', 'onboarding-packet', 'recommend-next'), a concrete path and flag ('--cwd .tmp/slate-v2'), and explicit do-not-run boundaries, which qualifies as specific actionable instruction even though it is not copy-paste code.

3 / 3

Workflow Clarity

This is a simple single-purpose read-only skill whose single action ('loading slate-ar and running its read-only status mode') is unambiguous; it involves no destructive or batch operations, so no validation checkpoints are required for a top score.

3 / 3

Progressive Disclosure

Under 50 lines with no need for external references, and well-organized with a heading, a one-line trigger, and a clearly labeled Contract section — matching the rubric note that short self-contained skills can score 3 on organization alone.

3 / 3

Total

12

/

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.

The description is specific and distinct, naming concrete read-only outputs and a clear niche, but it omits an explicit 'Use when' trigger clause and leans on specialized jargon over natural user phrasing. These gaps cap completeness and trigger-term quality at 2.

Suggestions

Add an explicit 'Use when...' clause naming natural user phrasings (e.g., 'Use when the user asks for the status, progress, or current state of the Slate v2 Autoresearch loop').

Soften jargon by including common variations alongside 'Slate v2 Autoresearch' (e.g., 'Slate AR', 'autoresearch loop status') so trigger terms match what users actually say.

Mirror the body's single trigger sentence into the description so completeness covers both what and when in the frontmatter alone.

DimensionReasoningScore

Specificity

Lists multiple concrete capabilities — 'current session state, dashboard URL, next recommended action, blockers, and latest metric evidence' — matching the anchor for listing several specific concrete actions.

3 / 3

Completeness

It clearly states what the skill does but lacks an explicit 'Use when...' trigger clause in the description, so per the guideline a missing explicit when clause caps completeness at 2.

2 / 3

Trigger Term Quality

Contains relevant terms ('Slate v2 Autoresearch', 'status') but they are specialized jargon with no common natural-language variations a user would say, so it lands at 'some relevant keywords but missing common variations' rather than full coverage.

2 / 3

Distinctiveness Conflict Risk

The narrow 'read-only status shortcut for Slate v2 Autoresearch' niche with explicit do-not-run boundaries makes it clearly distinguishable and unlikely to trigger for the wrong skill.

3 / 3

Total

10

/

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.