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%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.

The body is a dense, actionable, well-sequenced migration guide with strong workflow clarity and concrete examples, but it suffers from a broken external reference and bulk content that could be progressively disclosed into separate files.

Suggestions

Create the missing `examples.md` (or remove the dead link) so the 'Additional resources' reference resolves to a real bundle file.

Move the long Pattern A-F and/or Pitfall catalogues into one-level-deep reference files (e.g., `patterns.md`, `pitfalls.md`) and keep SKILL.md as a tighter overview with signaled links, improving progressive disclosure.

Tighten the near-duplicate rules repeated across the Core invariants, Architecture patterns, and Boundary checklist to reduce redundancy.

DimensionReasoningScore

Conciseness

The body is long but nearly every token is high-signal domain guidance (invariants, pattern rules, pitfalls, checklists) that Claude would not already know; minor near-duplicate rules across Patterns and checklists could be trimmed.

4 / 5

Actionability

Provides concrete file paths, copy-paste TypeScript snippets, an artifact-type decision table, an `rg` command, and exact stub return shapes; a few snippets are illustrative rather than fully runnable, which is justified by the pattern-based nature.

4 / 5

Workflow Clarity

A clearly numbered Migration workflow (steps 0, 0.5, 0.6, 1-6) with explicit verification and boundary checklists and feedback loops ('fix missing mirrored dependencies iteratively') for destructive/batch operations.

5 / 5

Progressive Disclosure

Good section structure and a decision table, but the body references `examples.md` which does not exist in the bundle, and large amounts of pattern/pitfall detail are inlined rather than split into reference files.

3 / 5

Total

16

/

20

Passed

Description

57%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.

The description states a clear, distinctive purpose with concrete named actions, but it omits any explicit 'when to use' trigger guidance and relies on technical jargon rather than natural-language trigger phrases.

Suggestions

Add an explicit 'Use when...' clause listing trigger phrases users would actually say (e.g., 'Use when migrating a module to be dual-edition, when the user mentions `src/opensource`, `enterprise/`, Vite overlay, or edition-specific overrides').

Expand the action list slightly so it lists several specific concrete actions (classify target, add mirrored overlay, switch callers to `@/opensource/...`, delete old `variant` facades) to lift specificity above 3.

Add a plain-language synonym or two alongside the technical terms to broaden natural trigger coverage.

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 list several specific actions, so it stops at 'domain + 1-2 concrete actions'.

3 / 5

Completeness

Has a clear 'what' but no explicit 'Use when...' / 'when' clause; per the judging guidelines a missing trigger clause caps completeness at 3.

3 / 5

Trigger Term Quality

Includes domain-natural terms like `src/opensource`, `enterprise/`, 'overlays', and 'component override points', but these are mostly technical jargon with limited synonym or plain-language coverage.

3 / 5

Distinctiveness Conflict Risk

Targets a very specific niche (dual-edition open-source/enterprise module migration with a named boundary), making it highly distinguishable with minimal conflict risk.

5 / 5

Total

14

/

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

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.