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.
The body is an exceptionally lean and actionable operational runbook: exact commands, timeout arithmetic, bounded retry loops, result-state branching, and diagnostic recovery paths, with strong validation gates around a risky outward-facing operation. Its only structural weakness is the lack of section headers to aid navigation through the dense single-file layout.
Suggestions
Add 3–4 section headers (e.g., ## 预览与提交, ## 视频发布, ## 结果与重试, ## 失败诊断) so the dense paragraphs are navigable without reading linearly.
If the skill grows, move the video timeout/diagnostic detail table into a references/ file and link it, keeping SKILL.md as an overview.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Every sentence carries skill-specific operational constraints (e.g., "预览的 video_transport 显示上传与进程总超时", "进程总超时为上传超时加 420 秒，默认 720 秒") that Claude could not know; there is no padding, no explanation of known concepts, and no verbosity to trim. This matches the 'lean and efficient; every token earns its place' anchor. | 5 / 5 |
Actionability | Fully executable guidance throughout: copy-paste-ready bash commands for both preview and confirmed publish, an exact env-var invocation ("PLATFORM_API_WEIBO_VIDEO_UPLOAD_TIMEOUT_SECONDS=600 ... --video /绝对路径/video.mp4"), concrete parameter values ("最多 7 次本人作品首页（每次最多 20 条、间隔 5 秒）"), and named diagnostic fields ("diagnostic.detail.request", "video_upload/video_transcode/video_submit"). Specific examples cover the common publish and video cases, matching the top anchor. | 5 / 5 |
Workflow Clarity | The risky multi-step publish flow is explicitly sequenced with validation checkpoints and feedback loops: check before execution, preview-by-default with an explicit --confirm gate, video upload→transcode→submit ordering with timeout arithmetic, result-state branching ("published:true, recorded:false" → re-run only recording; "accepted:true, resolution_pending:true" → query only, never re-publish), a bounded retry loop with precise matching rules, and failure diagnostics with recovery steps. This matches the 'clear sequence with explicit validation steps; feedback loops for error recovery' anchor. | 5 / 5 |
Progressive Disclosure | As a single-file skill with no bundle files, the body appropriately avoids phantom references, but organization is minimal: one H1 heading followed by ~10 dense unheaded paragraphs. Navigation relies entirely on reading order, matching 'some structure but could be better organized' rather than the well-organized-sections needed for a higher score on a headerless layout. | 3 / 5 |
Total | 18 / 20 Passed |