CtrlK
BlogDocsLog inGet started
Tessl Logo
PluginPublic

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

Quality

90%

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

85%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 an exceptionally concrete orchestration script: verbatim prompts, dispatch tables, a config template, confirmation gates, and correction loops leave little ambiguity about what to do at each step. Its main weaknesses are repetition of the --auto/doc-scan-only behavior across three sections, and a bundle whose referenced agent/shared files are missing while its one shipped reference file is orphaned — which hurts navigation more than the in-file structure deserves.

Suggestions

Link references/spectrum-s2-upgrade.md from SKILL.md (e.g. in the Supporting Files section or wherever Admin UI web-src migration is discussed) — it is currently shipped but unreachable from the skill body.

Ensure all referenced bundle files (agents/analyzer.md, agents/events.md, agents/webhooks.md, agents/admin-ui-sdk.md, agents/business-config.md, agents/executor.md, shared/schema.md, shared/questions.md, shared/migration-warnings.md, shared/references.md) actually ship with the skill, since Steps 1–5 cannot execute without them.

State the doc-scan-only and --auto behaviors once (in the Confirmation protocol) and have Step 1/Step 3/Notes reference that section instead of re-specifying them; consider moving the metadata derivation rules into a shared/ file to slim the body.

DimensionReasoningScore

Conciseness

The body is dense, operational, and explains nothing Claude already knows — every block is an instruction, template, or rule. Minor trimming is possible: the doc-scan-only flow is fully specified twice (Confirmation protocol and again in Step 1's early-exit), and the Notes section recaps the --auto summary, env-var handling, and productDependencies rules already stated in Steps 3–4. That duplication is more than nothing but well short of the 'several unnecessary explanations' anchor at 3.

4 / 5

Actionability

Guidance is fully executable: exact agent dispatch instructions with file paths and payloads ('Pass mode = "doc-scan-only"... Pass the ProjectSnapshot JSON... Pass assembled config = null'), a complete defineConfig TypeScript template, a confidence→agent mapping table, verbatim output blocks, and precise metadata derivation rules (normalization steps, 50-char limits, boilerplate names to skip). Concrete specifics cover the common cases with no pseudocode.

5 / 5

Workflow Clarity

The Preflight → Step 1–5 sequence is explicit with validation at every risky point: preflight file checks, alreadyMigrated early-exit, [await] confirmation checkpoints, and error-recovery feedback loops ('Re-print summary with corrections and ask again until confirmed', 'Repeat until the developer confirms. Do NOT restart the entire flow'). For a destructive batch migration it also provides a rollback story (git branch, 'git checkout main to abandon'), matching the anchor for explicit validation steps plus feedback loops.

5 / 5

Progressive Disclosure

References are clearly signaled and one level deep (a Supporting Files section plus inline ${CLAUDE_SKILL_DIR} paths), but scored against the actual bundle they don't resolve: none of the ten referenced agents/*.md or shared/*.md files exist in the bundle, while the one bundled file, references/spectrum-s2-upgrade.md, is never linked from SKILL.md and is therefore unreachable. Long inline sections (the ~40-line metadata derivation rules, the doc-scan-only protocol) also belong in the shared/ files the skill already envisages. This fits 'some structure but could be better organized' rather than the well-placed anchor at 4.

3 / 5

Total

17

/

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 description: it states concrete capabilities for every mode of the skill and closes with an explicit, well-phrased 'Use when...' trigger clause covering both migration and upgrade intents. It is on the long side (~130 words) and could trim operational detail like the --auto summary behavior, and trigger coverage misses a few synonymous phrasings, but neither weakens its dispatch quality materially.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions with comprehensive coverage: 'Migrate an Adobe Commerce App Builder project... to the new App Management approach', 'scan README.md and env.dist for outdated content without modifying any files', and 'the action code is rewritten to read them with @adobe/aio-commerce-lib-config'. Every operational mode of the skill (--auto, --doc-scan-only, env-var migration) is explicitly stated, matching the anchor for multiple specific concrete actions rather than the minor-gaps level below.

5 / 5

Completeness

Both halves are explicit: the 'what' opens the description ('Migrate an Adobe Commerce App Builder project from the Integration Starter Kit or Checkout Starter Kit to the new App Management approach') and the 'when' is a concrete trigger clause ('Use when the user wants to migrate an App Builder project... or mentions upgrading their Adobe Commerce extension architecture'). This matches the anchor for clearly and explicitly answering both what AND when with concrete triggers.

5 / 5

Trigger Term Quality

Natural terms are well covered — 'migrate', 'Integration Starter Kit', 'Checkout Starter Kit', 'App Management', 'upgrading their Adobe Commerce extension architecture' — plus file-level triggers like 'README.md and env.dist'. However, a few plausible user phrasings are absent (e.g. 'aio', 'Commerce SDK', 'app.commerce.config'), which fits 'good keyword coverage; a few natural terms missing' rather than the comprehensive-synonyms anchor at 5.

4 / 5

Distinctiveness Conflict Risk

The niche is unambiguous — Adobe Commerce App Builder migration from two specifically named starter kits to a specifically named target approach — so triggers like 'Integration Starter Kit' or 'App Management' would not fire a generic skill. This is a clear niche with distinct triggers and minimal conflict risk.

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.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 10 missing

Warning

Total

15

/

16

Passed

Reviewed

On this page