search-skills
31 database search skills. Trigger: finding papers, search strategies, querying academic databases. Design: one skill per database/tool with API details, query syntax, and rate limits.
Profile →npx skills add brycewang-stanford/Auto-Empirical-Research-Skills --skill search --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.
# Database Search — 31 Skills Select the skill matching the user's need, then `read` its SKILL.md. | Skill | Description | |-------|-------------| | [arxiv-api](./arxiv-api/SKILL.md) | Search and retrieve preprints from the arXiv open-access repository | | [arxiv-batch-reporting](./arxiv-batch-reporting/SKILL.md) | Batch search and report generation from arXiv preprint repository | | [arxiv-cli-to
What does the search-skills skill do?
31 database search skills. Trigger: finding papers, search strategies, querying academic databases. Design: one skill per database/tool with API details, query syntax, and rate limits.
How do I install it?
Run `npx skills add brycewang-stanford/Auto-Empirical-Research-Skills --skill search --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.