agentleFS
zamushwanizamushwani/biomedical-ai-skills/.cursor/rules/biomedical-skills.mdc

biomedical-ai-skills / rules

Cursor rule1 starsChanged 3 months agoMITView on GitHub

Biomedical AI Skills — protocol files for cancer bioinformatics, and the rules for changing them

  • Installs packages

The file

We split this biomedical-skills.mdc into the rules it gives an agent

3 rules. About 0 are common, 2 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Read the relevant skills/<name>/SKILL.md before writing analysis code in that domain.

    line 11
  2. Distinctive:

    Verify every version, signature and default against the registry and package source in the current session.

    line 15
  3. Distinctive:

    Never claim a test passes unless it was executed.

    line 18

≈ “Common” is an estimate: at least 1 in 5 of the 6,809 Cursor rule files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
biomedical-skills.mdc
---
description: Biomedical AI Skills — protocol files for cancer bioinformatics, and the rules for changing them
globs: skills/**/*.md,tools/*.py,pyproject.toml
alwaysApply: false
---

# Biomedical AI Skills

This repository is a library of **16 SKILL.md protocol files** under `skills/`. Each is a self-contained protocol for one domain: what to run, which parameter values and why, and the mistakes that produce plausible-looking wrong answers.

Read the relevant `skills/<name>/SKILL.md` before writing analysis code in that domain. The full instructions are in [AGENTS.md](../../AGENTS.md) — Cursor's Agent mode reads that file directly, while Chat and Composer read this rule.

## Rules for changing a skill

1. Verify every version, signature and default against the registry and package source in the current session. Never write one from memory.
2. A skill edit must be released in the same session, or `pip install` serves stale content.
3. A green CI run is not proof. Verify the published artifact.
4. Never claim a test passes unless it was executed.
5. Stage explicit paths. Never `git add .` — untracked personal files sit in the repository root.

## Portability

Skills must stay tool-neutral: no argument placeholders, no file-include directives, no inline shell execution syntax. That is what lets the same file work across Claude Code, Codex CLI, Cursor and Gemini CLI. `python3 tools/check_portability.py` enforces it.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.