CtrlK
BlogDocsLog inGet started
Tessl Logo

dual-edition-module-migration

Migrate modules between shared `src/opensource/` code and enterprise overlays under `enterprise/src/opensource/`, while preserving the `src/opensource` boundary and existing component override points.

58

Quality

67%

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 ./frontend/magic-web/.agents/skills/dual-edition-module-migration/SKILL.md
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 content is highly actionable with a clear, validated migration workflow, but it is long and repeats rules across sections, and it leans on a single broken external reference instead of splitting detail into real bundle files.

Suggestions

Create the referenced `examples.md` (or remove the dead link) and move the 15 pitfalls and/or the 6 architecture patterns into a separate reference file to slim the inline body.

Dedupe rules that recur across Core invariants, Architecture patterns, Common pitfalls, and the checklists (e.g. the 'do not use enterprise/components for dual-edition modules' rule) into a single canonical statement.

DimensionReasoningScore

Conciseness

The body assumes Claude's competence (no explanation of Vite overlays or editions) and stays actionable, but ~464 lines repeat the same rules across Core invariants, Architecture patterns, Migration workflow, Common pitfalls, and checklists (e.g. the 'no enterprise/components path' and stub-mismatch rules recur several times), so it could be tightened.

2 / 3

Actionability

It provides concrete file paths, executable commands (`rg "ModuleName|useModuleName"`), a decision table by artifact type, and copy-paste-ready TypeScript stub examples with exact return shapes.

3 / 3

Workflow Clarity

The migration workflow is clearly sequenced (steps 0 through 6) with explicit validation checkpoints (find all importers first, run lint/tests, iterative build verification) and Boundary/Verification checklists covering destructive file moves and deletions.

3 / 3

Progressive Disclosure

Most content (15 pitfalls, 6 architecture patterns, full workflow) lives inline in a ~464-line monolithic body, and the only signaled reference, [examples.md](examples.md), does not exist on disk; the sectioning is clear but content that should be separate is inline and the one reference is dead.

2 / 3

Total

10

/

12

Passed

Description

57%

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 and distinctive about its niche but omits an explicit 'Use when...' trigger clause, capping completeness at 2, and its trigger terms lean on internal path jargon rather than natural user phrasing.

Suggestions

Add an explicit trigger clause such as 'Use when migrating modules that must exist in both open-source and enterprise editions, or when the user mentions `src/opensource`, `enterprise/`, or the Vite overlay.'

Broaden trigger terms with natural user phrasing (e.g., 'dual-edition module', 'enterprise overlay', 'open-source boundary') beyond raw path strings.

DimensionReasoningScore

Specificity

Names the domain and a couple of concrete actions ('Migrate modules between shared `src/opensource/` code and enterprise overlays', 'preserving the `src/opensource` boundary and existing component override points'), but does not enumerate multiple specific actions like the top anchor requires.

2 / 3

Completeness

It clearly answers 'what does this do', but there is no 'Use when...' clause or equivalent explicit trigger guidance, so per the guidelines 'when' is only implied and completeness is capped at 2.

2 / 3

Trigger Term Quality

It uses some relevant terms a developer on this codebase would say ('Migrate modules', 'enterprise overlays', 'src/opensource'), but they are heavily path-based jargon and lack the natural user-facing variations the top anchor rewards.

2 / 3

Distinctiveness Conflict Risk

The dual-edition `src/opensource`/`enterprise/src/opensource` overlay model is a clear, narrow niche with distinct triggers that is very unlikely to fire for an unrelated skill.

3 / 3

Total

9

/

12

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

relative_links

Relative link issues: 1 missing

Warning

Total

15

/

16

Passed

Repository
dtyq/magic
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.