CtrlK
BlogDocsLog inGet started
Tessl Logo

testland/mv2-to-mv3-migration-test-checklist

Build-an-X workflow that emits a per-extension MV2 → MV3 migration test checklist. Walks the six canonical migration sections (manifest, service worker, API calls, declarative net request, security, publication) per the Chrome migration checklist, then for each one inventories the source MV2 manifest, names the MV3 replacement field / API, and emits the verification test cases. Covers the Firefox-Chrome divergence cells (page_action retained in Firefox, event pages allowed in Firefox 106+, host-permission install-prompt behavior changed in Firefox 127, web_accessible_resources `use_dynamic_url` Chromium-only). Output: a checklist artifact with per-section test cases the migrating extension must pass before publishing the MV3 build. Use when migrating an MV2 extension to Manifest V3 and the team needs section-by-section evidence the migration is complete.

74

Quality

93%

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%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is highly actionable with executable code, a clear three-step workflow with validation feedback loops, and good one-level-deep progressive disclosure. The main weakness is structural redundancy: the six-section enumeration recurs across multiple sections and could be consolidated.

Suggestions

Consolidate the repeated six-section enumeration: keep the canonical list in one place (e.g., the Step 2 table) and have the Overview, anti-patterns, and limitations reference it by name rather than re-listing every section.

Deduplicate the 35s SW-survival test reference, which is described inline in Step 2, restated as a checklist item in Step 3, and re-explained in anti-patterns; cite it once and cross-link.

Trim the Overview's failure-mode examples to the one or two that best motivate the per-cell verification approach, since the same points reappear in the anti-patterns table.

DimensionReasoningScore

Conciseness

The body is mostly lean and free of generic concept explanations, but the six-section structure is re-enumerated across the Overview, the Step 2 table, the Step 3 checklist template, the anti-patterns table, the limitations, and the references, which could be tightened.

2 / 3

Actionability

Provides fully executable, copy-paste-ready guidance: a jq inventory command, a complete Playwright service-worker survival test, and a concrete markdown checklist artifact template.

3 / 3

Workflow Clarity

Three clearly sequenced steps with an explicit validation checkpoint and feedback loop ('If the checklist has a cell with no backing test... author the missing test before merging, never check the box by hand').

3 / 3

Progressive Disclosure

SKILL.md is an overview that points to one-level-deep references/verification-cases.md (a real bundle file) for the detailed matrices, while keeping the signature SW-survival test inline; navigation is clearly signaled.

3 / 3

Total

11

/

12

Passed

Description

100%

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, complete, and distinctive: it states concrete actions, explicit 'Use when' triggers, and a clear output artifact, all in third-person voice. It is a strong model description with no significant weaknesses.

DimensionReasoningScore

Specificity

Lists multiple concrete actions ('Walks the six canonical migration sections', 'inventories the source MV2 manifest', 'names the MV3 replacement field / API', 'emits the verification test cases') rather than vague language.

3 / 3

Completeness

Explicitly answers both what ('emits a per-extension MV2 → MV3 migration test checklist' walking six sections) and when ('Use when migrating an MV2 extension to Manifest V3 and the team needs section-by-section evidence the migration is complete').

3 / 3

Trigger Term Quality

Covers the natural terms a migrating user would say ('migrating an MV2 extension to Manifest V3', 'MV2 → MV3 migration', 'Manifest V3'), which are the idiomatic trigger phrases for this domain.

3 / 3

Distinctiveness Conflict Risk

Occupies a narrow, well-defined niche (MV2→MV3 migration test checklists) with distinct triggers, making it unlikely to fire for an unrelated skill.

3 / 3

Total

12

/

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

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Reviewed

Table of Contents