Conciseness

At ~514 lines for a single CLI wrapper, the body has several padded sections: "When to Use This Skill" repeats the frontmatter description, each capability carries "Useful for"/"Great for" bullet filler, "Common Usage Patterns" and "Advanced Use Cases" ("Combining Multiple Searches" duplicates "Research on a Topic") re-demonstrate flag combinations already documented, and the closing "Resources" section re-summarizes the script's features yet again. Not a 3 because the redundancy goes beyond minor tightening — well over half of the second half of the file could be deleted with no loss; not a 1 because it avoids explaining concepts Claude already knows and most lines are concrete commands.

Actionability

Every capability is shown as a copy-paste-ready command (e.g., `python scripts/search.py "climate change" --type news --time-range w --max-results 15`), all 13 documented flags exist in the actual script's argparse, sample outputs for all three formats are shown, installation is given, and troubleshooting covers concrete failure modes. Fully executable with common cases covered — matches the top anchor.

Workflow Clarity

The "Implementation Approach" section lays out a clear 5-step sequence (identify intent → configure parameters → select format → execute → process results), and Troubleshooting supplies error-recovery feedback ("No results found: Try broader search terms or remove time filters", retry after timeouts, space out rate-limited requests). Not a 5 because these recovery loops live in a separate section rather than being integrated as checkpoints in the workflow itself; well above a 3 since sequence and recovery guidance are both explicit.

Progressive Disclosure

The body is well-sectioned with headers and a Quick Reference, and its single bundle file (scripts/search.py) is real, correctly referenced, and consistently used. However, everything is inlined in one ~514-line SKILL.md: the per-filter option catalogs, the usage-pattern cookbook, and the script-feature summary are content that could live in a references/ file or be delegated to the script's own --help, which the doc itself points to. Structure exists, but content that should be separate is inline — matches the middle anchor.

Specificity

Lists several concrete actions — "search the web for information, find current content, look up news articles, search for images, or find videos" and "return results in clean, formatted output (text, markdown, or JSON)" — with minor gaps (filtering, region, and output-to-file capabilities are not mentioned). Not a 5 because coverage is not comprehensive, and not a 3 because far more than 1-2 actions are named.

Completeness

Explicitly answers both questions: what it does ("uses DuckDuckGo's search API to return results in clean, formatted output (text, markdown, or JSON)") and when to use it ("This skill should be used when users need to..." plus "Use for research, fact-checking, finding recent information, or gathering web resources"). Clear 'what' and explicit 'when' with concrete trigger phrases matches the top anchor.

Trigger Term Quality

Good natural keyword coverage: "search the web", "look up news articles", "search for images", "find videos", "fact-checking", "research", "gathering web resources" — phrases users would actually say. Not a 5 because common variations like "search online", "look this up", or "google it" are absent; not a 3 because multiple synonyms and content types are covered well beyond a single generic keyword.

Distinctiveness Conflict Risk

The DuckDuckGo web/news/image/video search niche is mostly distinct with clear triggers. Not a 5 because broad phrases like "research", "fact-checking", and "gathering web resources" create minor overlap risk with dedicated research or verification skills; well above a 3 since the core triggers (web search, news, images, videos) are unambiguous.