Write clear, reproducible experimental protocols and Standard Operating Procedures (SOPs) for any scientific discipline.
Scanned 9/6/2026
Install to Claude Code
npx -y skills add BioTender-max/awesome-bio-agent-skills --skill protocol-writing --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Protocol Writing?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/biotender-max-protocol-writing)More formats (shields.io, HTML) on the badges page.
# Protocol Writing — Reproducible Lab Protocols & SOPs
## Overview
Write clear, reproducible experimental protocols and Standard Operating Procedures (SOPs) for any scientific discipline.
## Structure
1. **Title and Version** — Protocol name, version number, date, author
2. **Purpose** — What this protocol achieves and when to use it
3. **Safety** — Hazards, PPE requirements, waste disposal
4. **Materials** — Exact reagents (catalog numbers, lot numbers), equipment, consumables
5. **Preparation** — Buffer recipes, stock solutions, equipment setup
6. **Procedure** — Numbered steps with exact quantities, temperatures, times, speeds
7. **Quality Control** — Expected results, acceptance criteria, troubleshooting
8. **Data Recording** — What to record, where, in what format
9. **References** — Published methods this protocol is based on
## Key Principles
- **Exact quantities**: "Add 2.5 mL" not "add some"
- **Catalog numbers**: Every reagent identified by manufacturer and catalog number
- **Time precision**: "Incubate for 30 min at 37°C" not "incubate for a while"
- **Critical steps**: Mark steps where deviation causes failure
- **Troubleshooting table**: Common problems and solutions
- **Version control**: Track changes between protocol versions
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!
Ultra-compressed communication mode. Cuts token usage ~75% by speaking like caveman while keeping full technical accuracy. Supports intensity levels: lite, full (default), ultra, wenyan-lite, wenyan-full, wenyan-ultra. Use when user says "caveman mode", "talk like caveman", "use caveman", "less tokens", "be brief", or invokes /caveman. Also auto-triggers when token efficiency is requested.
Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...
Routes multi-tool workflows through MCP servers for large datasets and pipelines. Use when Bash tool overhead is limiting throughput on data-heavy tasks.
Recovers prior coding-agent session context by running `catchup <agent> --since-compact`, which extracts a clean summary of a previous Codex, Claude Code, Antigravity, OpenCode, or Pi Agent session. Use when the user says "catch up", "what did the last session do", "get me up to speed", "I switched agents", or asks to recover/summarize a previous session before continuing. Do NOT use for the current conversation, git history, or any non-agent log.
Interview, source-challenge, verify, save, and ADR-gate fuzzy coding requests into Codex-ready implementation specs. Use when a feature, bugfix, refactor, migration, repo-wide change, or architecture task needs user-verified requirements, source-backed decisions, durable architecture decisions, acceptance criteria, validation commands, rollout notes, saved spec/ADR files, and a Codex execution prompt. Do not use when already fully specified or when the user wants direct implementation now.