CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

literature-search-openalex

Query the OpenAlex scholarly database for research papers, authors, institutions, topics, sources, publishers, funders, geo-locations, and keywords. Use when searching academic papers, resolving DOIs, downloading open-access PDFs, finding an author's publications, aggregating bibliometric data (citation counts, h-index, impact factor), exploring the research taxonomies, or performing DOI lookups.

Quality

90%

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

82%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 dense, highly actionable CLI skill: executable commands, cost/rate-limit tables, and explicit error-recovery guidance, with detail correctly split into one-level-deep reference files. Main gaps are repeated credentials-protocol phrasing, implicit validation checkpoints in the main workflows, and an orphaned citation.bib bundle file.

Suggestions

State the credentials-skill protocol once (e.g., in Prerequisites or Core Rules) and reference it tersely elsewhere ('see credential rule above') instead of repeating the full instruction ~5 times.

Add explicit validation checkpoints to Common Workflows, e.g. after `resolve`: 'confirm the candidate ID (display_name/hint) before using it in --filter', and after `filter`: 'check result count is non-empty before slimming with jq'.

Either link `references/citation.bib` from the body (e.g., in Entity References or a workflow for exporting a bibliography) or remove it from the bundle so every reference file is navigable from SKILL.md.

DimensionReasoningScore

Conciseness

The body is largely lean — tables for costs and error codes, terse rules, no explanations of concepts Claude already knows — but "use the safe credentials protocol in the credentials skill" is repeated ~5 times (Prerequisites, Core Rule 5, download-pdf, rate-limit, error table) and Rule 2 restates 'resolve' twice. Not 5: these repetitions could be trimmed to a single stated rule; not 3: the padding is minor, not whole unnecessary sections.

4 / 5

Actionability

Fully executable, copy-paste-ready commands throughout: five complete `uv run scripts/openalex_cli.py ...` workflows (author works, DOI lookup, bulk DOI, group-by, sample), concrete flag documentation, and an error-code-to-action table. Matches the anchor: specific examples cover the common cases.

5 / 5

Workflow Clarity

Sequences are clear (resolve → filter shown in Common Workflows, Rule 2 mandates it) and feedback loops exist (max 3 retries, 429-body disambiguation with 'Do not retry' guidance, verify downloaded PDFs are non-empty, report empty results accurately). Not 5: the main workflows lack inline numbered validation checkpoints — e.g., no explicit 'confirm the resolved ID before filtering' or 'verify results non-empty before jq' step — leaving checkpoints implicit in examples and comments.

4 / 5

Progressive Disclosure

SKILL.md is a well-organized overview with clearly signaled, one-level-deep references to `references/*.md` per entity (all files exist, no nesting) and the CLI in `scripts/`. Not 5: `references/citation.bib` exists in the bundle but is never mentioned or linked anywhere in the body, making that asset undiscoverable from the skill — a minor organization gap matching the anchor-4 description.

4 / 5

Total

17

/

20

Passed

Description

92%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: third-person voice, concrete action verbs, an explicit 'Use when...' clause with natural trigger phrases, and a clearly anchored niche (OpenAlex). Only weakness is a handful of missing natural synonyms a user might say, such as 'literature search'.

DimensionReasoningScore

Specificity

Lists multiple concrete actions across the domain — "resolving DOIs", "downloading open-access PDFs", "finding an author's publications", "aggregating bibliometric data (citation counts, h-index, impact factor)" — with comprehensive coverage of entity types. Not 4: there are no minor gaps in the action list; it enumerates the concrete capabilities exhaustively rather than leaving coverage holes.

5 / 5

Completeness

Explicitly answers both: what — "Query the OpenAlex scholarly database for research papers, authors, institutions..." — and when — "Use when searching academic papers, resolving DOIs, downloading open-access PDFs..." with concrete trigger phrases. Matches the anchor-5 example structure directly.

5 / 5

Trigger Term Quality

Natural user phrases like "searching academic papers", "resolving DOIs", "open-access PDFs", and "h-index" are present, but a few common variants (e.g., "literature search", "find citations/papers on X") are missing. Not 5: keyword coverage is good but lacks the synonym-level comprehensiveness of the top anchor; not 3: it clearly exceeds 'some relevant keywords'.

4 / 5

Distinctiveness Conflict Risk

"OpenAlex scholarly database" names a clear niche, and triggers like DOI resolution, h-index, and bibliometric aggregation are unlikely to fire for unrelated skills. Not 4: overlap risk with generic search or other bibliographic skills is minimal because the source and triggers are domain-anchored.

5 / 5

Total

19

/

20

Passed

Validation

100%

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

google-deepmind/science-skills

Path

skills/literature_search_openalex/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.