CtrlK
BlogDocsLog inGet started
Tessl Logo

plate-plugin-creator

Build new Plate plugins with Slate-first architecture, sane typing, and explicit React/Plate wrapper boundaries. Use when authoring or refactoring Plate plugin packages, deciding between createSlatePlugin vs createPlatePlugin, defining plugin APIs/transforms/options, or lifting semantic base plugins into React/Plate wrappers.

65

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-plugin-creator/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.

A well-structured, repo-specific execution companion with concrete APIs, commands, code patterns, and a verification-ended workflow. Its main defect is progressive disclosure: three referenced rules files do not exist in the bundle, so the detailed guidance they promise is unreachable.

Suggestions

Ship the missing ./rules/creation-flow.md, ./rules/typing.md, and ./rules/composition.md files referenced by the body, or inline their essential content so the Detailed References links resolve.

De-duplicate the shared-KEYS rule so it lives in one place (e.g. Typing & Context) and is referenced rather than restated across Principles and Do Not Copy.

Replace the `...` ellipses in the Key Patterns code blocks with minimal complete bodies (or label them explicitly as elided templates) so the examples are copy-paste ready.

DimensionReasoningScore

Conciseness

Dense, imperative prose that assumes Plate/Slate competence and explains no basic concepts, but the KEYS/shared-keys rule is restated across Principles, Typing & Context, and Do Not Copy, so not every token earns its place.

4 / 5

Actionability

Concrete APIs, file paths, the `pnpm brl` command, and real TypeScript pattern examples cover the common cases, but code blocks use `...` ellipses and key detail is deferred to the rules files.

4 / 5

Workflow Clarity

A numbered 7-step workflow ends with a verification step, the barrel flow has a fix-and-retry feedback loop, and the north-star gate plus derived checklist add checkpoints, though some validation remains implicit.

4 / 5

Progressive Disclosure

Section structure and signaling are good and the audit reference is real and one level deep, but three of the four local references (./rules/creation-flow.md, typing.md, composition.md) are dangling, breaking navigation.

3 / 5

Total

15

/

20

Passed

Description

88%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, specific description that clearly answers both what the skill does and when to use it, anchored by concrete Plate API names. Minor overlap risk with sibling doctrine skills and slightly jargon-heavy triggers keep it just short of perfect.

DimensionReasoningScore

Specificity

Lists multiple concrete actions and names specific APIs ('createSlatePlugin vs createPlatePlugin', 'defining plugin APIs/transforms/options', 'lifting semantic base plugins into React/Plate wrappers'), giving comprehensive coverage rather than just 1-2 actions.

5 / 5

Completeness

Explicitly states what ('Build new Plate plugins with Slate-first architecture, sane typing, and explicit React/Plate wrapper boundaries') and an explicit 'Use when...' clause with concrete trigger phrases.

5 / 5

Trigger Term Quality

Strong natural triggers for this niche ('authoring or refactoring Plate plugin packages', specific factory names), but the terms are jargon-heavy and lack the synonym/extension variations the top anchor calls for.

4 / 5

Distinctiveness Conflict Risk

Clear niche with distinctive API-name triggers, but 'defining plugin APIs/transforms/options' has minor overlap with the closely-related north-star skill that owns API shape.

4 / 5

Total

18

/

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.

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

relative_links

Relative link issues: 7 missing, 4 suspicious

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.