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.

Quality

77%

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

Quality

Content

92%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 lean, actionable, and well-structured for a simple read-only operator skill, scoring the top of the scale on conciseness, workflow clarity, and progressive disclosure. The only soft spot is actionability, where the delegated 'loading slate-ar' step and the serve/dashboard startup could be made more concrete.

Suggestions

Make the 'loading slate-ar' step concrete (e.g. show the exact invocation or how read-only status mode is selected) so the entry action is copy-paste ready.

Add one concrete example of the serve/dashboard command and how the dashboard URL is surfaced, since starting serve is listed as an allowed action without details.

Optionally show one example output format for the reported counts so the reporting spec is unambiguous.

Dimension	Reasoning	Score
Conciseness	Roughly 20 lines with no concept explanations and no padding; every line (including the negative-scope guardrail) earns its place and the skill assumes Claude's competence.	5 / 5
Actionability	Gives concrete commands ('state', 'onboarding-packet', 'recommend-next'), the '--cwd .tmp/slate-v2' flag, a concrete state path, and a reporting spec, but delegates mechanics to 'loading slate-ar' without showing how, leaving a minor gap below the copy-paste-ready 5.	4 / 5
Workflow Clarity	This is a single, unambiguous read-only action (load slate-ar, run status mode, report) well under 50 lines with no destructive or batch operations, so the simple-skill exception applies and the action is clearly specified with an explicit do/don't contract.	5 / 5
Progressive Disclosure	No bundle files exist and none are needed for a ~20-line skill; the body is organized into a title, a trigger line, and a 'Contract' section, satisfying the simple-skill exception for a clean 5.	5 / 5
	Total	19 / 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, distinctive, and well-scoped as a read-only status view, but it omits an explicit 'Use when...' trigger clause, which caps completeness, and it lacks trigger-term synonyms. Adding a concrete trigger phrase would raise both completeness and trigger_term_quality.

Suggestions

Add an explicit 'Use when...' trigger clause to the description, e.g. 'Use when the user asks where the Slate v2 Autoresearch loop stands or wants a read-only status snapshot.'

Include natural trigger synonyms users might say (e.g. 'status', 'where is the loop', 'progress', 'dashboard') to improve trigger_term_quality beyond the single domain term.

Consider adding '.tmp/slate-v2' or 'dashboard URL' as concrete trigger tokens to round out coverage toward a 5.

Dimension	Reasoning	Score
Specificity	Names the domain and lists several concrete capabilities ('Shows current session state, dashboard URL, next recommended action, blockers, and latest metric evidence'), landing between 'lists several specific actions' (4) and 'comprehensive coverage' (5).	4 / 5
Completeness	It clearly states 'what' the skill does, but a 'Use when...' trigger clause is absent from the description ('without running packets or editing files' is scope, not a trigger), so per the judging guidelines completeness is capped at 3.	3 / 5
Trigger Term Quality	The natural user term 'Slate v2 Autoresearch' is present, but the description lacks synonyms or variations a user might actually say; it does not reach the broad natural-term coverage of a 4.	3 / 5
Distinctiveness Conflict Risk	It carves out a clear niche (read-only status view for Slate v2 Autoresearch) with an explicit scope boundary, making overlap with other skills minimal.	5 / 5
	Total	15 / 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-status/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.