CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

google-scholar-search

Search Google Scholar for academic papers and author profiles. Use when discovering papers to triage — by keyword, author, or year range. Returns titles, authors, abstracts, and links. Triggers: search papers, find papers, google scholar, search scholar, find author, author profile, literature search, paper discovery, search academic literature.

Quality

92%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

88%Weight 40%Scale 1-5

Reviews 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.

DimensionReasoningScore

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

Description

96%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description that explicitly states what the skill does, what it returns, and when to use it, backed by a comprehensive list of natural trigger phrases. The only weakness is that several generic paper-discovery triggers overlap with adjacent academic-search skills, slightly raising conflict risk.

DimensionReasoningScore

Specificity

"Search Google Scholar for academic papers and author profiles", "by keyword, author, or year range", and "Returns titles, authors, abstracts, and links" list multiple concrete actions and outputs with comprehensive coverage of the skill's niche. It exceeds the score-4 anchor because there are no notable gaps in the capability coverage it claims.

5 / 5

Completeness

Both questions are explicitly answered: "what" via "Search Google Scholar... Returns titles, authors, abstracts, and links" and "when" via "Use when discovering papers to triage — by keyword, author, or year range" plus explicit trigger phrases. This is a direct match to the score-5 anchor's structure.

5 / 5

Trigger Term Quality

The trigger list — "search papers, find papers, google scholar, search scholar, find author, author profile, literature search, paper discovery, search academic literature" — covers nine natural phrases a user would actually say, including synonym pairs (search/find, google scholar/search scholar). This matches the comprehensive-synonyms anchor; no file extensions apply to this skill.

5 / 5

Distinctiveness Conflict Risk

The Google-Scholar-specific triggers ("google scholar", "search scholar", "author profile") form a clear niche, but half the trigger list ("search papers", "literature search", "paper discovery") is generic academic-search language that would equally fire for closely related skills such as a semantic-scholar or arxiv search skill. This is the score-4 anchor — mostly distinct with minor overlap risk — rather than 5's minimal conflict risk.

4 / 5

Total

19

/

20

Passed

Validation

81%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

allowed_tools_field

'allowed-tools' contains unusual tool name(s)

Warning

metadata_version

'metadata.version' is missing

Warning

relative_links

Relative link issues: 1 missing

Warning

Total

13

/

16

Passed

Repository

pantheon-org/tekhne

Path

skills/documentation/research/google-scholar-search/SKILL.md

Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.