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 unusually dense, prescriptive instruction-only skill: it specifies fonts, sizes, timings, CSS mechanics, and a precise JSON contract, with two explicit pre-submit validation checks. Its main costs are systematic rule duplication between the usage and contract sections and the lack of a single worked HTML example showing what a compliant output looks like.
Suggestions
State each rendering rule once: keep the normative version in 文档与渲染契约 and reduce the 使用方式 and 实片排版 restatements of root opacity:1, render-from-0s, no-infinite, and screenCopy-once-only to brief pointers, cutting a substantial token block.
Add one compact worked example of a compliant output — a minimal HTML/CSS snippet for a gradient title group plus the filled-in JSON object — so the contract can be verified by pattern-match rather than reconstructed from constraints.
Promote the detailed rendering contract (units, exit attributes, html_js/GSAP rules) into a single one-level-deep reference file (e.g. references/rendering-contract.md) and keep an overview plus the pre-submit checklist in SKILL.md.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | There is no fluff and no re-teaching of known concepts (CSS keyframes, GSAP, background-clip are assumed), but key rules are systematically restated: root-container "opacity:1" appears in 使用方式, 实片排版, and 渲染契约; render-from-0s and the no-"infinite" rule appear twice (lines 23 and 76); screenCopy completeness/once-only appears twice (lines 21 and 75). This is more than minor trimmable over-explanation, so it fits 'mostly efficient but could be tightened' rather than 4. | 3 / 5 |
Actionability | Guidance is highly concrete: named fonts (PingFang SC / Noto Sans CJK SC / Microsoft YaHei), numeric ranges (中文 3.5%–6.5%、英文 1.6%–2.4% of canvas width; 0.3–0.8s entrance; ≥约3s label reading), exact CSS mechanics (background-clip:text, animation-fill-mode:both/forwards, data-motion-exit values), a copy-paste-ready JSON output contract, and the window.__hf={duration,seek(t,o)} API. Not 5: no worked HTML/CSS example of an actual caption design, which is the skill's primary artifact. | 4 / 5 |
Workflow Clarity | The flow is unambiguous ("直接设计当前字幕,并按文末契约返回 JSON,不输出计划或调用其他工具") and includes two explicit checkpoints: "核对一次 HTML 的全部可见文字…应与本次 screenCopy 完全相同" and "提交前检查入场、流光高光经过、稳定期与末态". Not 5: the sequence is embedded in prose rather than ordered steps, and there is no error-recovery loop for a failed check. | 4 / 5 |
Progressive Disclosure | Five well-organized sections plus a semantic effects table, and every path mentioned exists at runtime (no skill bundle files are referenced; vendor/gsap.min.js is a runtime library). Not 5: at roughly 60 dense lines — above the simple-skill threshold — the detailed rendering contract and material/motion specifications could be split into a one-level-deep reference file. | 4 / 5 |
Total | 15 / 20 Passed |