slate-ar-finalize

Finalization shortcut for Slate v2 Autoresearch. Runs preview-only finalization by default, explains review-branch/current-tree options, and requires explicit review-branch approval before branch creation.

Quality

72%

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

Quality

Content

82%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 a tight, actionable safety contract with concrete commands and explicit approval checkpoints gating destructive operations. It is well-structured and defers detail to the referenced slate-ar skill appropriately.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Claude's competence: no concept explanations, no padding, every line is an actionable rule or concrete command, matching the 'lean and efficient; every token earns its place' anchor.	5 / 5
Actionability	Concrete commands ('finalize-preview --cwd .tmp/slate-v2', 'finalize-current-tree') and exact approval wording are provided with only minor gaps, fitting the 'mostly executable guidance' anchor rather than the fully copy-paste-ready 5 anchor.	4 / 5
Workflow Clarity	A clear sequence (preview first → report warnings → explicit approval before any mutation) with explicit validation/approval checkpoints is present; the destructive-operation cap at 3 does not apply because approval gating and warning reporting are the core of the skill.	4 / 5
Progressive Disclosure	Well-organized 'Default contract' section with a clearly signaled one-level-deep reference ('The detailed safety rules live in slate-ar'); not a 5 because the reference is not a navigable link and structure could be slightly tighter.	4 / 5
	Total	17 / 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 clearly distinct, with concrete third-person actions and a well-defined niche. Its main weakness is the absence of an explicit 'when to use' trigger clause and reliance on jargon over natural user phrasing.

Suggestions

Add an explicit 'Use when ...' clause naming the natural trigger phrases users would say (e.g., 'Use when the user wants to finalize, wrap up, or create review branches for Slate AR work').

Soften internal jargon with common synonyms so the description reads as natural user language rather than tool-internal terminology.

Dimension	Reasoning	Score
Specificity	Names the domain ('Slate v2 Autoresearch finalization') and lists several concrete actions — 'Runs preview-only finalization', 'explains review-branch/current-tree options', 'requires explicit review-branch approval' — with only minor coverage gaps, matching the 4 anchor better than the more comprehensive 5 anchor.	4 / 5
Completeness	The 'what' is clearly stated, but there is no explicit 'Use when...' clause or equivalent trigger guidance; per the rubric a missing explicit trigger caps completeness at 3.	3 / 5
Trigger Term Quality	Relevant domain terms ('finalize', 'review-branch', 'current-tree', 'preview', 'branch creation') are present but the phrasing leans heavily on internal jargon rather than the natural variations/synonyms a user would say, fitting the 'some relevant keywords but missing common variations' anchor.	3 / 5
Distinctiveness Conflict Risk	The 'Slate v2 Autoresearch finalization' niche is highly specific with distinct triggers and minimal overlap risk with other skills, matching the clear-niche anchor.	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-finalize/SKILL.md
Commit: 8f65d77

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.