openalex-api
Skill63 starsChanged 5 months agoMITView on GitHub
Access and analyze OpenAlex scholarly metadata through the REST API, including works, authors, institutions, sources, concepts, topics, funders, and publishers. Use when asked to retrieve publication or citation metadata, run OpenAlex searches with filters, map author-institution relationships, or build reproducible bibliometric datasets from OpenAlex.
- Reads credentials
In this repository47 other files it gives its agents.
- install/claude.mdCLAUDE.md
- daskSkill
- econ-visualizationSkill
- geopandasSkill
- matplotlibSkill
- plotlySkill
- polarsSkill
- pymc-bayesian-modelingSkill
- scikit-learnSkill
- seabornSkill
- statistical-analysisSkill
- statsmodelsSkill
- pyfixestSkill
- python-panel-dataSkill
- r-econometricsSkill
- stata-data-cleaningSkill
- stata-regressionSkill
- wrdsSkill
- api-data-fetcherSkill
- citation-managementSkill
- datacommons-clientSkill
- exploratory-data-analysisSkill
- financial-text-nlpSkill
- literature-reviewSkill
- lit-review-assistantSkill
- paper-2-acfin-webSkill
- research-ideationSkill
- research-lookupSkill
- sec-edgarSkill
- web-scrapeSkill
- academic-paper-writerSkill
- beamer-presentationSkill
- econ-humanizer-plusSkill
- econ-humanizerSkill
- econ-refereeSkill
- econ-slidesSkill
- econ-writeSkill
- econ-writing-plusSkill
- hypothesis-generationSkill
- latex-econ-modelSkill
- latex-postersSkill
- latex-tablesSkill
- paper-pdfSkill
- peer-reviewSkill
- scholar-evaluationSkill
- scientific-critical-thinkingSkill
- venue-templatesSkill
The file
We split this skill into the rules it gives an agent
11 rules. About 0 are common, 2 are distinctive, and 9 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
9
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 13
Use this skill to turn research questions into reliable OpenAlex API queries and structured outputs.
- Very specific: line 25
Use repeated --filter flags for AND logic.
- Very specific: line 26
Use OpenAlex pipe syntax (for example value1|value2) inside one filter for OR logic.
- Very specific: line 27
Use --select to reduce payload size for large pulls.
- Very specific: line 28
Use --cursor '*' for deep paging beyond basic page limits.
- Very specific: line 30
Use OPENALEX_API_KEY or --api-key when available for higher-rate access.
- Distinctive: line 58
Prefer JSON for full response bundles and JSONL for row-wise pipelines.
- Very specific: line 59
Keep original IDs (id, ids.openalex, DOI fields) unchanged in exports.
- Distinctive: line 60
When reporting findings, cite exact query parameters used to ensure reproducibility.
- Very specific: line 64
Use scripts/query_openalex.py for all API calls.
- Very specific: line 65
Use references/openalex-query-patterns.md for entity routing, filter templates, and reusable query patterns.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Barrios Skills — John Barrios's curated workflow for economists and accountants. Prioritize reproducible empirical work, clear identification language, and journal-ready output.
OpenAlex API
Overview
Use this skill to turn research questions into reliable OpenAlex API queries and structured outputs. Prefer scripts/query_openalex.py for repeatable retrieval, pagination, and filter-safe URL construction.
Workflow
- Define the target entity:
works,authors,institutions,sources,concepts,topics,funders, orpublishers. - Define retrieval scope: exact ID lookup, search, or filtered dataset pull.
- Build query parameters with
scripts/query_openalex.pyinstead of handcrafting URLs. - Retrieve data to JSON/JSONL and keep the raw export before downstream cleaning.
- Validate key fields (IDs, dates, citation counts, authorships) before analysis.
Query Rules
- Use repeated
--filterflags for AND logic. - Use OpenAlex pipe syntax (for example
value1|value2) inside one filter for OR logic. - Use
--selectto reduce payload size for large pulls. - Use
--cursor '*'for deep paging beyond basic page limits. - Include
--mailto you@domain.edufor polite-pool style identification. - Use
OPENALEX_API_KEYor--api-keywhen available for higher-rate access.
Common Commands
# Fetch one work by OpenAlex ID
python3 scripts/query_openalex.py works --entity-id W2741809807 --select "id,display_name,publication_year,cited_by_count"
# Search works and save first 200 records
python3 scripts/query_openalex.py works \
--search "political polarization" \
--filter "from_publication_date:2020-01-01" \
--sort "cited_by_count:desc" \
--per-page 100 \
--pages 2 \
--output polarization_works.json
# Cursor-paginate author records to JSONL
python3 scripts/query_openalex.py authors \
--filter "last_known_institutions.country_code:US" \
--cursor "*" \
--max-results 500 \
--format jsonl \
--output us_authors.jsonlOutput Guidance
- Prefer JSON for full response bundles and JSONL for row-wise pipelines.
- Keep original IDs (
id,ids.openalex, DOI fields) unchanged in exports. - When reporting findings, cite exact query parameters used to ensure reproducibility.
Resources
- Use
scripts/query_openalex.pyfor all API calls. - Use
references/openalex-query-patterns.mdfor entity routing, filter templates, and reusable query patterns.
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
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.

