Content
72%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.
This is a highly actionable orchestration skill: every source has an exact command, the categorization and opportunity frameworks are concrete, and the output format is fully templated. Its main weaknesses are the absence of any error handling or validation across the batch of parallel source scans, and a monolithic 360-line body whose report template and strategy-pattern catalog should live in reference files.
Suggestions
Add validation/feedback steps for the batch data collection — e.g., check each source's exit status and output, retry or log-and-skip failed sources, and report which sources failed in the Scan Statistics section.
Move the ~90-line report template and the strategy-patterns catalog into reference files (e.g. references/report-template.md and references/strategy-patterns.md) with clear one-level pointers from the body.
Trim the redundant opening paragraph (it restates the frontmatter description) and compress the asides in Phase 3/4 to tighten token efficiency.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Nearly all of the ~360 lines are concrete commands, config fields, and structured tables with almost no explanation of concepts Claude already knows. Minor trims are possible (the intro paragraph repeats the frontmatter description, asides like "The goal is signal, not volume"), so it fits the efficient-with-minor-trims anchor rather than the lean every-token-earns-its-place anchor given the sheer inline volume. | 4 / 5 |
Actionability | Every data source has a copy-paste-ready bash command with flags and placeholder substitution (e.g. the blog, Reddit, Twitter, HN, review-site scripts), web-search query patterns are given verbatim, and the output template plus config field list make execution unambiguous. This matches the fully-executable anchor with specific examples covering the common cases. | 5 / 5 |
Workflow Clarity | The five-phase sequence is clearly ordered and Phase 3 says to consolidate "after all data collection completes", but there are no validation checkpoints or feedback loops for a batch operation spanning up to nine parallel sources — nothing on what to do when a script fails, returns empty, or errors mid-scan. The rubric's scoring note caps workflow clarity at 3 for batch operations without feedback loops, which precludes the level-4 anchor. | 3 / 5 |
Progressive Disclosure | Section structure is good and references to other skills are clearly signaled and one level deep ("Read skills/blog-feed-monitor/SKILL.md for full CLI reference"), but the skill ships no bundle files of its own while inlining roughly 90 lines of report template and 45 lines of strategy patterns that belong in reference files. This matches the anchor where content that should be separate is inline, rather than the good-placement anchor at 4. | 3 / 5 |
Total | 15 / 20 Passed |