doi-content-negotiation
Retrieve structured metadata from any DOI via HTTP content negotiation
Profile →npx skills add brycewang-stanford/Auto-Empirical-Research-Skills --skill doi-content-negotiation --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# DOI Content Negotiation ## Overview Any DOI can return structured metadata in multiple formats through HTTP content negotiation — simply set the `Accept` header when requesting `https://doi.org/{doi}`. This is the most universal way to get citation metadata, BibTeX entries, JSON-LD, and RDF from any publisher without needing a specific API. Works for all 300M+ registered DOIs. Free, no authentic
What does the doi-content-negotiation skill do?
Retrieve structured metadata from any DOI via HTTP content negotiation
How do I install it?
Run `npx skills add brycewang-stanford/Auto-Empirical-Research-Skills --skill doi-content-negotiation --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From brycewang-stanford/Auto-Empirical-Research-Skills, a repository with 3,244 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.