CtrlK
BlogDocsLog inGet started
Tessl Logo

webiny-v5-to-v6-migration

Migration patterns for converting v5 Webiny code to v6 architecture. Use this skill when migrating existing v5 plugins to v6 features, converting context plugins to DI services, adapting v5 event subscriptions to v6 EventHandlers, or understanding how v5 patterns translate to v6. Targeted at AI agents performing migrations.

67

Quality

81%

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

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 thorough, highly actionable migration reference with excellent concrete v5→v6 code, but it is monolithic — large enough that splitting per-pattern detail into referenced files would improve navigation and token efficiency, and the repeated registry-lookup boilerplate could be consolidated.

Suggestions

Split patterns 7–11 (and the longer migration-map tables) into reference files under references/ and link to them from a concise overview, moving the skill toward one-level-deep progressive disclosure.

Consolidate the three near-identical 'Looking up X by type' registry-injection blocks into a single shared example referenced once, instead of repeating the full block per pattern.

Add a short top-level migration workflow (e.g., identify pattern → apply v6 equivalent → verify types from source → test) so the patterns hang together as a sequenced process.

DimensionReasoningScore

Conciseness

Mostly efficient reference material, but the near-identical 'Looking up X by type' registry blocks in patterns 7, 9, and 10 and repeated createFeature registration boilerplate add tokens that could be factored out.

3 / 5

Actionability

Every pattern ships concrete, copy-paste-ready v5 and v6 TypeScript with imports, interface implementation, and feature registration — fully executable guidance covering the common migration cases.

5 / 5

Workflow Clarity

Patterns are clearly numbered and the Type Resolution Guide is an explicit 3-step sequence with a verify-from-source checkpoint, but there is no overall migration workflow tying the patterns into a sequenced process.

4 / 5

Progressive Disclosure

Content is a single 755-line monolithic SKILL.md with no references/, scripts/, or assets/ bundle files; the repeated per-pattern detail is inlined rather than split into one-level-deep reference files, though in-file headers provide some structure.

3 / 5

Total

15

/

20

Passed

Description

92%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 in third person that clearly answers both what the skill does and when to use it, with concrete migration triggers. Minor room to add common synonyms/version strings for trigger coverage.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'converting v5 plugins to v6 features', 'converting context plugins to DI services', 'adapting v5 event subscriptions to v6 EventHandlers' — giving comprehensive coverage of the migration surface.

5 / 5

Completeness

Explicitly states the 'what' (migration patterns v5→v6) and an explicit 'Use this skill when...' trigger clause enumerating several concrete scenarios.

5 / 5

Trigger Term Quality

Includes natural terms a migrator would say ('v5 plugins', 'context plugins', 'DI services', 'event subscriptions', 'EventHandlers'); a few synonyms or version-string variants are missing, so it stops just short of comprehensive.

4 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (v5→v6 Webiny migration) with distinct triggers and minimal overlap risk against other Webiny skills.

5 / 5

Total

19

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

SKILL.md is long (765 lines); consider splitting into references/ and linking

Warning

Total

15

/

16

Passed

Repository
webiny/webiny-js
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.