Back to all resources
scientific-agent-skills v2.67 MIT · free Claude Code, Cursor, Codex LIVE

Give the agent one lab tool, not the lab.

An agent that knows Python still guesses at scanpy's API or which genomics database to query. Scientific Agent Skills is 164 separate, tested skills, each one documentation and examples for a specific scientific library or database. You install the one or two your work actually needs. Nothing here touches your data unless the skill calls out to a database.

By Raj Singh · September 2026 · 44k stars · 164 skills, 100+ databases · 5 min read

WHAT IT LOOKS LIKE

There is no dashboard here either, just a bigger context window and better answers. Ask about a bulk RNA-seq result and the agent reaches for the actual `bulk-rnaseq` skill's documented workflow instead of guessing at an API.

An isometric illustration of agent work stations feeding into a central hub, standing in for many narrow skills feeding one agent
One skill, one scientific library, no dashboard neededAgileSingh
BEFORE YOU INSTALL IT

Install one skill, not 164. gh skill install K-Dense-AI/scientific-agent-skills scanpy pulls a single named skill. The bare npx skills add command with no skill name pulls the entire library into context at once.

Needs Python 3.13 or newer. Set by pyproject.toml. Skills that wrap a specific library, scanpy, biopython, cobrapy, still need that library installed separately in your environment.

Every skill is security-scanned. A CI workflow runs cisco-ai-skill-scanner against every pull request, with the results published in docs/security-report.md. Worth reading once before you trust a skill with lab data.

Version-pin it for reproducibility. gh skill install ... --pin v2.66.0 locks a skill to a release instead of tracking main. A lab workflow that must be reproducible in a year should pin, not track latest.

Licence, in plain English: MIT. Free for commercial and academic work, fine to embed, no obligation beyond keeping the licence file. The accompanying paper asks for a citation if you use it in published research.

Honest limitA skill is documentation and examples, not a guarantee. It makes the agent reach for the right API and the right defaults; it does not review the science. The result still needs a scientist to read it.
Read the whole setup

Get the setup that works.

Drop your email and unlock the rest: what you need, the install for a single skill, the update and pin commands, and how to tell if a skill actually fired.

One email. No follow-up unless I ship something that fits.

WHAT YOU NEED
  • Python 3.13 or newer
  • The GitHub CLI (gh), for the gh skill install path
  • Claude Code, Cursor, Codex or another Agent Skills-compatible client
  • The underlying library, already installed, for whichever skill you pick
INSTALL

One named skill, for your agent

Name the skill and the agent so the install stays small. The full-library install exists but is rarely what you want on your first run.

The install

terminalone skill, one agent
$ gh skill install K-Dense-AI/scientific-agent-skills scanpy --agent claude-code → scanpy skill installed and available in your next session

Repeat the command with a different skill name to add more. Each one stays a separate, removable install rather than one monolithic package.

Prove itAsk the agent a question that needs the skill, for example a scanpy preprocessing question. An answer that cites the skill's documented workflow, not a generic guess, means it loaded.
CONFIGURE

Pin it if it needs to reproduce

There is no settings file, the two real choices are where you install to and whether you pin a version.

terminalreproducible install
$ gh skill install K-Dense-AI/scientific-agent-skills scanpy --pin v2.66.0
SettingDefaultWhy I change it
Pintracks mainA published-analysis workflow should not silently change behavior when the skill updates. Pin the version you validated against.
Install scopeuser-level (~/.agents/skills)Project-level (.agents/skills/ inside the repo) when a specific research project needs a skill nobody else on the machine should get by default.
Updatinggh skill update refreshes one installed skill; gh skill update --all refreshes every skill from this library you have installed.
DAILY DRIVING

Ask in plain words

The skill loads into context automatically once installed. You do not invoke it by name, the agent recognizes when the task matches.

  • Ask the domain question. "Run differential expression on this bulk RNA-seq count matrix" is enough for the bulk-rnaseq skill to engage.
  • Let it choose the database. Skills that wrap a database, PatentsView, Treasury fiscal data, know the current API shape, including recent breaking changes the maintainers already patched.
  • Check the citation. A skill answer sourced from a specific database or paper should say so. If it does not, ask which source it used.

The value shows up as fewer wrong API calls and fewer confidently wrong defaults, not as a new interface to learn.

WHEN IT DRIFTS

Two failures, both configuration

The agent still guesses at the API
The skill was never installed, or was installed for a different agent flag than the one you are running. Re-run gh skill install with the correct --agent value.
A database lookup returns an error
The upstream API changed. Check docs/security-report.md and recent commits, since this project patches dead or changed endpoints quickly, most recently PatentsView and Treasury.
ResetRemove the skill directory under ~/.agents/skills/ or the project-level .agents/skills/ and reinstall. Nothing outside that folder is touched.
THE SHAPE OF IT

Where everything lives

~/.agents/skills/scientific-agent-skills/user-level install, available in every project .agents/skills/scientific-agent-skills/project-level install, scoped to one repo skills/<name>/one folder per skill, inside this repo, each independently testable docs/security-report.mdthe CI security scan results per skill tests/the pytest suite you can run per skill or in full

Removing the top-level folder removes every skill installed from this library in one step.

That is the whole setup

One skill, named and pinned, beats installing all 164 at once. The agent gets the specific documentation it needed for the one library your lab actually runs, and nothing else crowding its context.

Open on GitHub →

↑ Unlocks the moment you submit the form above.

RS
WRITTEN BY

Raj Singh

I'm Raj Singh, founder of DebtOps.ai and a Claude certified partner. Over the last five years I've managed $25M in ads, built AI solutions for Fortune 100 companies, and installed AI operating systems and AI brains inside small businesses. Everything here is something I've shipped, debugged, or watched a client ship. My goal with AgileSingh is to make you irreplaceable in this AI age.

$25M
Ads managed · 5 yrs
F100
Enterprise AI builds
Claude
Certified partner
23
Guides shipped
More guides

Now give the agent memory of what it found.

A skill makes one session more capable. The gbrain setup guide is how the finding from that session survives into the next one instead of being re-derived from scratch.