CtrlK
BlogDocsLog inGet started
Tessl Logo

adobe/commerce-app-migration

Migrate an Adobe Commerce App Builder project from the Integration Starter Kit or Checkout Starter Kit to the new App Management approach. Run from the root of the App Builder project to be migrated. Pass --auto to skip confirmation prompts (suitable for CI or batch use).

62

Quality

78%

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

Overview
Quality
Evals
Security
Files

Quality

Content

60%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-sequenced, mostly actionable orchestration skill with strong workflow checkpoints, but it is somewhat verbose and its progressive-disclosure structure is broken: nearly all referenced supporting files are absent from the bundle and the one bundled reference is never linked.

Suggestions

Ship the referenced supporting files (agents/analyzer.md, agents/executor.md, agents/events.md, agents/webhooks.md, agents/admin-ui-sdk.md, agents/business-config.md, shared/schema.md, shared/questions.md, shared/migration-warnings.md) or inline their essential content so the skill is self-contained.

Link the existing references/spectrum-s2-upgrade.md from the body (e.g. in the Supporting Files section or an Admin UI SDK step) so the one bundled reference is reachable instead of orphaned.

Trim the "Notes" section (remove items that restate Steps 1-5) and condense the description-rewrite rules (lines 306-318) into a few concrete rules to reduce repetition.

DimensionReasoningScore

Conciseness

The ~395-line body is mostly concrete operational instruction but carries noticeable repetition — the "Notes" section re-summarizes steps already detailed above, the description-rewrite rules (lines 306-318) are over-elaborated, and the cross-cutting warning handling is restated — so it could be tightened meaningfully.

3 / 5

Actionability

Provides concrete, executable guidance — a copy-paste TypeScript config template, exact preflight file checks, exact output blocks, and explicit dispatch instructions — but key execution detail (file writes, CLI commands) is deferred to agent files that are not present, leaving minor self-contained-execution gaps.

4 / 5

Workflow Clarity

Clear five-step sequence (Preflight → Analyzer → parallel domain agents → Q&A → config assembly → Executor) with explicit [await] checkpoints, confirmation prompts, and correction/rejection feedback loops, though there is no explicit post-migration verification that the migrated project builds or is valid.

4 / 5

Progressive Disclosure

The body references nine agent/shared files via ${CLAUDE_SKILL_DIR}/ paths and a "Supporting Files" section, but none of those files exist in the bundle, while the one shipped bundle file (references/spectrum-s2-upgrade.md) is orphaned and never referenced — navigation to supporting material is effectively broken.

2 / 5

Total

13

/

20

Passed

Description

87%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 that explicitly states both what the skill does and when to use it, with natural domain trigger phrases and a clear, distinctive niche. Minor specificity gains are possible by framing capabilities as distinct actions rather than flag modes.

DimensionReasoningScore

Specificity

Lists several concrete actions — "Migrate an Adobe Commerce App Builder project...", "scan README.md and env.dist... without modifying any files", and the --auto/--doc-scan-only operational modes — but the actions are largely operational flag modes rather than a breadth of distinct capabilities, leaving minor coverage gaps.

4 / 5

Completeness

Clearly answers both — "what" ("Migrate an Adobe Commerce App Builder project... to the new App Management approach") and an explicit "when" with concrete triggers ("Use when the user wants to migrate... or mentions upgrading their Adobe Commerce extension architecture").

5 / 5

Trigger Term Quality

Good natural keyword coverage ("migrate", "App Builder project", "Integration Starter Kit", "Checkout Starter Kit", "upgrading their Adobe Commerce extension architecture") with a few natural synonyms (e.g. "modernize", "move off starter kit") missing.

4 / 5

Distinctiveness Conflict Risk

Highly specific niche (Adobe Commerce App Builder, Integration/Checkout Starter Kit, App Management approach) with distinct triggers and minimal overlap risk with other skills.

5 / 5

Total

18

/

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: 10 missing

Warning

Total

15

/

16

Passed

Reviewed

Table of Contents