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.

71

Quality

88%

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

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 highly actionable with concrete code, commands, APIs, and a sequenced workflow with verification, but it is weakened by restated rules and by broken detailed-reference links — the core rules/*.md files it repeatedly points to are absent from the bundle.

Suggestions

Create the missing ./rules/creation-flow.md, ./rules/typing.md, and ./rules/composition.md files (or remove the references and inline the essential content), since three of the four detailed-reference links the body promises currently resolve to nothing.

Consolidate the Slate-first directive and KEYS guidance, which are restated across Principles, Critical Rules, Hard Law, and Do Not Copy, into one authoritative location to tighten token efficiency.

Verify each link target against the actual bundle before finalizing, so the 'Detailed References' section only lists files that exist.

DimensionReasoningScore

Conciseness

It assumes Claude's intelligence with no concept-explanation padding, but the Slate-first directive and KEYS guidance are restated across Principles, Critical Rules, Hard Law, and Do Not Copy, so it could be tightened; this fits 'mostly efficient but could be tightened' rather than 'every token earns its place'.

2 / 3

Actionability

Provides copy-paste-ready TS patterns (e.g. `createTSlatePlugin<BaseCommentConfig>({ key: KEYS.comment }).extendApi(...)`), concrete commands (`pnpm brl`), specific APIs (`toPlatePlugin`, `configurePlugin`, `inject.nodeProps.transformProps`), and exact file paths (`packages/utils/src/lib/plate-keys.ts`).

3 / 3

Workflow Clarity

A 7-step numbered Workflow ends in an explicit verification step ('Verify the smallest honest surface: package tests, type tests, React tests'), and the barrel rule supplies a feedback loop ('If pnpm brl produces a broken barrel, fix the barrel generator/config or file placement'), plus a derived checklist.

3 / 3

Progressive Disclosure

Structure and signaling are good (one-level-deep links under 'Creation Flow →', 'Typing & Context →', 'Composition & API Shape →', 'Detailed References'), but three of the four referenced detail files (./rules/creation-flow.md, ./rules/typing.md, ./rules/composition.md) do not exist in the bundle, so the navigation is broken and cannot score 3.

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.

The description is specific, complete, and well-triggered for its specialized Plate-plugin niche, covering concrete actions and explicit use-when guidance. It uses the imperative 'Use when...' form consistent with the rubric's good examples and avoids first/second-person voice penalties.

DimensionReasoningScore

Specificity

Lists multiple concrete actions such as 'Build new Plate plugins', 'refactoring Plate plugin packages', 'deciding between createSlatePlugin vs createPlatePlugin', and 'defining plugin APIs/transforms/options', naming specific APIs rather than vague language.

3 / 3

Completeness

Explicitly answers both what ('Build new Plate plugins with Slate-first architecture, sane typing, and explicit React/Plate wrapper boundaries') and when ('Use when authoring or refactoring Plate plugin packages...'), matching the anchored 'what AND when' pattern.

3 / 3

Trigger Term Quality

Triggers map to terms a Plate plugin author would naturally say ('authoring or refactoring Plate plugin packages', 'createSlatePlugin vs createPlatePlugin', 'lifting semantic base plugins into React/Plate wrappers'); the technical jargon is appropriate to this niche rather than generic.

3 / 3

Distinctiveness Conflict Risk

Scoped to a clear niche (Plate plugin mechanics, specific createSlatePlugin/createPlatePlugin APIs) with triggers unlikely to fire for generic or sibling skills.

3 / 3

Total

12

/

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

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.