CtrlK
BlogDocsLog inGet started
Tessl Logo

testland/chrome-extension-test-loader

Loads an unpacked Chrome / Chromium extension for testing through the `chrome://extensions` Developer-mode flow: the minimum loadable `manifest.json`, the Load-unpacked directory-not-file selection, toolbar pinning, and the reload matrix deciding what a code edit actually re-evaluates (`manifest.json`, the background service worker, and content scripts need an explicit card refresh, content scripts additionally need a host-page refresh, while popup / options / other extension HTML pages re-evaluate on next open). Also covers reading the red Errors card, where service-worker and content-script logs surface, and the `--load-extension` and `web-ext --target chromium` equivalents that move the same load into CI. Scope is getting a build directory loaded and reloaded, not the runtime behaviour asserted afterwards. Use when a freshly built extension directory has to go into Chrome for the first time, or when an edit appears to have no effect and you need to know which surface requires an explicit reload.

76

Quality

96%

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

92%

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

The content is highly actionable and concise, with a clear sequenced load workflow, an explicit validation checkpoint, exact error strings, and a useful reload matrix and anti-patterns table. The main gap is progressive disclosure: everything lives in one ~310-line file with no external references despite the topic having natural candidate splits.

Suggestions

Move the detailed reference quotations (exact error strings, chrome.management permission notes) and the per-URL reference list into a REFERENCES.md and link to it one level deep, leaving SKILL.md as the load/reload overview.

Consider splitting the CI integration (Playwright flags + web-ext) into a CI.md file referenced from the main body, since it is a distinct concern from the manual chrome://extensions flow.

The reload matrix and anti-patterns table are the highest-reuse content; if either grows, pull it into its own reference file rather than expanding the main body.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence: no explanation of what a manifest or service worker is, just the loadable shape, the reload matrix, and exact error strings. Source quotations are short and load-bearing rather than decorative.

3 / 3

Actionability

Fully executable guidance: a complete minimal manifest.json, a project layout tree, numbered Steps with concrete UI gestures, a worked example with expected card shape, and copy-paste CI snippets for both Playwright and web-ext.

3 / 3

Workflow Clarity

Clear sequenced workflow (Step 1-5) with an explicit validation checkpoint: the worked example expects a card with 'NO red Errors button' and re-checks after a reload. The reload matrix and anti-patterns table give explicit error-recovery feedback loops.

3 / 3

Progressive Disclosure

No bundle files exist, so structure is judged on the body alone; it is well-organized with clear sections, but it is a single monolithic file with no offloaded reference material, and the detailed per-source quotations and full reference list are inline rather than split into one-level-deep reference files.

2 / 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 dense but specific, naming concrete capabilities, natural trigger terms, an explicit 'Use when' clause, and a sharp scope boundary that separates it from runtime-testing skills. It is borderline verbose for a description but every clause earns its place.

DimensionReasoningScore

Specificity

Lists multiple concrete actions: 'the minimum loadable manifest.json, the Load-unpacked directory-not-file selection, toolbar pinning, and the reload matrix', plus reading the Errors card and CI equivalents.

3 / 3

Completeness

Explicitly answers both what (load/reload flow, manifest, pinning, reload matrix, Errors card, CI equivalents) and when ('Use when a freshly built extension directory has to go into Chrome for the first time, or when an edit appears to have no effect').

3 / 3

Trigger Term Quality

Natural user-facing terms are well covered: 'Chrome / Chromium extension', 'load-unpacked', 'chrome://extensions', 'manifest.json', 'reload', 'extension directory', 'edit appears to have no effect'.

3 / 3

Distinctiveness Conflict Risk

Clear niche scoped to loading/reloading a build directory in Chromium, with an explicit scope boundary excluding runtime behaviour assertions, making it unlikely to trigger for other skills.

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