metadata-skills
24 metadata & bibliometrics skills. Trigger: DOI resolution, citation metrics, author disambiguation, bibliometrics. Design: metadata APIs and bibliometric analysis tools for scholarly records.
Profile →npx skills add brycewang-stanford/Auto-Empirical-Research-Skills --skill metadata --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.
# Metadata & Bibliometrics — 24 Skills Select the skill matching the user's need, then `read` its SKILL.md. | Skill | Description | |-------|-------------| | [academic-paper-summarizer](./academic-paper-summarizer/SKILL.md) | Summarize academic papers with structured extraction of key elements | | [altmetrics-guide](./altmetrics-guide/SKILL.md) | Guide to altmetrics and research impact beyond trad
What does the metadata-skills skill do?
24 metadata & bibliometrics skills. Trigger: DOI resolution, citation metrics, author disambiguation, bibliometrics. Design: metadata APIs and bibliometric analysis tools for scholarly records.
How do I install it?
Run `npx skills add brycewang-stanford/Auto-Empirical-Research-Skills --skill metadata --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.