document-skills
10 document processing skills. Trigger: extracting text from PDFs, parsing references, document Q&A. Design: parsing pipelines (GROBID, marker) and structured extraction tools.
Profile →npx skills add brycewang-stanford/Auto-Empirical-Research-Skills --skill document --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.
# Document Processing — 10 Skills Select the skill matching the user's need, then `read` its SKILL.md. | Skill | Description | |-------|-------------| | [anystyle-api](./anystyle-api/SKILL.md) | Citation reference parser using machine learning | | [docsgpt-guide](./docsgpt-guide/SKILL.md) | Deploy DocsGPT for private document analysis and research knowledge bases | | [grobid-pdf-parsing](./grobid-
What does the document-skills skill do?
10 document processing skills. Trigger: extracting text from PDFs, parsing references, document Q&A. Design: parsing pipelines (GROBID, marker) and structured extraction tools.
How do I install it?
Run `npx skills add brycewang-stanford/Auto-Empirical-Research-Skills --skill document --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.