agentleFS
yyyy/claude-scholar/skills/openalex/SKILL.md

openalex

Skill39 starsChanged 8 months agoMITView on GitHub

Query and analyze scholarly literature using the OpenAlex API. Use for literature searches, finding papers by author or institution, citation analysis, and bibliometric queries.

  • Reads credentials

6 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

2 rules. 0 are common, 0 are distinctive, and 2 are very specific to this project.

  • 0

    Common

    Most of the 6 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Use the bundled dependency-aware CLI.

    line 12
  2. Very specific:

    Do not import openalex_client.py from uv run python -.

    line 20

“Common” is measured: kept by at least 6 in 10 of the 6 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

OpenAlex literature search

Query the OpenAlex API for academic papers, authors, institutions, and citation data.

CLI

Use the bundled dependency-aware CLI. Its inline script metadata installs requests in an isolated uv environment without modifying the caller's lockfile.

OPENALEX="<skill-directory>/scripts/openalex.py"
uv run --script "$OPENALEX" search-works "CRISPR"

Do not import openalex_client.py from uv run python -; stdin scripts ignore the client's inline dependency metadata.

The client handles rate limiting and retries. Set OPENALEX_API_KEY in the environment; OpenAlex permits limited no-key requests.

Key Patterns

Search works

uv run --script "$OPENALEX" search-works "CRISPR" \
  --filter 'publication_year=>2020' --filter is_oa=true \
  --sort cited_by_count:desc

Resolve names before filtering

Names are ambiguous. Search for the entity, inspect candidate identifiers, affiliations, and topics, then filter by the selected OpenAlex ID:

uv run --script "$OPENALEX" search-works "Jennifer Doudna" --per-page 5
# Inspect candidates, then filter with the selected OpenAlex author ID:
uv run --script "$OPENALEX" search-works "CRISPR" \
  --filter authorships.author.id=A1969205032

Get entity by external ID

uv run --script "$OPENALEX" get-entity works \
  'https://doi.org/10.1038/s41586-021-03819-2'
uv run --script "$OPENALEX" get-entity authors \
  'https://orcid.org/0000-0003-1613-5981'

Batch DOI lookup (up to 100 per request)

uv run --script "$OPENALEX" batch-lookup works \
  10.1038/s41586-021-03819-2 10.1038/s41586-020-2649-2 --id-field doi

Aggregate by field

uv run --script "$OPENALEX" group-by works publication_year \
  --filter authorships.author.id=A1969205032

Filter Syntax

Single:     --filter publication_year=2023
AND:        --filter 'publication_year=>2020' --filter is_oa=true
OR:         --filter 'type=journal-article|book'
NOT:        --filter 'type=!paratext'
Range:      --filter publication_year=2020-2024
Greater:    --filter 'cited_by_count=>100'
Both inst:  --filter authorships.institutions.id=ID1+ID2
Either:     --filter 'authorships.institutions.id=ID1|ID2'

Common filters: publication_year, is_oa, cited_by_count, type, authorships.author.id, authorships.institutions.id, primary_location.source.id, topics.id, has_doi.

Attribution

OpenAlex client adapted from K-Dense-AI/claude-scientific-skills (MIT License).

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.