CtrlK
BlogDocsLog inGet started
Tessl Logo

chrome-extension-developer

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

58

Quality

67%

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

Fix and improve this skill with Tessl

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

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

SKILL.md
Quality
Evals
Security

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 content is concise and actionable with executable examples and clean section organization. Its main weakness is workflow clarity: guidance is advisory (principles) rather than a sequenced process with validation checkpoints.

Suggestions

For multi-step workflows (e.g., migration or debugging message passing), add an explicit numbered sequence with validation/checkpoint steps rather than only principle-level instructions.

Expand code examples to cover one or two more common cases (e.g., content-script-to-background round trip with error handling, or storage read/write) to push actionability toward fully copy-paste ready.

Tighten the intro line and a couple of Do/Don't entries that restate widely known practices to approach maximal token efficiency.

DimensionReasoningScore

Conciseness

The body is lean with short numbered instructions and compact code blocks, mostly avoiding explanation of concepts Claude already knows; only minor trims are possible.

4 / 5

Actionability

Provides concrete, executable examples (manifest.json and a message-passing listener) plus specific API calls, with only minor gaps in coverage of common cases.

4 / 5

Workflow Clarity

Instructions are presented as a numbered list of principles rather than a sequenced process, and there are no explicit validation checkpoints; the troubleshooting entry is a feedback hint but not a structured loop.

3 / 5

Progressive Disclosure

Single, well-organized SKILL.md with clearly labeled sections and no nested references; content is appropriately placed inline, with only minor room to split reference material.

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 distinct, naming several concrete MV3 capabilities, but it lacks an explicit "Use when" trigger clause, which limits its completeness score. Trigger-term coverage is good but could add synonyms and file extensions.

Suggestions

Add an explicit 'Use when...' clause stating when to invoke this skill (e.g., building, migrating, or debugging Chrome extensions).

Include natural trigger synonyms and file references like 'Chrome Extension', '.crx', 'manifest.json', and 'browser extension' to broaden keyword coverage.

Mention a couple more capabilities in the description (e.g., permissions, storage, popup/options pages) to push specificity toward comprehensive.

DimensionReasoningScore

Specificity

Names the Chrome Extensions MV3 domain plus several concrete capabilities ("background scripts, service workers, content scripts, and cross-context communication"), but coverage is not fully comprehensive (storage, permissions, UI contexts absent).

4 / 5

Completeness

Has a clear "what" but no "Use when..." or equivalent explicit trigger clause, which per the rubric caps completeness at 3.

3 / 5

Trigger Term Quality

"Chrome Extensions" and "Manifest V3" are natural terms a user would say, but common synonyms and file/extension references are missing.

4 / 5

Distinctiveness Conflict Risk

The Chrome Extensions / Manifest V3 niche is clearly distinct from general web skills with low conflict risk, though it is slightly broad without narrower trigger phrases.

4 / 5

Total

15

/

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.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

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