Skills DirectorySkills Directory
SkillsLearnSecurityCategoriesDocsBlogPro
Sign InSubmit Skill
Skills Directory

Security-tested agent skills for Claude, coding agents, and AI workflows.

Directory

  • Browse Skills
  • All Skills A–Z
  • Claude Skills
  • Claude Code Skills
  • Agent Skills
  • Categories
  • Authors
  • Submit a Skill

Learn

  • Learn Hub
  • Install Claude Skills
  • Write SKILL.md
  • Skills vs MCP
  • Directories Compared

Security

  • Security
  • Methodology
  • Secure Claude Skills
  • Security Badges
  • Chrome Extension
  • Skill Manager

Company

  • About
  • Community
  • Blog
  • API Docs
  • Advertise

2026 Skills Directory. All rights reserved.

ProTermsPrivacyRefunds
Back to skills

Sample Biobanking

ASecurity

Biobanking best practices — consent, SOPs, cold chain, sample tracking, and quality management.

2 stars
0 votes
0 copies
0 views
Added 9/29/2026
ai-agentsgoawstestingdocumentation

Security Analysis

A100/100

Scanned 9/29/2026

$npx -y skills add aicodedecode/awesome-muse-skills --skill sample-biobanking --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Sample Biobanking?

Add the live security badge to your README — it updates automatically with every re-scan.

Security grade badge for Sample Biobanking
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/aicodedecode-sample-biobanking/badge)](https://www.skillsdirectory.com/skills/aicodedecode-sample-biobanking)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
Files
SKILL.md
---
name: sample-biobanking
description: Biobanking best practices — consent, SOPs, cold chain, sample tracking, and quality management.
category: scientific
---

## Overview

sample-biobanking covers the professional management of biological sample collections: ethical
and legal foundations (consent, governance), standard operating procedures for collection and
processing, cold-chain logistics, inventory tracking (LIMS), and quality management. A biobank's
value is entirely in sample quality and annotation — poorly collected samples with thin metadata
are freezer filler, not a resource.

## When to use

- Establishing a biobank or biorepository: governance, infrastructure, SOPs.
- Consent design: broad vs tiered consent, re-contact, withdrawal, commercial use.
- Collection SOPs: pre-analytical variables (time to freeze, tube types, aliquoting).
- Cold chain: freezers, LN2, monitoring, backup power, disaster planning.
- LIMS: sample tracking, barcoding, chain of custody.
- Quality management: QC metrics, audits, accreditation (CAP, ISO 20387).
- Sample sharing: MTAs, access committees, cost recovery.

## Core concepts

- **Consent.** Broad consent for future unspecified research (with ethics approval) vs
  tiered/specific consent; must cover: re-contact, return of results policy, commercial use,
  data sharing, withdrawal (and what withdrawal means for already-distributed samples).
  Consent forms need ethics-committee approval and periodic review — regulations evolve
  (GDPR, national biobank laws).
- **Pre-analytical variables.** The dominant quality factor: time from collection to
  processing/freezing (record it — "cold ischemia time"), tube type (EDTA vs heparin vs
  citrate changes downstream assays), centrifugation protocol, aliquot size (avoid
  freeze-thaw by aliquoting single-use volumes). Standardize ruthlessly; document deviations.
- **SPREC codes.** Standard PREanalytical Code: documents pre-analytical conditions in a
  compact code (sample type, collection tube, time to freeze, storage). Use it — it's how
  downstream users judge fitness-for-purpose.
- **Cold chain.** −80°C freezers for most analytes, LN2 vapor phase for cells/DNA long-term;
  continuous temperature monitoring with alarming; backup power (generator + UPS); disaster
  plan (where do samples go if a freezer dies at 2 AM?). Map freezer contents — digging
  through boxes warms everything.
- **Aliquoting strategy.** Multiple small aliquots beat one large tube (freeze-thaw cycles
  degrade proteins, RNA, and many metabolites — typically limit to 1-2 cycles). Plan aliquot
  numbers from expected use cases, not convenience.
- **LIMS and barcoding.** Every sample barcoded at collection; chain of custody from bedside
  to freezer to distribution; 2D barcodes on tubes (human-readable labels fail in frost).
  The LIMS is the biobank's memory — paper logs don't scale and get lost.
- **Quality management.** QC program: periodic integrity testing (DNA/RNA integrity numbers,
  hemolysis checks), temperature log review, inventory audits, SOP version control, staff
  training records, non-conformance tracking. Accreditation (ISO 20387, CAP biorepository)
  formalizes this — pursue it for any serious biobank.
- **Governance and sharing.** Access committee (scientific + ethics review of requests),
  MTAs/DTAs for transfers, cost-recovery pricing (biobanks hemorrhage money giving samples
  away free), publication/acknowledgment policies, and benefit-sharing where applicable.

## Practical workflow

1. **Govern.** Ethics approval, consent forms, governance structure, legal review (data
   protection, human-tissue legislation).
2. **Write SOPs.** Collection, processing, aliquoting, freezing, shipping — versioned,
   trained, audited.
3. **Set up infrastructure.** Freezers with monitoring + backup power, LN2 supply, barcoding,
   LIMS configured before the first sample.
4. **Collect.** Trained staff, SPREC documentation, pre-analytical times recorded, chain of
   custody unbroken.
5. **Store.** Mapped locations, aliquot strategy, temperature monitoring with escalation.
6. **QC.** Periodic integrity testing, audits, non-conformance handling.
7. **Share.** Access committee review, MTAs, cost recovery, distribution tracking.

## Common pitfalls

- Consent that doesn't cover actual future uses (re-consent nightmares).
- Pre-analytical variables unrecorded (samples of unknown quality).
- Single large aliquots guaranteeing freeze-thaw damage.
- No temperature alarming (discovering freezer failure Monday morning).
- Paper-based tracking that collapses at scale.
- Free distribution bankrupting the biobank.
- No disaster plan (it's a matter of when, not if).
- Withdrawal requests with no defined process for already-distributed samples.

Attribution

aicodedecodeaicodedecode
View sourceSee grades on GitHubMore from aicodedecode →
SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments (0)

No comments yet. Be the first to comment!

SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Related Skills

Caveman

Terse caveman voice: answer first, fluff gone, every technical fact kept. Use for /caveman, "caveman mode", "talk like caveman", "be brief", "less tokens". Stays on until "stop caveman" or "normal mode".

1100021 votes

Hyperplan

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', ...

698621 votes

Writing Skills

Create and manage Claude Code skills in HASH repository following Anthropic best practices. Use when creating new skills, modifying skill-rules.json, understanding trigger patterns, working with hooks, debugging skill activation, or implementing progressive disclosure. Covers skill structure, YAML frontmatter, trigger types (keywords, intent patterns), UserPromptSubmit hook, and the 500-line rule. Includes validation and debugging with SKILL_DEBUG. Examples include rust-error-stack, cargo-dep...

3931 votes

Mcp Code Execution

Routes multi-tool workflows through MCP servers for large datasets and pipelines. Use when Bash tool overhead is limiting throughput on data-heavy tasks.

3421 votes

catchup

Recovers the conversation and failed tool calls of a previous Codex, Amp, Claude Code, Antigravity, Cline, Copilot CLI, Cursor, DeepSeek Harness, Grok Build, Kimi, OpenCode, Pi Agent, or ZCode session. Use when the user says "catch up", "what did the last session do", "get me up to speed", "I switched agents", asks to recover/summarize a previous session before continuing, or asks to diagnose or report a catchup failure. Do NOT use for the current conversation, git history, or any non-agent log.

741 votes
View all in ai-agents →