Content
88%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.
A well-structured, highly actionable skill body with executable commands for every case and a genuinely defensive workflow (silent-block detection, single retry, MCP fallback, no auto-triage). Its two weaknesses are redundancy between the Mindset and Anti-Patterns sections and a dangling requirements.txt reference in the References section.
Suggestions
Consolidate the Mindset section's points 2 and 3 with the Anti-Patterns entries they duplicate (silent CAPTCHA block, MCP-first), stating each gotcha once with its rationale to trim roughly 10-15 lines.
Fix or remove the broken "Dependencies: requirements.txt" reference in the References section — the file does not exist in the bundle — or point the link at references/setup-and-troubleshooting.md, which contains the actual install commands.
Consider narrowing the generic triggers ("search papers", "literature search", "paper discovery") toward Google-Scholar-specific phrasing to reduce overlap with adjacent academic-search skills like semantic-scholar.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is command-focused with no explanations of concepts Claude already knows, but there is real cross-section redundancy: the silent-CAPTCHA gotcha and the MCP-first pitfall each appear three to four times ("Mindset" points 2–3 restate the "Anti-Patterns" WHY lines almost verbatim). That is more than the score-5 "every token earns its place" bar but less severe than anchor 3's unnecessary explanation — it is emphasis duplication that could be consolidated. | 4 / 5 |
Actionability | Every workflow step ships copy-paste-ready executable commands covering the common cases: basic search ("--query ... --results 10"), advanced ("--author ... --year-start ... --year-end"), author profile, JSON export ("--format json --output /tmp/candidates.json"), a python3 one-liner to parse output, and the retry command. Setup is delegated to a real reference file with executable venv commands. This fully matches the score-5 anchor. | 5 / 5 |
Workflow Clarity | The six numbered steps form a clear sequence with an explicit error-recovery feedback loop (HTTP 429 or short body → wait 60 s → retry once → MCP fallback, "NEVER retry in a tight loop") and an explicit user-confirmation checkpoint before handing off to triage ("NEVER triage automatically — always confirm with the user first"). Not score 4 because no validation checkpoint is missing: detection, retry, fallback, and the handoff gate are all explicit. | 5 / 5 |
Progressive Disclosure | The SKILL.md is a clean overview pointing one level deep to a real, well-organized reference (references/setup-and-troubleshooting.md, verified to exist) and the script source, with a clearly labeled References section. However, the listed "Dependencies: requirements.txt" link does not resolve — no requirements.txt exists in the bundle — which is exactly the minor organization gap of anchor 4 rather than 5's fully easy navigation. | 4 / 5 |
Total | 18 / 20 Passed |