Content
92%Weight 40%Scale 1-5Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
A tightly written, highly actionable skill: both tiers get complete working examples, the workflow includes validation and iteration feedback loops, and detail is properly pushed into a real references/sdk-api.md bundle file. The only flaw is systematic restatement of hard constraints across §3, §6, and §7, which trims conciseness without harming correctness.
Suggestions
Consolidate the manifest constraint duplicates: §6's first two bullets restate the id/version/tier regex and permission rules already given as comments in the §3 manifest example — keep one normative statement and reference it from the other.
In §7's checklist, replace full restatements of the rules (e.g. the id regex, permission matching) with short verification prompts, since the checklist's job is to trigger a check rather than re-teach the constraint.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is dense with hard constraints and executable specifics, with no padding explaining concepts Claude already knows. However, the same hard constraints are stated three to four times (id/version regex in §3 comments, §6, and the §7 checklist; permission minimality in §3/§6/§7; the no-import rule in §2, the code comment, §6, and §7), and §6 substantially restates §3 — minor duplication that could be consolidated. This is anchor 4 (efficient with trimmable redundancy) rather than 5 (every token appears exactly once by necessity). | 4 / 5 |
Actionability | Two complete, copy-paste-ready examples (a full Tier-0 manifest.json and a full Tier-1 main.js with proper effect cleanup), exact validation regexes, a concrete directory layout, and precise install steps ("侧边栏「插件」→「从本地目录安装」"). The common cases for both tiers are fully covered, matching the anchor-5 pattern. | 5 / 5 |
Workflow Clarity | Clear sequence (decide tier → structure files → write manifest → implement → deliver) with explicit validation in §5 ("验收:让用户确认看到效果;没看到就让用户看插件页该行的错误提示,别猜") and an error-recovery feedback loop (re-install hot-reloads the same id). The §7 pre-completion checklist caps a well-sequenced process, matching anchor 5. | 5 / 5 |
Progressive Disclosure | The bulk API reference is correctly offloaded to references/sdk-api.md (verified to exist in the bundle), referenced explicitly at the right moments (§3, §6, §7, §8) and exactly one level deep. §8 deliberately points to the project's plugin-development guide instead of duplicating it ("本 skill 不复制它以免出现第二份过期快照"). This is the anchor-5 pattern of a lean overview with well-signaled references. | 5 / 5 |
Total | 19 / 20 Passed |