Conciseness

The body is mostly efficient (commands, tables, no explaining concepts Claude already knows), but the ~35-row 'Quick map' table repeats '(see `--help`)' as the payload for roughly 25 rows, and its Bloomberg/Eastmoney/Xueqiu/Reddit command lists duplicate what references/finance-sources.md already details — matching the anchor 'Mostly efficient but includes some unnecessary explanation or could be tightened'. Not score 4: the stub rows and the table/reference duplication are more than minor trims; not score 2 because there is no concept padding and every section carries operational content.

Actionability

Fully executable throughout: install command ("npm install -g @jackwener/opencli"), environment probe, discovery commands ("opencli list -f json", "opencli <site> <command> --help"), and copy-paste-ready examples covering common cases ("opencli yahoo-finance quote AAPL -f json", "opencli reddit subreddit wallstreetbets --limit 20 -f json", "opencli web read 'https://example.com/article' -f json"). Matches the anchor for fully executable, copy-paste ready commands covering common cases; nothing remains at the hint level.

Workflow Clarity

A clear 7-step sequence (decide → ensure ready → discover → check strategy → execute → handle failures → present) with explicit checkpoints and a feedback loop: pre-flight 'opencli doctor' probe, strategy preconditions checked before running, "Start with a small --limit (10–20) to validate the shape before pulling more", and a failure path ("OPENCLI_DIAGNOSTIC=1") with numbered recovery responses. Not score 4: validation and error-recovery checkpoints are explicit, not merely present with gaps. The read-only nature means the destructive/batch cap does not apply.

Progressive Disclosure

Good structure: the body is a step-by-step overview, and both bundle files are real, one level deep, and clearly signaled in a 'Reference Files' section with per-file descriptions and a when-to-read condition ("when you need concrete examples for a specific site"). Not score 5 because the split is not clean — the strategy table in Step 4 and the source shortlist table in Step 3 duplicate content in references/discovery.md and references/finance-sources.md, so some content that belongs in the reference files is inlined; not score 3 because navigation is easy and the references are well signaled rather than buried.

Specificity

The description names the domain exhaustively ("finance sites (Yahoo Finance, Bloomberg, Reuters, Barchart, Eastmoney, Xueqiu, Sinafinance), communities (Reddit, HackerNews...)") but the concrete actions are limited to "read or fetch" — 1-2 actions, matching the anchor 'Names domain and 1-2 concrete actions, but not comprehensive'. The example triggers ("Eastmoney hot stocks", "Bloomberg markets headlines") name data targets, not additional actions. Not score 4 because 'Lists several specific actions' is not met; not score 2 because the what is far more concrete than 'Processes PDF files'.

Completeness

Both what and when are explicit: what is "Generic read-only fallback for sources opencli supports but no dedicated skill covers", and when is "Use it when the user asks to read or fetch from such a site — for example... or says 'use opencli to read'", with concrete trigger phrases and examples. Not score 4 because the 'when' is fully explicit with multiple concrete trigger examples, exactly matching the anchor-5 exemplar.

Trigger Term Quality

Comprehensive natural terms users would actually say: site names across categories ("Reddit", "HackerNews", "Substack", "arXiv", "YouTube"), example phrasings ("r/wallstreetbets", "the HackerNews front page", "the Xueqiu feed"), and the direct phrase "use opencli to read" — matching the anchor for comprehensive coverage including synonyms. Not below 5 because no commonly-said variation is missing; synonyms like Chinese platform names (Xueqiu, Xiaohongshu) are even included.

Distinctiveness Conflict Risk

It has a clear niche — opencli-supported sources not covered by dedicated skills — and explicitly defuses conflict with "Prefer twitter-reader, linkedin-reader, discord-reader, telegram-reader, or yc-reader when the source matches", plus "Read-only: never runs write commands" to separate it from write-capable tools. Not score 4: the overlap risk with the named dedicated readers is explicitly resolved rather than merely minor; the residual breadth of "and more" is bounded by "sources opencli supports".