skills/43-wentorai-research-plugins/skills/literature/metadata/orcid-api/SKILL.md
Look up researcher profiles and academic identities via the ORCID registry
npx skillsauth add brycewang-stanford/Awesome-Agent-Skills-for-Empirical-Research orcid-apiInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
ORCID (Open Researcher and Contributor ID) is a nonprofit organization that provides unique, persistent digital identifiers to researchers worldwide. With over 18 million registered researchers, ORCID has become the standard for disambiguating author identities across the scholarly ecosystem. Publishers, funders, and institutions use ORCID to reliably connect researchers with their works, grants, and affiliations.
The ORCID Public API provides read access to public data in ORCID records. This includes biographical information, employment history, education, works (publications), funding, and peer review activities. The API is essential for building research information systems, verifying researcher identities, and integrating with institutional repositories.
Authentication is required. The public API uses OAuth 2.0 with a client credentials grant, which provides a bearer token for read-only access to public data. Registration is free and tokens can be obtained programmatically.
The ORCID Public API requires an OAuth 2.0 access token. Register for free API credentials at https://orcid.org/developer-tools and obtain a token:
curl -X POST "https://orcid.org/oauth/token" \
-H "Accept: application/json" \
-d "client_id=YOUR_CLIENT_ID" \
-d "client_secret=YOUR_CLIENT_SECRET" \
-d "grant_type=client_credentials" \
-d "scope=/read-public"
Include the token in all API requests:
Authorization: Bearer YOUR_ACCESS_TOKEN
Tokens are long-lived (typically 20 years) and can be reused across sessions.
GET https://pub.orcid.org/v3.0/{orcid-id}/recordcurl -H "Authorization: Bearer YOUR_TOKEN" \
-H "Accept: application/json" \
"https://pub.orcid.org/v3.0/0000-0002-1825-0097/record"
person (name, biography, emails, addresses), activities-summary (works, funding, employment, education, peer reviews).GET https://pub.orcid.org/v3.0/{orcid-id}/workscurl -H "Authorization: Bearer YOUR_TOKEN" \
-H "Accept: application/json" \
"https://pub.orcid.org/v3.0/0000-0002-1825-0097/works"
group array of work summaries, each containing title, external-ids (DOI, PMID, etc.), type, publication-date, and journal-title.GET https://pub.orcid.org/v3.0/searchcurl -H "Authorization: Bearer YOUR_TOKEN" \
-H "Accept: application/json" \
"https://pub.orcid.org/v3.0/search?q=family-name:Hinton+AND+affiliation-org-name:Toronto&rows=10"
result array containing orcid-identifier (ORCID iD and URI) for each matching researcher.The public API allows 24 requests per second and 40 burst requests. The member API has higher limits. If limits are exceeded, the API returns HTTP 503 with a Retry-After header. For bulk data access, ORCID provides annual data dumps and a Lambda file for incremental updates. Rate limits apply per access token.
Confirm that a researcher's ORCID is valid and retrieve their public profile:
curl -H "Authorization: Bearer YOUR_TOKEN" \
-H "Accept: application/json" \
"https://pub.orcid.org/v3.0/0000-0001-5109-3700/person"
Retrieve all works associated with an ORCID profile and extract DOIs:
curl -H "Authorization: Bearer YOUR_TOKEN" \
-H "Accept: application/json" \
"https://pub.orcid.org/v3.0/0000-0002-1825-0097/works" | jq '.group[].work-summary[0] | {title: .title.title.value, doi: (.["external-ids"]["external-id"][] | select(.["external-id-type"] == "doi") | .["external-id-value"])}'
Search for ORCID profiles affiliated with a specific organization:
curl -H "Authorization: Bearer YOUR_TOKEN" \
-H "Accept: application/json" \
"https://pub.orcid.org/v3.0/search?q=affiliation-org-name:Stanford+AND+current-institution-affiliation-name:Stanford&rows=50"
tools
Show mcp-stata identity, connected tools, and status. Use when the user asks if mcp-stata is available, asks about access to the toolkit, or asks what Stata tools are connected.
tools
Activate when users mention Stata commands, .do files, regressions, econometrics, stored results, graphs, dataset inspection, replication, or Stata errors. Route the task through mcp-stata tools and the specialized research skills instead of treating it as plain text coding.
development
Build and review paper-ready regression, balance, and summary tables from Stata outputs. Use when the user needs a clean table for a draft, appendix, or coauthor share-out.
tools
Install, configure, update, or verify mcp-stata across Claude Code, Codex, Gemini CLI, Cursor, Windsurf, and VS Code. Activate when users ask to set up the Stata toolkit or troubleshoot the installation.