CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

sync-shadcn

Sync upstream shadcn docs into Plate with source inventory, fork-aware apply and baseline accounting, or match shadcn's registry and install protocol source by source.

Quality

77%

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

Quality

Content

78%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 entrypoint that routes each mode to real, verified one-level-deep references and keeps itself lean, with concrete state-file and gate conditions inline. The only slack is mild redundancy in the ownership statements and the unspecified form of 'applicable verification', both of which live in the references by design.

DimensionReasoningScore

Conciseness

The body is a lean router with no concept over-explanation ('All procedures, examples, inventory shapes, commands and prompts live in the linked mode references'). Not 5 because ownership/scope rules are stated twice — in the opening paragraph and again in the 'forked product' paragraph — and could be merged.

4 / 5

Actionability

Concrete anchors are present ('Read docs/sync/shadcn/status.json and decisions.md', 'Record exact upstream SHAs', 'Advance lastSyncedCommit only after complete range accounting') alongside a per-mode command table. Not 5 because the body's own guidance stops at policy statements like 'this skill owns upstream range accounting', deferring all executable detail to the references.

4 / 5

Workflow Clarity

The sequence is clear (read policy, select mode, read state files, classify, plan, apply accepted rows) and checkpoints are named: 'Advance lastSyncedCommit only after complete range accounting and applicable verification' and 'Apply and revalidate only accepted rows'. Not 5 because 'applicable verification' is left unspecified in the body, so the feedback loop for this batch operation exists but its concrete form is only in the references.

4 / 5

Progressive Disclosure

A mode table gives well-signaled, one-level-deep links and every referenced file exists in the bundle (policy.md, planning.md, status.md, apply.md, dashboard.md, review.md, parity.md, plus scripts/build-dashboard.mjs backing the dashboard mode). The body also guards against drift ('Do not replace them with the entrypoint summary or create a parallel sync ledger'), matching the top anchor.

5 / 5

Total

17

/

20

Passed

Description

70%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 distinctive, domain-specific description that names its concrete actions and niche precisely, but it omits any 'Use when...' trigger guidance and leans on project-internal jargon ('baseline accounting', 'fork-aware apply') that a cold reader cannot parse. Adding an explicit trigger clause and one or two plain-language synonyms would lift the two weakest dimensions.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user asks to sync, update or port shadcn docs/components into Plate, or to mirror shadcn's registry or install protocol.'

Replace or gloss the insider terms 'fork-aware apply' and 'baseline accounting' with plain-language actions so the 'what' reads concretely without project context.

Include natural synonym phrasings users might say ('update from upstream', 'pull in shadcn changes', 'shadcn parity') to broaden trigger coverage.

DimensionReasoningScore

Specificity

Names several concrete actions ('Sync upstream shadcn docs into Plate', 'match shadcn's registry and install protocol source by source') covering both operating modes, but 'fork-aware apply' and 'baseline accounting' are insider jargon rather than plainly concrete actions, so coverage is not fully comprehensive.

4 / 5

Completeness

The 'what' is clear and covers both sync and parity modes, but there is no 'Use when...' clause or any equivalent explicit trigger guidance, which caps completeness at 3 per the rubric guidelines.

3 / 5

Trigger Term Quality

'shadcn', 'sync', 'Plate', 'registry' and 'install protocol' are exactly the natural terms a user in this repository would say when invoking the skill. Not 5 because common variations like 'update' or 'port shadcn components' are absent.

4 / 5

Distinctiveness Conflict Risk

The pairing of 'upstream shadcn docs into Plate' with 'registry and install protocol' carves out a clear niche with distinct trigger phrases; virtually no other skill would match these terms.

5 / 5

Total

16

/

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

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

13

/

16

Passed

Repository

udecode/plate

Path

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