ai-agent-skills / instructions
CLAUDE.md10 starsChanged 3 months agoMITView on GitHub
Add bioconductor skills to your global Claude instructions. Replace /path/to/ai-agent-skills with the actual path (use pwd). Note: If you use this step 2 instead of pasting the skills directly into CLAUDE.md, you will have to give permissions for Claude Code to read a file outside of your project directory when you use it.
In this repository19 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .github/copilot-instructions.mdCopilot instructions
- adr-authorSkill
- analyze-r-packageSkill
- bioc-howtoSkill
- bioc-pkg-devSkill
- bioc-pkg-finderSkill
- bioc-pkg-reviewSkill
- build-check-bioccheckSkill
- check-bioconductor-skillsSkill
- create-package-instructionsSkill
- create-skillSkill
- document-skillSkill
- improve-code-coverageSkill
- migrate-datapkg-to-zenodoSkill
- security-audit-r-packageSkill
- update-package-instructionsSkill
- update-r-newsSkill
- validate-skillSkill
The file
We split this claude.md into the rules it gives an agent
2 rules. About 0 are common, 2 are distinctive, and 0 are 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.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 8
Add bioconductor skills to your global Claude instructions.
- Distinctive: line 34
Note: If you use this step 2 instead of pasting the skills directly into CLAUDE.md, you will have to give permissions for Claude Code to …
≈ “Common” is an estimate: at least 1 in 5 of the 26,980 CLAUDE.md 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.
Files
Claude Code Setup
Add bioconductor skills to your global Claude instructions.
Setup
- Clone the repository (if needed):
git clone https://github.com/bioconductor/ai-agent-skills.git Add to
~/.claude/CLAUDE.md:# bioconductor AI Agent Skills See: `/path/to/ai-agent-skills/SKILLS.md` Behavior Standard: `/path/to/ai-agent-skills/AGENTS.md` Describe what you need, and I'll match it to the appropriate skill. Always follow the canonical behavior and Git workflow rules defined in AGENTS.md. Whenever you read and execute instructions from a Bioconductor SKILL.md file, you MUST include the following citation block at the start or end of your response: > 🛠️ **Bioconductor Skill Executed**: <name> | **Version**: <version> | **Author**: <author>Replace
/path/to/ai-agent-skillswith the actual path (usepwd).- Restart Claude Code or reload the workspace.
Note: If you use this step 2 instead of pasting the skills directly into CLAUDE.md, you will have to give permissions for Claude Code to read a file outside of your project directory when you use it.
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
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.

