CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

sync-plate-ui

Sync Plate registry UI into downstream apps with fork-aware comparison, scoped apply and changelog tracking.

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/sync-plate-ui/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

77%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.

A disciplined, agent-native workflow document: imperative, specific, and unusually strong on validation with its start/completion gates, pre-apply revalidation, and review verdicts. The weaknesses are structural rather than instructional — reference material is inlined in a monolithic file, and a small amount of constraint repetition could be consolidated.

Suggestions

Move stable reference material into one-level-deep files (e.g. references/plan-shape.md for the plan template and decision taxonomy, references/target-state.md for the status.json/fork-ledger schemas, references/potion-example.md for the file-by-file inspection list) and keep SKILL.md as the mode/dispatch overview.

Make verification concrete: name the actual commands per package manager (e.g. `pnpm typecheck`, `pnpm test --filter`) or state how to derive them, so apply-mode verification is copy-paste ready instead of a placeholder.

Consolidate the duplicated whole-file-overwrite rules (stated in Core Take, Three-Way Classification, and Apply Mode) and the planning-mode constraints (repeated between Flow Modes and Planning Mode) into single authoritative sections.

DimensionReasoningScore

Conciseness

The body is dense, imperative, and assumes Claude's competence throughout — no space is spent explaining what Plate, registries, or three-way merges are. It falls short of anchor 5 due to mild redundancy: planning/apply constraints appear in both "Flow Modes" and the dedicated "Planning Mode"/"Apply Mode" sections, and the whole-file-overwrite caution is stated three times ("Core Take", "Three-Way Classification", "Apply Mode").

4 / 5

Actionability

Guidance is overwhelmingly concrete: exact paths (`apps/www/src/registry/registry-editor.ts`, `<target>/.plate-ui-sync/runs/<date>-<scope>/plan.md`), a full `status.json` schema, invocation examples (`sync-plate-ui plan ../potion code-block`), a copyable apply payload, plan-shape and output templates. Not anchor 5 because a few steps stay abstract — "run focused target verification" and "run focused target typecheck, lint and test" name no commands, and verification commands are left as `<commands/results>` placeholders.

4 / 5

Workflow Clarity

The multi-step process is explicitly sequenced with validation checkpoints: a "Start Gates" checklist, mode-by-mode may/must-not rules, a pre-apply loop (re-read plan, recompute classification, confirm row still valid, record verification commands), "Completion Gates" for both planning and apply, and a review mode with verdicts (fresh/stale-plate/stale-target/blocked) that functions as an error-recovery feedback loop. This is an anchor-5 match — checklists plus feedback loops for a destructive-capable workflow — and the destructive-operation cap does not apply since validation is present, not missing.

5 / 5

Progressive Disclosure

No bundle files exist (references/, scripts/, assets/ are all absent), so the entire ~500-line workflow lives inline in SKILL.md. Section headers make it navigable, but self-contained reference material — the `status.json` schema, the Potion file-by-file inspection list, the plan-shape and dashboard-payload templates — is exactly the content that belongs in one-level-deep reference files. That matches anchor 3 ("some structure... content that should be separate is inline"); it is above anchor 2 because the inline material is well organized, and below anchor 4 because nothing is split out.

3 / 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.

A specific, correctly voiced, jargon-appropriate description that names a distinct niche but reads like a capability summary rather than a trigger. Its main weakness is the absent "when to use" guidance and thin synonym coverage, which leave discovery to users who already know the exact terms.

Suggestions

Append an explicit trigger clause, e.g. "Use when syncing Plate UI registry components into an app that copied and customized Plate (like Potion), or when the user mentions Plate registry, fork drift, or registry changelog sync."

Add natural-language synonyms users would actually say — "Plate UI", "component sync", "potion", "copy-pasted registry components" — so the skill triggers without the user naming the exact workflow.

Disambiguate from sibling skills in the description itself (e.g. "downstream consumer-side sync; not the shadcn↔Plate comparison skill") so the two do not compete for the same request.

DimensionReasoningScore

Specificity

The description lists several concrete actions — "Sync Plate registry UI into downstream apps", "fork-aware comparison, scoped apply and changelog tracking" — in third person with no filler. It stops short of anchor 5 because coverage is not comprehensive: outputs like plans, dashboards, and the status/fork-ledger state are never hinted at.

4 / 5

Completeness

The "what" is clear (sync, compare, apply, track) but there is no "Use when..." clause or equivalent trigger guidance, which caps completeness at 3 per the rubric. It cannot score 2 because the what-side is concrete and multi-action, not vague.

3 / 5

Trigger Term Quality

Relevant domain keywords are present ("Plate registry UI", "sync", "fork", "changelog", "downstream apps") but there are no common variations or synonyms — nothing like "component library", "Plate UI", "potion", or the plain phrase a user would say when invoking this. It sits above anchor 2 (more than one or two generic keywords) but below anchor 4, where only a few natural terms are missing.

3 / 5

Distinctiveness Conflict Risk

"Sync Plate registry UI into downstream apps with fork-aware comparison" carves out a clear niche (Plate registry, forks, downstream targets) with minimal generic surface. It is not a 5 because the skill's own body concedes overlap risk with sibling skills — "This is not `sync-shadcn`" — which the description does nothing to disambiguate.

4 / 5

Total

14

/

20

Passed

Validation

75%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 12 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

SKILL.md is long (523 lines); consider splitting into references/ and linking

Warning

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

12

/

16

Passed

Repository

udecode/plate

Path

.agents/skills/sync-plate-ui/SKILL.md

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.