slate-ar-perf

Slate v2 performance lane for Codex Autoresearch. Delegates generic loop mechanics to slate-ar/codex-autoresearch and adds target registry, fastest-safe stop rules, exactness gates, and pagination/virtualization defaults.

Quality

66%

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

Quality

Content

75%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 content is actionable, well-structured, and assumes Claude's competence, with concrete commands and validation checkpoints throughout. It sits just below top marks because the two default contracts are long and inlined rather than split into referenced files.

Dimension	Reasoning	Score
Conciseness	The body is dense and assumes domain competence without explaining basics, but the two full default contracts (Pagination, Huge Document Select-All) run long and could be trimmed, fitting the 4 anchor rather than the lean 5.	4 / 5
Actionability	Concrete copy-paste commands (pnpm bench:targets:list, bench-targets.mjs autoresearch-init) and METRIC line examples cover common cases, but the underlying benchmark scripts are referenced rather than shown, leaving minor gaps.	4 / 5
Workflow Clarity	The numbered Default Path sequences setup through validation (dry-run, pnpm bench:targets:check before AR init) and the Exactness Gate supplies keep/discard feedback loops, but the multi-mode structure is not a single fully-validated linear workflow.	4 / 5
Progressive Disclosure	No bundle files exist and the body is well-sectioned with clear headers, but at over 200 lines with two complete default contracts inlined, some content could be split into reference files, matching the 4 rather than 5 anchor.	4 / 5
	Total	16 / 20 Passed

Description

58%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 clearly distinct, but it answers only "what" and omits any "when to use" trigger guidance, which caps completeness. Trigger terms are present but jargon-heavy and lack natural synonyms.

Suggestions

Append an explicit 'Use when...' clause naming natural user phrases (e.g., 'Use when the user says fast, fastest, pagination, virtualization, benchmark, or asks to speed up a Slate v2 surface').

Soften jargon and add common synonyms in the description so trigger matching fires on plain-language requests, not just internal terms like 'exactness gates' or 'loop mechanics'.

Dimension	Reasoning	Score
Specificity	Names the domain and lists several concrete additions — "target registry, fastest-safe stop rules, exactness gates, and pagination/virtualization defaults" — with only minor coverage gaps, fitting the 4 anchor better than the fully comprehensive 5.	4 / 5
Completeness	The "what" is clear (performance lane that delegates and adds specific gates), but there is no "Use when..." or equivalent explicit trigger guidance, so completeness is capped at 3 per the rubric guideline.	3 / 5
Trigger Term Quality	Contains some natural terms ("performance", "fastest", "pagination", "virtualization") but leans on technical jargon ("Codex Autoresearch", "loop mechanics", "exactness gates") and misses common user synonyms, matching the 3 anchor.	3 / 5
Distinctiveness Conflict Risk	It carves a clear niche ("Slate v2 performance lane for Codex Autoresearch") with distinct triggers, with only minor overlap risk against sibling skills like slate-ar and slate-patch.	4 / 5
	Total	14 / 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-perf/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.