i1
Paper Retrieval Agent - Multi-database paper fetching from Semantic Scholar, OpenAlex, arXiv Handles rate limiting, deduplication, and PDF URL extraction Use when: fetching papers, searching databases, paper retrieval
Profile →npx skills add brycewang-stanford/Auto-Empirical-Research-Skills --skill i1 --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.
## ⛔ Prerequisites (v8.2 — MCP Enforcement) No prerequisites required for this agent. ### Checkpoints During Execution - 🔴 SCH_DATABASE_SELECTION → `diverga_mark_checkpoint("SCH_DATABASE_SELECTION", decision, rationale)` - 🔴 SCH_API_KEY_VALIDATION → `diverga_mark_checkpoint("SCH_API_KEY_VALIDATION", decision, rationale)` ### Fallback (MCP unavailable) Read `research/decision-log.yaml` (or `.rese
What does the i1 skill do?
Paper Retrieval Agent - Multi-database paper fetching from Semantic Scholar, OpenAlex, arXiv Handles rate limiting, deduplication, and PDF URL extraction Use when: fetching papers, searching databases, paper retrieval
How do I install it?
Run `npx skills add brycewang-stanford/Auto-Empirical-Research-Skills --skill i1 --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.