Content
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
A highly actionable, well-sequenced skill with strong executable code and validation for the risky QC step. It is held back by some discursive sections and a broken reference to a missing `analysis_patterns.md` file.
Suggestions
Create `references/analysis_patterns.md` (or fix the references to point at an existing file) — it is cited for 'Pattern 1'/'Pattern 2' DE and correlation workflows but is absent from the bundle.
Tighten or relocate the discursive prose: collapse the QC biology explanations, 'Core Principles', 'Reasoning Framework', and 'Synthesis Questions' into the leanest actionable form or move them to a reference file.
Move the large ToolUniverse Integration tool list and the Scanpy-vs-Seurat table into reference files (the latter already overlaps `seurat_workflow.md`) to keep SKILL.md an overview.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is largely lean executable code and tables, but several sections are discursive and could be tightened — the QC biology prose ('A ruptured membrane lets cytoplasmic mRNA leak out...'), 'Core Principles', the 'Reasoning Framework for Result Interpretation', and the 'Synthesis Questions' list add explanatory bulk beyond what is strictly actionable. | 2 / 3 |
Actionability | It provides abundant copy-paste-ready, executable code (data loading with orientation handling, QC metrics, the complete pipeline, statistical tests, Harmony batch correction) plus a concrete `tu run run_deseq2_analysis` command, fully meeting the executable-guidance anchor. | 3 / 3 |
Workflow Clarity | A decision tree sequences the workflows, and the destructive QC-filtering operation has explicit validation/feedback: the install-plan preflight gate ('if scanpy is not installed... stop'), 'Always visualize distributions first', and per-step removal reporting — satisfying the validation-checkpoint requirement for risky operations. | 3 / 3 |
Progressive Disclosure | References are one-level-deep and mostly real and well-signaled, but `analysis_patterns.md` is referenced three times (decision tree and Reference Documentation) yet does not exist in the bundle, and some inline content (the ToolUniverse Integration list, the Scanpy-vs-Seurat table duplicating `seurat_workflow.md`) could live in separate files. | 2 / 3 |
Total | 10 / 12 Passed |