Skills DirectorySkills Directory
SkillsLearnSecurityCategoriesDocsCommunityBlog
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

Company

  • About
  • Community
  • Blog
  • API Docs
  • Advertise

2026 Skills Directory. All rights reserved.

ProTermsPrivacyRefunds
Back to skills

Cc Study Design

ASecurity

Use when designing or auditing the experimental plan for a Cancer Cell (Cell Press) study — orthogonal validation across in vitro, in vivo, and human tumor systems, with controls, replicates, power, randomization, and blinding. It plans design; it does not run statistics or write figures.

1,052 stars
0 votes
0 copies
1 views
Added 6/4/2026
ai-agentsgo

Works with

cli

Security Analysis

A100/100

Scanned 6/4/2026

Install to Claude Code

$npx -y skills add brycewang-stanford/Awesome-Journal-Skills --skill cc-study-design --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Cc Study Design?

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

Security grade badge for Cc Study Design
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/brycewang-stanford-cc-study-design/badge)](https://www.skillsdirectory.com/skills/brycewang-stanford-cc-study-design)

More formats (shields.io, HTML) on the badges page.

Download with Pro
Files
SKILL.md
---
name: cc-study-design
description: Use when designing or auditing the experimental plan for a Cancer Cell (Cell Press) study — orthogonal validation across in vitro, in vivo, and human tumor systems, with controls, replicates, power, randomization, and blinding. It plans design; it does not run statistics or write figures.
---

# Experimental Design (cc-study-design)

## When to trigger

- The mechanism rests on a single system (e.g., cell lines only)
- Reviewers will ask "is this true in vivo?" or "does it hold in patients?"
- Controls, replicates, or sample-size logic are unclear
- Planning mouse / PDX / organoid experiments and unsure about rigor elements

## Orthogonal validation ladder

Cancer Cell expects a mechanism corroborated across **independent, complementary systems**. Build the strongest ladder the biology allows:

| Layer | Systems | Role |
|-------|---------|------|
| In vitro | Cell lines (multiple, authenticated), primary cells, co-cultures, biochemistry | Establish mechanism, gain/loss-of-function, epistasis |
| Functional genetics | CRISPR KO/KI, shRNA/siRNA with rescue, point mutants, degrons | Causality and specificity |
| In vivo | GEMM, syngeneic, xenograft, **PDX**, orthotopic, metastasis models | Mechanism operates in a tumor in an organism |
| 3D / ex vivo | Tumor **organoids**, patient-derived organoids, slice cultures, spheroids | Bridge to human, drug response |
| Human | Patient tumor samples, TMAs, scRNA-seq, public cohorts (TCGA), outcome data | Translational anchor / clinical relevance |

A Cancer Cell paper typically spans in vitro + in vivo + a human anchor. Decide early which layers carry the **causal** claim and which provide corroboration.

## Controls (the parts reviewers attack)

- **Genetic perturbation:** include rescue / add-back; use ≥2 independent sgRNAs or shRNAs (or rule out off-target); non-targeting / scramble control matched to delivery.
- **Pharmacology:** vehicle control, dose-response, on-target genetic phenocopy, and where possible a resistant mutant or analog.
- **In vivo:** isotype/vehicle controls, littermate or co-housed controls for GEMMs, tumor-volume and endpoint pre-defined.
- **Antibody / staining:** isotype, KO/KD-validated, single-stain compensation for flow.

## Replicates: biological vs technical

- **Biological replicates** = independent biological units (separate mice, independent cell passages/cultures, distinct patients). These define `n`.
- **Technical replicates** (duplicate wells, repeat measurements) reduce measurement noise but **do not** increase `n`.
- Report both clearly; never inflate `n` with technical replicates (see `cc-statistics`).

## Sample size, randomization, blinding (especially animals)

- **Power / sample size:** justify mouse `n` (effect size + variance from pilot or literature); state the basis even if informal.
- **Randomization:** allocate animals to arms randomly (e.g., when tumors reach a set volume), not by cage convenience.
- **Blinding:** blind outcome assessment (tumor measurement, histology scoring, imaging quantification) wherever feasible.
- **Inclusion/exclusion:** pre-define humane endpoints and exclusion criteria; report all animals/samples and any exclusions.

## Human-sample design

- Define cohort, inclusion/exclusion, and how samples link to outcomes.
- Power survival / association analyses; pre-specify primary comparison.
- Note IRB/consent (route to `cc-ethics-registration`).

## Checklist

- [ ] Mechanism validated across ≥2 orthogonal systems; causal layer identified
- [ ] In vivo evidence present (GEMM / xenograft / PDX / orthotopic) where claims require it
- [ ] Genetic perturbations include rescue and ≥2 independent reagents
- [ ] Matched controls defined for every perturbation and treatment
- [ ] Biological vs technical replicates distinguished; `n` = biological units
- [ ] Animal sample size justified; randomization and blinding specified
- [ ] Inclusion/exclusion criteria and humane endpoints pre-defined
- [ ] Human-sample cohort and primary comparison pre-specified

## Anti-patterns

- Conclusions from a single cell line or a single system
- shRNA/CRISPR phenotype with no rescue (off-target not excluded)
- "n=3" that is three wells of one experiment (pseudo-replication)
- Mouse experiments with no randomization, no blinding, no power basis
- Therapeutic efficacy claimed without an in vivo tumor model
- Selecting samples post hoc to fit the hypothesis

## Output format

```
【Causal claim layer】in vitro / in vivo / human
【Orthogonal systems planned】...
【Controls per perturbation】rescue + 2 reagents? vehicle/isotype?
【Replicates】biological n = ... ; technical handled separately
【Animal rigor】power basis / randomization / blinding / endpoints
【Human anchor】cohort + primary comparison
【Gaps to close before submission】...
【Next step】cc-reporting-standards (rigor reporting) or cc-statistics
```

Attribution

brycewang-stanfordbrycewang-stanford
View sourceMore from brycewang-stanford →
SSkills DirectorySkills Directory

Know which skills are safe — weekly.

Best new skills + every skill we flagged as malicious. From the team that scanned 103,619.

Join free

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

Know which skills are safe — weekly.

Best new skills + every skill we flagged as malicious. From the team that scanned 103,619.

Join free

Related Skills

Caveman

Ultra-compressed communication mode that cuts output tokens while keeping technical accuracy. Levels: lite, full, ultra and the wenyan variants. Use for /caveman, "caveman mode", "talk like caveman", "be brief" or "less tokens".

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

693161 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.

3351 votes

catchup

Recovers the conversation and failed tool calls of a previous Codex, Claude Code, Antigravity, Cline, Copilot CLI, Cursor, DeepSeek Harness, 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.

691 votes

math-skill

A comprehensive mathematical reasoning skill for AI assistants — handles arithmetic to research-level problems with rigorous step-by-step reasoning, systematic verification, and transparent uncertainty handling

381 votes
View all in ai-agents →