Content
51%Scale 1-5Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The skill provides a reasonable overview of Chrome Extension development with MV3, including useful concrete examples (manifest structure, message passing). However, it reads more like a reference cheat sheet than an actionable skill—it lacks sequenced workflows for its stated use cases (building from scratch, migration, debugging) and misses validation/verification steps. Some content explains things Claude would already know (e.g., basic security practices like avoiding eval).
Suggestions
Add a sequenced workflow for building an extension from scratch (e.g., 1. Create manifest → 2. Implement service worker → 3. Add content script → 4. Test with chrome://extensions → 5. Verify message passing), including validation checkpoints like loading the unpacked extension and checking for errors.
Add a brief migration workflow for MV2→MV3 with concrete steps and common pitfalls, since this is listed as a primary use case.
Remove or condense generic advice Claude already knows (e.g., don't use eval, validate external input) and replace with Chrome-extension-specific gotchas that are less obvious.
Consider referencing separate files for advanced topics like declarativeNetRequest rules, side panel API, or detailed debugging procedures to improve progressive disclosure.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The 'Use this skill when' and 'Do not use this skill when' sections add moderate overhead. The instructions section is reasonably tight but includes some obvious guidance (e.g., 'Use Manifest V3' for a skill explicitly about MV3). The best practices section mixes well-known security advice (don't use eval) with Chrome-specific tips. | 3 / 5 |
Actionability | Provides concrete, executable examples including a complete manifest.json and a working message-passing snippet. However, it lacks a content script counterpart example for the message passing, and the instructions are more like guidelines than step-by-step executable procedures. The troubleshooting section gives a concrete solution (chrome.alarms). | 4 / 5 |
Workflow Clarity | There is no clear multi-step workflow for building or debugging an extension. The instructions are a flat list of guidelines rather than a sequenced process. For a skill covering extension development from scratch, migration, and debugging, the lack of any sequenced workflow with validation checkpoints is a notable gap. | 2 / 5 |
Progressive Disclosure | The content is organized into logical sections (instructions, examples, best practices, troubleshooting) which provides decent structure. However, there are no references to external files for deeper topics like migration guides, advanced APIs (declarativeNetRequest, side panel), or detailed debugging procedures, and all content is inlined in a single file without clear pointers for expansion. | 3 / 5 |
Total | 12 / 20 Passed |