一键导入
sdrf-design
Use when the user wants to analyze the experimental design encoded in an SDRF file, check for batch effects, confounders, or replication issues.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
菜单
Use when the user wants to analyze the experimental design encoded in an SDRF file, check for batch effects, confounders, or replication issues.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Independently falsify and review a created, modified, or proposed SDRF against its specification, ontology terms, source evidence, repository files, and experimental design. Use after SDRF annotation or repair, before contribution or completion, when a review gate reports a pending artifact, or whenever an isolated reviewer must distrust the producer's self-assessment and issue a hash-bound verdict.
Create or improve an SDRF through a producer-reviewer workflow with deterministic validation, an evidence manifest, fresh-context adversarial review, repair, and mandatory re-review. Use when an SDRF must be independently verified before completion or contribution, when the user requests adversarial review, or when automated review hooks require a passing hash-bound receipt.
Use when the user wants SDRF annotation to run as an autonomous retained-improvement loop over one dataset, a manifest, or a dataset class such as all PRIDE cell line or crosslinking datasets.
Use when the user has a completed SDRF annotation for a ProteomeXchange dataset and wants to contribute it back to the community via a PR to sdrf-annotated-datasets.
Use when the user wants a comprehensive quality review of an SDRF file, a PR review of an SDRF submission, or a quality score assessment.
Use before sdrf:autoresearch when the user needs to screen or shortlist proteomics studies from PRIDE, MassIVE, ProteomeXchange accessions, or a manifest using detailed user-defined inclusion/exclusion criteria; extract study-level metadata from repository records and publications; and write an evidence-backed TSV for downstream annotation, review, or meta-analysis.
| name | sdrf:design |
| description | Use when the user wants to analyze the experimental design encoded in an SDRF file, check for batch effects, confounders, or replication issues. |
| user-invocable | true |
| argument-hint | [file path or paste SDRF content] |
You are analyzing the experimental design captured in an SDRF file to detect statistical and methodological issues.
Extract from the SDRF:
Present a clear summary:
Experimental Design Summary:
Type: Two-group comparison
Factor: disease (breast carcinoma vs normal)
Group 1 "breast carcinoma": 10 biological replicates
Group 2 "normal": 10 biological replicates
Technical setup:
Label: TMT10plex (10 channels per plex)
Fractions: 12 per TMT set
Technical replicates: 1 per sample
Instrument: Q Exactive HF
File math:
2 TMT sets × 12 fractions = 24 raw files
Each file → 10 rows (one per TMT channel)
Total SDRF rows: 240
Statistical power:
n=10 per group — adequate for detecting medium effect sizes
Cross-tabulate factor values against technical variables:
Check: Is "condition" confounded with "instrument"?
Cross-tab factor value × comment[instrument]
BAD: All "disease" on Instrument A, all "control" on Instrument B
→ Cannot separate biology from instrument effect
GOOD: Both conditions measured on both instruments (balanced)
Check: Are conditions balanced across TMT sets/channels?
Cross-tab factor value × TMT set × channel position
BAD: All disease in TMT set 1, all control in TMT set 2
→ TMT set is confounded with condition
GOOD: Each TMT set contains both disease and control samples
Check: Were conditions processed at different times?
If file names contain dates → check if conditions cluster by date
BAD: All disease samples processed Monday, all controls Friday
GOOD: Randomized processing order
Check independence of factor values from other characteristics:
For each characteristics column × factor value:
If perfectly or strongly correlated → FLAG
Examples:
⚠ All female samples are disease, all male are control → sex confounds disease
⚠ All young (20-30Y) are treatment, all old (60-70Y) are control → age confounds treatment
⚠ All HeLa are condition A, all MCF7 are condition B → cell line IS the condition (expected)
Use a simple contingency analysis:
Biological replicates per condition:
n=1: ⚠ CRITICAL — No statistical testing possible
n=2: ⚠ WARNING — Very low power, only extreme effects detectable
n=3: ⚠ CAUTION — Minimum for basic statistics, low power
n≥5: ✓ Acceptable for many proteomics analyses
n≥10: ✓ Good statistical power
Technical replicates:
0: Common for TMT (label channels serve as tech reps)
1: Standard for label-free (one injection per sample)
2+: Used for quality assessment or when variability is high
Based on the factor values, suggest:
characteristics[individual] IDs match across conditions)Example for disease (breast carcinoma vs normal):
comparison <- matrix(c(-1, 1), nrow=1)
colnames(comparison) <- c("normal", "breast carcinoma")
rownames(comparison) <- c("breast_carcinoma_vs_normal")
Example for multi-group (A vs B, A vs C):
comparison <- matrix(c(-1,1,0, -1,0,1), nrow=2, byrow=TRUE)
colnames(comparison) <- c("groupA", "groupB", "groupC")
rownames(comparison) <- c("B_vs_A", "C_vs_A")
Present findings as an actionable report:
# Experimental Design Analysis
## Summary
[design summary from Step 2]
## Issues Found
### 🔴 Critical
[perfect confounds, n=1 replication]
### 🟡 Warnings
[partial confounds, low replication, unbalanced TMT]
### 🟢 Good
[balanced design aspects, adequate replication]
## Recommendations
1. [specific actionable recommendations]
2. [suggested changes to SDRF or experimental design]