Content
86%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 lean, well-structured instruction-only skill: dense project-specific contract with exact paths, field names, theme variables, and a strong six-step acceptance checklist including seek and real-export verification. The main gaps are a missing minimal manifest example, unnamed validation commands, and no explicit fix-and-revalidate loop.
Suggestions
Add a minimal complete registry-item.json example (variables, visualComponent.data, ai.slots, surfaces) so the core artifact is copy-paste ready instead of derived from schema files.
Name the exact validation/test commands or script paths in the acceptance section rather than "通过当前仓库对应校验和受影响的测试".
Add an explicit error-recovery loop to section 8 (e.g., if validation or Studio install fails, fix the manifest/HTML and re-run until checks pass).
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is dense, imperative project contract: exact repo paths ("vendor/hyperframes/registry/blocks/world-map/"), exact field names ("visualComponent.data", "themeMode: inherit", "update: live"), exact CSS variables ("--ipw-color-bg", "--ipw-font-display"), and no padding or explanation of concepts Claude already knows. Every token is project-specific knowledge Claude cannot infer; matches the 'lean and efficient' anchor. | 5 / 5 |
Actionability | Highly concrete throughout: a minimal deliverable layout ("registry-item.json # 元信息..." / "<slug>.html"), a complete executable JSON data example ("{ "version": 1, "kind": "region-value", ... }"), exact variable types ("string / number / color / boolean / enum"), and the timeline registration point ("window.__timelines[compositionId]"). Not score 5 because two common cases lack copy-paste-ready examples: a complete minimal registry-item.json manifest, and the concrete validation/test commands referenced only as "通过当前仓库对应校验和受影响的测试". | 4 / 5 |
Workflow Clarity | Clear sequencing: section 1 explicitly gates work ("开始前：以当前代码契约为准" — read AGENTS.md and find similar components first), sections 2-7 define the build contract, and section 8 is a six-item acceptance checklist covering validation, Studio install, boundary/empty/error data, both themes, multi-instance isolation, seek behaviors, and real export ("不能仅凭截图声称通过"). Not score 5 because there is no explicit error-recovery feedback loop (what to do when validation fails and re-verify); validation steps themselves are comprehensive, so above the midpoint between anchors 3 and 5. | 4 / 5 |
Progressive Disclosure | The skill is a single self-contained file (~95 lines) organized into eight clearly numbered sections with no inlined material that belongs in separate bundle files, and it points one level deep to authoritative detail in the target repo ("packages/core/schemas/registry-item.json", "packages/types/src/hyperframes.ts", "blockInstaller.ts") as the source of truth. Easy to navigate, appropriately split between overview here and detail in the referenced files; matches the top anchor. | 5 / 5 |
Total | 18 / 20 Passed |