CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

manifest-v3-test-surface-reference

Pure-reference catalog of the Manifest V3 test surface for Firefox + Chromium browser extensions. Maps each manifest field that changed from MV2 (manifest_version, background.service_worker vs background.scripts, action vs browser_action / page_action, host_permissions split, web_accessible_resources object-form, content_security_policy object-form), the runtime restrictions service workers impose (no DOM, no XMLHttpRequest, no localStorage, ephemeral lifecycle, synchronous listener registration, alarms instead of setTimeout), and the Firefox-vs-Chrome key matrix (browser_specific_settings.gecko, externally_connectable / offline_enabled gaps, MV2-only user_scripts manifest key); references/ carry Mozilla's web-ext CLI (lint via addons-linter, run on firefox-desktop / firefox-android / chromium targets, deterministic build, AMO sign). Use as the manifest-surface reference when authoring extension tests across both browsers, or when driving Firefox runs / AMO signing with web-ext.

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

SKILL.md
Quality
Evals
Security

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.

A well-executed pure-reference skill: dense MV2/MV3 and Firefox/Chrome lookup tables with per-row test implications, a fix-per-anti-pattern table, an honest Limitations section for volatile/out-of-scope material, and an appropriate body-plus-two-references split with clearly signaled one-level-deep navigation. Only minor repetition of the cross-skill pointer and quote material keeps conciseness and actionability at the second-highest anchors.

DimensionReasoningScore

Conciseness

The body is dense reference material where every table row carries a test implication and no space is spent explaining concepts Claude already knows. Minor trim-able redundancy keeps it off the lean anchor: the relationship to `playwright-extension-fixtures` is stated three times (Overview paragraphs 2 and 3, plus References), and the "Two load-bearing quotes" paragraph repeats content already in the lifecycle/listener table rows. Not score 3, since the padding is limited to these instances and everything else earns its place.

4 / 5

Actionability

Concrete throughout: exact field shapes ("{ \"service_worker\": \"sw.js\", \"type\": \"module\"? }"), exact API substitutes ("use chrome.storage.local", "chrome.alarms", "chrome.offscreen.createDocument"), an anti-patterns table with a specific Fix column, and exact URLs to fetch for volatile data. It falls short of the fully copy-paste-ready anchor only because the body itself contains no runnable command (web-ext commands are deferred to references/web-ext-firefox.md) and some shapes are deliberately abbreviated summaries — minor gaps matching the 'mostly executable guidance' anchor.

4 / 5

Workflow Clarity

This is a single-task reference skill with no multi-step process to sequence, and its single action — look up a field or divergence in the summary tables, drill into references/ for exact shapes — is unambiguous. The "When to use" section enumerates the four entry scenarios (author, migrate, triage, review), and the skill is read-only, so the destructive/batch validation cap does not apply. Per the simple-skill guideline, an unambiguous single action warrants the top score.

5 / 5

Progressive Disclosure

Clean two-file split: summary lookup tables live in the body while exact shapes, the full key matrix, and the web-ext CLI each live in a dedicated file; every section explicitly signals where the detail resides ("the exact MV2/MV3 shapes... are in references/manifest-matrix.md", "detailed in references/manifest-matrix.md"). Both referenced files exist, contain the promised content, and point back to SKILL.md rather than chaining to a third level, and the References section consolidates navigation — matching the clear-overview, one-level-deep anchor exactly.

5 / 5

Total

18

/

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, information-dense description: it comprehensively enumerates the covered fields, runtime restrictions, and CLI operations in third person, and closes with an explicit dual-trigger 'Use as...' clause. The only gap is minor synonym coverage ('Chrome' never appears alongside 'Chromium'), which keeps trigger-term quality just below the top anchor.

DimensionReasoningScore

Specificity

Enumerates comprehensive concrete coverage rather than vague claims: "Maps each manifest field that changed from MV2 (manifest_version, background.service_worker vs background.scripts, action vs browser_action / page_action, host_permissions split...)", "the runtime restrictions service workers impose (no DOM, no XMLHttpRequest, no localStorage, ephemeral lifecycle, synchronous listener registration, alarms instead of setTimeout)", and "lint via addons-linter, run on firefox-desktop / firefox-android / chromium targets, deterministic build, AMO sign". Every clause names a specific field, restriction, or CLI operation; no gaps in the coverage enumeration, so it sits at the comprehensive anchor rather than the 'minor gaps' anchor below.

5 / 5

Completeness

Explicitly answers both parts: the what is "Pure-reference catalog of the Manifest V3 test surface... Maps each manifest field that changed from MV2... the Firefox-vs-Chrome key matrix; references/ carry Mozilla's web-ext CLI", and the when is a concrete trigger clause: "Use as the manifest-surface reference when authoring extension tests across both browsers, or when driving Firefox runs / AMO signing with web-ext". Both are present with concrete trigger phrases, matching the top anchor; the 'when' is explicit, not the could-be-more-specific form of the anchor below.

5 / 5

Trigger Term Quality

Good natural-term coverage: "Manifest V3", "MV3", "browser extensions", "extension tests", "Firefox", "Chromium", "web-ext", "AMO sign". A few natural terms are missing — the word "Chrome" itself never appears (only "Chromium"), and "manifest.json" / "cross-browser" synonyms are absent — which matches the 'good keyword coverage; a few natural terms missing' anchor rather than the fully comprehensive one.

4 / 5

Distinctiveness Conflict Risk

Clear niche with distinct triggers: a manifest-field-keyed, Firefox-plus-Chromium test-surface reference, explicitly scoped to the manifest surface and to web-ext run/sign workflows. Its triggers ("authoring extension tests across both browsers", "driving Firefox runs / AMO signing") are specific enough that it would not fire for generic extension authoring, Chromium-only fixture work, or general Firefox tooling — 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

referenced_paths_exist

Referenced path issues: 3 missing

Warning

Total

15

/

16

Passed

Repository

testland/qa

Path

plugins/qa-browser-extension/skills/manifest-v3-test-surface-reference/SKILL.md

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.