pharma-skills
6 pharmaceutical research skills. Trigger: drug discovery, pharmacology, clinical trial design, regulatory filing. Design: end-to-end pipeline from target identification to clinical trials.
Profile →npx skills add brycewang-stanford/Auto-Empirical-Research-Skills --skill pharma --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.
# Pharmaceutical Research — 6 Skills Select the skill matching the user's need, then `read` its SKILL.md. | Skill | Description | |-------|-------------| | [clinical-pharmacology-guide](./clinical-pharmacology-guide/SKILL.md) | Clinical pharmacology principles for dosing, drug interactions, and patient s... | | [clinical-trial-design-guide](./clinical-trial-design-guide/SKILL.md) | Clinical trial
What does the pharma-skills skill do?
6 pharmaceutical research skills. Trigger: drug discovery, pharmacology, clinical trial design, regulatory filing. Design: end-to-end pipeline from target identification to clinical trials.
How do I install it?
Run `npx skills add brycewang-stanford/Auto-Empirical-Research-Skills --skill pharma --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.