CtrlK
BlogDocsLog inGet started
Tessl Logo

slate-ar-ship

Slate v2 one-command ship/readiness mini-skill. Runs finalization preview, picks the review shape, runs pre-commit gates/autoreview, pauses for commit approval, then commits/finalizes after confirmation.

60

Quality

72%

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

Quality

Content

77%

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 well-sequenced, actionable orchestration skill with strong validation checkpoints and feedback loops, but it is monolithic (no progressive disclosure into reference files) and carries duplicated guidance that could be tightened.

Suggestions

Deduplicate repeated rules — consolidate the 'autoresearch-review/*' branch prohibition and the READY-TO-COMMIT/confirmation rules into a single canonical statement to improve conciseness.

Extract the longer reference material (e.g., the Current Tree and Pre-Commit Review decision tables) into a reference file and link to it from a leaner SKILL.md overview to improve progressive disclosure.

DimensionReasoningScore

Conciseness

Directives are mostly lean and assume Claude's competence, but there is clear duplication — 'Do not create autoresearch-review/* branches' appears in both the Contract and Review And Commit sections, and the READY-TO-COMMIT pause/confirmation rules are restated across sections — so it sits at 'could be tightened' rather than fully lean.

2 / 3

Actionability

Provides concrete named commands (slate-ar-finalize, finalize-current-tree --exclude-session-artifacts, slate-ar-gate, autoreview, git) and specific file patterns (autoresearch.*, autoresearch.research/**) with explicit conditional logic; per the instruction-only scoring note this is actionable without code.

3 / 3

Workflow Clarity

Two clearly numbered sequences (8-step default path, 7-step pre-commit path) include explicit validation checkpoints and a feedback loop ('fix accepted P0/P1 findings ... then rerun the focused proof') plus a READY-TO-COMMIT gating pause, matching the clear-sequence-with-validation anchor.

3 / 3

Progressive Disclosure

No bundle files exist and the ~118-line body is a single monolithic file with sections but no reference splitting, so it has structure but content that could be separated remains inline — the level-2 anchor rather than a well-signaled multi-file overview.

2 / 3

Total

10

/

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 clearly occupies a distinct niche, but it lacks an explicit 'Use when...' trigger clause and mixes natural terms with internal jargon, capping trigger quality and completeness at 2.

Suggestions

Add an explicit 'Use when...' clause naming natural user phrasings (e.g., 'Use when the user wants to ship, review, or commit Slate v2 AR work') to lift completeness to 3.

Replace or gloss internal jargon ('AR', 'autoreview', 'finalization preview') with terms users would naturally say so trigger term quality reaches full coverage.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'Runs finalization preview, picks the review shape, runs pre-commit gates/autoreview, pauses for commit approval, then commits/finalizes' — matching the multiple-specific-actions anchor rather than the domain-only level 2.

3 / 3

Completeness

Clearly answers 'what' but provides no explicit 'Use when...' trigger clause, so per the rubric guideline a missing explicit-when clause caps completeness at 2 rather than 3.

2 / 3

Trigger Term Quality

Contains some natural terms ('ship', 'commit', 'review') but leans on internal jargon ('AR', 'autoreview', 'finalization preview') and misses common user phrasings, so it stops at 'some relevant keywords but missing common variations' rather than full coverage.

2 / 3

Distinctiveness Conflict Risk

The highly specific 'Slate v2 AR' ship/readiness niche with distinct triggers makes it unlikely to fire for the wrong skill, matching the clear-niche anchor.

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.