plate-ui

Build new shadcn-style components for Plate's registry and editor surfaces. Use when authoring or refactoring registry UI/components, deciding what belongs in packages vs app-local component files, creating base/live kits and registry wiring, or applying React Compiler, Effects, accessibility, polymorphism, data-slot, data-state, and composable-component rules to Plate UI work.

Quality

88%

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

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 highly actionable with concrete code, commands, and a well-validated workflow, but it carries redundancy across its principle/test/law sections and its progressive-disclosure layer is undercut by eight referenced files missing from the bundle.

Suggestions

Consolidate the redundant Major-Release Law, Extraction Test, and Principles sections with the Ownership/Cross-Platform rules so each idea appears once and tokens are not spent restating it.

Resolve the broken reference layer: either include the six ./rules/*.md and two .agents/rules/plate-ui/references/*.md files in the bundle or remove the dead links so navigation to detail actually works.

Move the inline Critical Rules detail into the (shipped) rule files so SKILL.md stays a lean overview rather than carrying both the summary and the detail inline.

Dimension	Reasoning	Score
Conciseness	Largely efficient and assumes Claude's competence (no explanations of what React or shadcn are), but the Major-Release Law, Extraction Test, Principles, and Ownership rules substantially restate one another, so it could be tightened. Not level 3 because every token does not earn its place given the redundancy.	2 / 3
Actionability	Provides concrete executable-style TSX good/bad examples, a real command ("pnpm brl"), specific file paths, and copy-ready rules — matching the level-3 anchor for fully executable, specific examples.	3 / 3
Workflow Clarity	The 11-step Workflow is clearly sequenced with explicit validation checkpoints (step 9 changelog generation/check, step 10 brl, step 11 "Verify the smallest honest surface" with spec/build/browser sub-checks), matching the level-3 anchor for clear sequence with explicit validation steps.	3 / 3
Progressive Disclosure	Structure and signaling are good (clear overview, rules labeled "Load these only when the task needs the detail"), but scored against the actual bundle: only references/component-audit.md exists, while the six ./rules/.md and two .agents/rules/plate-ui/references/.md links point to files absent from the bundle, so the detailed-reference navigation largely does not resolve.	2 / 3
	Total	10 / 12 Passed

Description

100%

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 strong, third-person description that states concrete capabilities and gives explicit, multi-trigger "Use when" guidance scoped tightly to Plate UI work. It is concise, distinguishable from the generic shadcn skill, and free of fluff.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — "Build new shadcn-style components", "authoring or refactoring registry UI/components", "deciding what belongs in packages vs app-local component files", "creating base/live kits and registry wiring", and applying named rules (React Compiler, Effects, accessibility, polymorphism, data-slot, data-state) — matching the level-3 anchor for multiple specific concrete actions.	3 / 3
Completeness	Explicitly answers what ("Build new shadcn-style components for Plate's registry and editor surfaces") and when via a clear "Use when ..." clause with multiple triggers, satisfying the level-3 anchor for both what AND when with explicit triggers.	3 / 3
Trigger Term Quality	Natural domain terms a Plate/shadcn user would say are well covered — "shadcn-style components", "Plate's registry", "base/live kits", "registry wiring", "React Compiler", "Effects", "accessibility", "data-slot", "data-state". Not level 2 because coverage is broad rather than a single keyword missing common variations.	3 / 3
Distinctiveness Conflict Risk	Scoped narrowly to "Plate's registry and editor surfaces" and explicitly positioned as a companion to the generic shadcn skill, giving it a clear niche unlikely to trigger for unrelated skills.	3 / 3
	Total	12 / 12 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
relative_links	Relative link issues: 12 missing	Warning

	Total	13 / 16 Passed

Repository: udecode/plate
Path: .agents/skills/plate-ui/SKILL.md
Commit: 45116fd

Reviewed: about 14 hours 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.