Content
67%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.
An information-dense, well-referenced body that gives precise, executable repo-specific guidance with real validation checkpoints and a genuine one-level reference structure. Its weaknesses are token efficiency — inline version/date minutiae and run-on paragraphs that belong in references — and the lack of an explicitly ordered top-level workflow.
Suggestions
Move the per-component minor-version requirements (Badge 5, form controls 6, table composition 7, resource cards 8) and the date-stamped verification records (2026-10-10 identity checks, 历史1.2整合记录) into references/plugin-contract.md or a dedicated changelog section, keeping only the current runtime version and one example call in SKILL.md.
Break the run-on paragraph in 固定接入规则 · v1 into a short list or table (entry, iframe rule, build mode, version check) so each rule is scannable instead of embedded in a wall of text.
Replace the repeated unspecified "共享包 README" pointer with the actual file path, and add one minimal copy-paste sample of the standard host-React and iframe import patterns.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Almost every token is repo-specific fact rather than explanation of known concepts, which is efficient in kind, but the body is packed with time-sensitive details — runtime version "1.8.0", per-component minor requirements (5, 6, 7, 8), and date-stamped verification notes ("2026-10-10 核对", "历史1.2整合记录") — inline rather than in a reference or dedicated changelog section. The run-on paragraph in 固定接入规则 mixing entry rules, version negotiation, and status bookkeeping clearly could be tightened, matching anchor 3 rather than 4. | 3 / 5 |
Actionability | Guidance is highly concrete and executable: exact import paths (`@/components/ui/*`, `@ipollowork/ui/controls`, `requireRuntime(1)`), exact API call signatures (`requireRuntime(1, ['Badge', 'Icon'], 5)`), exact token values (#1FBAC0, 32px/28px, 14/16/20px), and per-use-case component decision rules (Select vs Autocomplete vs RadioGroup). It stays below anchor 5 because a few pointers lack explicit paths ("共享包 README" appears several times with no file path) and there is no minimal copy-paste sample of the standard host-React import, though per the scoring notes the absence of code blocks per se is not penalized for an instruction-only skill. | 4 / 5 |
Workflow Clarity | A clear implicit sequence runs through section order: determine environment → read the contract's entry/build/version sections → select components by evidence tier (推荐/待验证/候选/历史) → apply colors/typography/interaction constraints → implement → verify, with explicit validation checkpoints ("实施前按共享包README的固定验收矩阵列出本次适用状态", "旧版本或缺组件时停止初始化并提示更新客户端", "校验真实选择值、草稿保留和重试写盘"). Not a 5 because the global ordering must be inferred from section order — there is no single ordered workflow listing — and some checkpoints are scattered across sections. | 4 / 5 |
Progressive Disclosure | The body is an overview with one-level-deep, well-signaled references that all exist in the bundle: references/plugin-contract.md (with section anchors like #主题与-token), references/component-catalog.md, and references/component-mapping.json hold the bulk detail (202/291/901 lines). Minor gaps: dense inline blocks such as the full 资源卡复用 spec and per-component minor-version requirements could live in the contract or catalog, and several repo files (docs/, evals/, examples/) are cited without verifying their placement for a reader landing in the skill directory. | 4 / 5 |
Total | 15 / 20 Passed |