Content
82%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 skill body is an operational, copy-paste-ready reference: a resource-selection table, concrete CLI examples, scenario strategies, and a standard JSON contract, all backed by real scripts. Its main gaps are recurring repetition of the crypto/fallback rules and the absence of any layered documentation files for progressive disclosure.
Suggestions
Consolidate the cryptocurrency prohibition into one authoritative section and cross-reference it instead of restating it across 硬性规则, 使用策略, and 输出约定.
Add a short numbered end-to-end workflow (select source → run script or browser-use → validate success=false/crypto → report with evidence URLs) to make the sequence and checkpoints explicit.
Verify the referenced requirements.txt exists at the skill root, since 依赖 instructs `pip install -r requirements.txt` but no such file is present in the bundle.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is dense and operational with no padding about what social media or search APIs are, but the crypto prohibition and fallback guidance recur across 硬性规则, 使用策略, and 输出约定, leaving minor trimmable repetition. | 4 / 5 |
Actionability | The 常用命令 section gives copy-paste-ready bash commands with concrete arguments covering each script's common cases, the 资源选择 table maps scenarios to specific real script paths and URLs, and the standard JSON output shape is specified. | 5 / 5 |
Workflow Clarity | 使用策略 sequences per-scenario workflows with explicit validation/error paths (crypto stop, dependency-fail fallback to browser-use, multi-source conflict reporting), but guidance is organized by scenario rather than as a numbered sequence with formal validate→fix→retry checkpoints. | 4 / 5 |
Progressive Disclosure | The body is a well-organized overview with clearly signaled one-level-deep script references (all referenced scripts exist under scripts/), but content is not split into separate doc files — everything lives inline in SKILL.md, so there is no deeper layered material to navigate to. | 4 / 5 |
Total | 17 / 20 Passed |