Content
71%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 actionable, well-structured single-purpose skill with concrete URLs, a staged fetching strategy, and explicit filtering criteria. Its weaknesses are duplicated output requirements, a hardcoded date in the template, and an ambiguous tool reference in the fetching strategy.
Suggestions
Remove the duplicated Notes section (or the Output Requirements block) so each rule about complete headlines and no commentary/source attribution is stated once.
Replace the hardcoded "3月25日" with a placeholder like "{今天的日期}" plus a note to insert the current date at output time, so the template does not go stale.
Specify the exact tool to use for fetching (e.g., name the web-fetch/WebFetch tool unambiguously) and add a quick check that a fetch returned items before filtering and moving to the next platform.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is mostly tight, but requirements are duplicated ("Each news item must be complete with clear beginning and end" and "Facts only, exclude subjective commentary" appear both under Output Requirements and in Notes), and the hardcoded date "3月25日" is time-sensitive information that will go stale. | 3 / 5 |
Actionability | Concrete platform paths (/n/KqndgxeLl9 etc.) and copy-paste web_fetch() URLs make the fetch step executable, but the tool invocation is ambiguous ("web-search skill or web_fetch") and the output template is a fill-in skeleton rather than fully covering cases. | 4 / 5 |
Workflow Clarity | The sequence is clear with an inline decision checkpoint ("Fetch one platform at a time, filter immediately, then decide whether to fetch the next") and explicit include/exclude criteria, but there is no step verifying that a fetch succeeded or yielded usable items before proceeding. | 4 / 5 |
Progressive Disclosure | No bundle files exist and none are needed; every section is short and appropriately inline, and the Data Collection / Fetching Strategy / Filtering Criteria / Output Format headings make navigation trivial. | 5 / 5 |
Total | 16 / 20 Passed |