CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

moai-platform-chrome-extension

Chrome Extension Manifest V3 development specialist covering service workers, content scripts, message passing, chrome.* APIs, side panel, declarativeNetRequest, and Chrome Web Store publishing. Use when building browser extensions.

Quality

65%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./.moai/archive/skills/v2.16/moai-platform-chrome-extension/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

42%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 well-organized topically and contains a useful density of Chrome-specific facts, but it is padded with concepts Claude already knows and admin boilerplate, provides no executable code or commands, and its progressive-disclosure references all point to module files that are absent from the bundle. It functions as a knowledgeable overview rather than an actionable development guide.

Suggestions

Cut conceptual explanations of known MV3 fundamentals and the administrative boilerplate (Status, Generated-with, Telemetry Window) to reclaim tokens; keep only the non-obvious specifics like the 64 MiB message cap, storage quotas, and field constraints.

Add executable examples for the common cases: a minimal manifest.json snippet, a top-level service-worker listener pattern, and a sendMessage/onMessage pair — currently the guidance is entirely descriptive prose.

Ship the referenced modules/*.md files (or remove the references), and deduplicate the module listing that currently appears in both the Module Index and the Resources section.

DimensionReasoningScore

Conciseness

Noticeably verbose: extensive passages explain platform concepts Claude already knows ("Service workers in Manifest V3 replace persistent background pages with an event-driven model", "Content scripts... run in isolated worlds, meaning they share DOM access with the host page"), the Quick Reference restates the frontmatter description, and non-instructional boilerplate pads the file ("Status: Production Ready", "Generated with: MoAI-ADK Skill Factory", the entire Telemetry Window admin block). Not a 1 because genuinely non-obvious specifics are interspersed (64 MiB message cap, storage area quotas, 75/132-character field limits).

2 / 5

Actionability

Provides concrete field-level and API-level guidance (manifest field names, types, and constraints; debug URLs like chrome://extensions and chrome://inspect) but contains zero code examples — no manifest.json snippet, no service-worker listener example, no commands to run. It describes rather than hands over executable material, which is incomplete guidance rather than purely high-level hints, landing between the minimal-guidance anchor and the mostly-executable anchor.

3 / 5

Workflow Clarity

Topics follow a rough build order (manifest → service worker → content scripts → messaging → APIs → UI → permissions → security) and a Verification checklist plus Troubleshooting section provide some validation, but no explicit sequenced development workflow (scaffold → load unpacked → debug → test → publish) with checkpoints is ever laid out. The sequence is implicit and checkpoints are scattered, matching the anchor for steps present with validation gaps.

3 / 5

Progressive Disclosure

A Module Index with clearly signaled one-level-deep modules/*.md references shows good structure in intent, but no modules directory exists in the bundle — every reference points to a missing file — and the module list is duplicated between the Module Index and the Resources section. Structure exists but navigation is broken and organization is redundant, so it cannot reach the good-structure anchor.

3 / 5

Total

11

/

20

Passed

Description

75%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 solid description that clearly states a specific niche and includes an explicit "Use when" clause with good natural trigger terms. Its main weaknesses are the topic-list framing rather than concrete actions and a somewhat generic when-clause that could name concrete triggers like manifest.json or chrome.* API usage.

DimensionReasoningScore

Specificity

Names the domain and lists many concrete coverage areas ("service workers, content scripts, message passing, chrome.* APIs, side panel, declarativeNetRequest, and Chrome Web Store publishing") with only minor gaps (e.g., popup/options page). Phrased as topics the specialist "covering" rather than concrete actions, so it does not reach the comprehensive action-listing of a 5.

4 / 5

Completeness

Explicitly answers both: the "what" is a Manifest V3 development specialist covering the listed areas, and the "when" is "Use when building browser extensions." The when-clause lacks concrete trigger phrases and is generic relative to the Chrome-specific what, matching the anchor where both are present but the when could be more explicit.

4 / 5

Trigger Term Quality

Includes natural terms users would say ("Chrome Extension", "Manifest V3", "browser extensions", "Chrome Web Store") with good coverage. A few natural variations and file artifacts are missing ("extension popup", "manifest.json", ".crx"), so it falls just short of the comprehensive synonym coverage of a 5 but is well above the sparse keyword coverage of a 3.

4 / 5

Distinctiveness Conflict Risk

"Chrome Extension Manifest V3 development" carves out a clear niche with distinct technical triggers. However, the when-clause "Use when building browser extensions" is browser-agnostic and could fire for closely related skills (e.g., Firefox/Safari extension development), creating minor overlap risk that keeps it below a 5.

4 / 5

Total

16

/

20

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

allowed_tools_field

'allowed-tools' contains unusual tool name(s)

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

14

/

16

Passed

Repository

modu-ai/moai-adk

Path

.moai/archive/skills/v2.16/moai-platform-chrome-extension/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.