Name: chrome-extension-developer
Rating: 58.4 (1 reviews)
Author: administrakt0r

chrome-extension-developer

Expert in building Chrome Extensions using Manifest V3. Covers background scripts, service workers, content scripts, and cross-context communication.

Quality

67%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/AI-Agents-Safe-Coding-Skills/skills/chrome-extension-developer/SKILL.md

The canonical home for this skill is chrome-extension-developer in administrakt0r/AI-Agents-Safe-Coding-Skills

Quality

Content

68%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 concise and actionable with executable examples and well-organized sections, but it presents principles rather than a sequenced, validated workflow. Adding a step-by-step process (e.g. for MV2→MV3 migration) with verification checkpoints would improve workflow clarity.

Suggestions

Add a sequenced multi-step workflow with validation checkpoints for at least one task (e.g. MV2→MV3 migration: edit manifest, convert background page to service worker, test, verify in chrome://extensions).

Include a small executable example for chrome.storage usage and a content-script message-send example to close the actionability gaps.

Trim the opening role-preamble line, which restates the description, to improve token efficiency.

Dimension	Reasoning	Score
Conciseness	The body is efficient and largely assumes Claude's competence, with concrete instructions and tight code, but the opening 'You are a senior Chrome Extension Developer…' preamble and a few obvious do/don'ts (innerHTML/eval) could be trimmed, matching anchor 4.	4 / 5
Actionability	It provides copy-paste-ready, executable code (a complete manifest.json and a chrome.runtime.onMessage listener) and names specific APIs (chrome.storage.local/sync, declarativeNetRequest, chrome.alarms), but lacks code for storage and content-script cases, leaving minor gaps at anchor 4.	4 / 5
Workflow Clarity	The content is organized as principles and examples rather than a sequenced workflow; there is a single troubleshooting problem/solution feedback loop but no explicit step sequence with validation checkpoints, matching anchor 3.	3 / 5
Progressive Disclosure	The skill is a single self-contained file with clear, well-organized section headers and no nested references, giving good structure and easy navigation; at ~75 lines it exceeds the under-50-line simple-skill exception, so it sits at anchor 4 rather than 5.	4 / 5
	Total	15 / 20 Passed

Description

66%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.

The description is specific and well-targeted to a clear niche, but it lacks an explicit 'Use when…' trigger clause, which caps its completeness. Adding natural trigger phrases like 'Use when building or migrating Chrome extensions' would raise the score.

Suggestions

Add an explicit 'Use when…' clause listing concrete trigger situations (e.g. building a Chrome extension, migrating MV2 to MV3, debugging message passing).

Replace or supplement 'cross-context communication' with the natural term 'message passing' to improve trigger-term quality.

Include file-format or surface triggers users might say (e.g. 'manifest.json', 'service worker', 'content script') to boost distinctiveness.

Dimension	Reasoning	Score
Specificity	Names the domain and several concrete sub-areas ('background scripts, service workers, content scripts, and cross-context communication'), which is several specific capabilities with minor gaps, but the 'Covers…' framing lists topics rather than discrete actions so it does not reach anchor 5.	4 / 5
Completeness	It clearly answers 'what' (building Chrome Extensions with MV3 and the listed components) but provides no explicit 'Use when…' trigger guidance; per the judging guidelines a missing 'Use when' clause caps completeness at 3, so it does not reach anchor 4.	3 / 5
Trigger Term Quality	Good natural developer keywords ('Chrome Extensions', 'Manifest V3', 'service workers', 'content scripts'), but it uses the jargon 'cross-context communication' instead of the more common 'message passing' and omits synonyms, matching anchor 4's 'a few natural terms missing'.	4 / 5
Distinctiveness Conflict Risk	The 'Chrome Extensions using Manifest V3' niche is mostly distinct with minimal conflict risk, but adjacency to general web development and related browser-extension skills (e.g. the body's own safari reference) keeps it at anchor 4 rather than 5.	4 / 5
	Total	15 / 20 Passed

Validation

93%

Warnings & errors only

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

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: administrakt0r/AI-Agents-Safe-Coding-Skills
Path: plugins/AI-Agents-Safe-Coding-Skills/skills/chrome-extension-developer/SKILL.md
Commit: 57c135b

Reviewed: 2 days ago

Table of Contents

Discovery Implementation Validation

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.