CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

plate-ui

Use before editing any file under the registry components or kits, or a component's drag, drop, handle menu or indicator UI. Implements Plate React component families, copied registry UI and kit wiring with exact browser proof.

Quality

80%

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

Quality

Content

71%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 lean, expert-level rulebook with concrete paths, code patterns, and a well-sequenced workflow, but it is held back by a broken core reference (rules/registry.md) and the absence of an explicit browser-proof verification step that its own description promises. Fixing the reference link and adding a validation checkpoint would lift the two weakest dimensions.

Suggestions

Fix the broken ./rules/registry.md link in the "Registry Wiring" section — either ship the file in the bundle or inline its essential content, since following the link currently dead-ends.

Add an explicit browser-proof verification step (with a fix-and-retry loop) at the end of the workflow so the "exact browser proof" promised in the description has a concrete checkpoint.

Consolidate the plate-plugins ownership routing, which is stated three times across Repo Surfaces, Routing Gate, and Workflow, into a single place to save tokens.

DimensionReasoningScore

Conciseness

The body is dense and expert-level with no explanation of known concepts, but has minor trims available: "vercel-react-best-practices" is introduced twice (opening paragraph and its own section) and plate-plugins ownership routing is stated three times ("package edits route to plate-plugins", "Package implementation and proof still route to plate-plugins", Routing Gate). This matches efficient-with-minor-trimming rather than every-token-earns-its-place.

4 / 5

Actionability

Concrete file paths ("apps/www/src/registry/components/editor"), an eight-snippet Good/Bad Key Patterns block, and specific rules (kebab-case data-slot, Tailwind v4 syntax) give mostly executable guidance. The snippets are illustrative fragments without imports or context rather than copy-paste-ready code, keeping it below fully executable.

4 / 5

Workflow Clarity

The ten-step workflow is clearly sequenced with explicit pre-code checkpoints (decide ownership, React checks before state/effects, audit step 8). However, verification is implicit — despite the description promising "exact browser proof", no workflow step actually verifies the result in a browser, which is a minor validation gap.

4 / 5

Progressive Disclosure

The overview is well sectioned and references/component-audit.md is a real, clearly signaled, one-level-deep file, but the "Registry Wiring" section links ./rules/registry.md which does not exist in the bundle — a dead-end link for a core topic. Scoring against the actual bundle structure, this is a meaningful organization gap rather than the minor gap anchor 4 allows.

3 / 5

Total

15

/

20

Passed

Description

83%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 strong description that explicitly states both capability and trigger conditions in third person, with concrete repo-specific trigger phrases. Its only weaknesses are jargon-dense action wording and slight overlap with the sibling shadcn/plate-plugins skills it does not disambiguate against.

DimensionReasoningScore

Specificity

"Implements Plate React component families, copied registry UI and kit wiring with exact browser proof" lists several concrete actions (component families, registry UI, kit wiring, browser proof), matching the anchor for several specific actions with minor gaps. It is not comprehensive (omits changelog, styling, and ownership routing the body covers), so it does not reach 5.

4 / 5

Completeness

It explicitly answers both: what ("Implements Plate React component families, copied registry UI and kit wiring with exact browser proof") and when with concrete trigger phrases ("Use before editing any file under the registry components or kits, or a component's drag, drop, handle menu or indicator UI"). The when clause is maximally specific, so the anchor-4 caveat ("could be more explicit") does not apply.

5 / 5

Trigger Term Quality

Triggers include "registry components", "kits", "drag, drop", "handle menu", and "indicator UI" — natural phrases for this domain, giving good coverage. A few natural terms are missing (e.g., "editor", "toolbar", "shadcn component") and there are no synonyms or extensions, so it stops short of 5.

4 / 5

Distinctiveness Conflict Risk

It carves a clear niche (Plate React copied registry UI and kit wiring) with distinct trigger surfaces. There is minor overlap risk with closely related sibling skills (shadcn, plate-plugins), since "editing registry UI" could plausibly route to those too, which matches anchor 4 rather than 5.

4 / 5

Total

17

/

20

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.

Validation — 13 / 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

relative_links

Relative link issues: 1 missing

Warning

Total

13

/

16

Passed

Repository

udecode/plate

Path

.agents/skills/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.