Content
93%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 excellent, tightly written skill body: executable quick-start commands, a complete CLI reference, cost transparency, and a clear output contract, with the single script bundle correctly referenced and no padding. The only notable gap is the absence of failure/verification guidance for the external paid API call (timeout, failed run, empty results), which keeps workflow clarity just below perfect.
Suggestions
Add a short error-handling note to the Notes section: what the script does on Apify timeout or failed run, and what to check when a query returns zero results (e.g., broaden the topic, remove country filter).
State the units and platform caveat for --min-followers next to the flag in the CLI table (or reference the Notes line) so users filtering on expected LinkedIn-specific counts are not misled.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is lean with zero concept explanation: prerequisites in one line ("Requires APIFY_API_TOKEN env var... pip install requests"), a compact CLI table, a one-line cost note, a field list, and factual Notes. Every section adds information Claude would not already know, matching the "every token earns its place" anchor. It is not score 4 because there is no over-explanation or padding to trim. | 5 / 5 |
Actionability | Four copy-paste-ready commands cover the common cases (topic only, topic+country, has-email, follower range), plus install, env var, output format, cost estimate, and a documented output-field contract. This matches the fully-executable, common-cases-covered anchor; there are no gaps that would drop it to score 4. | 5 / 5 |
Workflow Clarity | As a simple single-action skill the invocation is unambiguous (prereqs → run command), and the printed pre-run cost estimate acts as a checkpoint. However the operation calls a paid external API with a --timeout flag and no guidance on handling failures, timeouts, or empty result sets — a minor validation gap consistent with the score-4 anchor ("most checkpoints present; minor validation gaps") rather than the explicit error-recovery loops of score 5. It is not score 3: the single action is clear and the operation is read-only, not destructive or mutation-based. | 4 / 5 |
Progressive Disclosure | The body is a compact (~75 line) overview with well-organized sections, one script bundle (scripts/discover_influencers.py) that exists on disk and is referenced with a correct path, and no buried or nested references. Nothing that belongs in a separate file is inlined (the CLI table and field list are short enough to belong here), matching the small-skill ideal in the scoring notes. | 5 / 5 |
Total | 19 / 20 Passed |