Content
71%Weight 40%Scale 1-5Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
Strong, highly actionable content with excellent validated-quirk knowledge in the ToolUniverse catalog and unusually deep QC-gating guidance, weakened by a dangling `analysis_patterns.md` reference on the most common workflow path and by a few sections that re-teach standard scanpy/scipy knowledge. The hardcoded cutoffs in the quick-reference pipeline also sit in tension with the skill's own MAD-based thresholding mandate.
Suggestions
Create `analysis_patterns.md` (or repoint the three references to existing files like `references/marker_identification.md` and `references/scanpy_workflow.md`) so the 'Pattern 1' per-cell-type DE and 'Pattern 2' correlation navigation paths resolve.
Remove or trim the sections that re-teach knowledge Claude already has — the scipy statistical-tests quick reference, the Scanpy-vs-Seurat equivalents table, and the boilerplate 'Complete Pipeline' — or move them into an existing reference file.
Reconcile the 'Complete Pipeline (Quick Reference)' with the QC section by replacing the hardcoded `pct_counts_mt < 20` / `min_genes=200` filters with a pointer to `scripts/scrna_qc.py` MAD-based gating, so the quick reference cannot be copy-pasted in violation of the skill's own threshold guidance.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The high-value core (QC gating rationale, ToolUniverse catalog with live-verified parameter gotchas, RULE ZERO, analysis conventions) is dense and lean, but several sections re-teach material Claude already knows: the scipy 'Statistical Tests (Quick Reference)' (ttest_ind, f_oneway, pearsonr, multipletests), the 'Scanpy vs Seurat Equivalents' table, and the boilerplate 'Complete Pipeline' block. This matches 'mostly efficient but includes some unnecessary explanation' rather than score 2, since the padded material is a minority of the ~435 lines and the rest is reference-grade rather than prose-padded. | 3 / 5 |
Actionability | Code is copy-paste ready and covers the common cases: data loading with orientation check, QC metric computation, the full scanpy pipeline, Harmony batch correction, and a concrete `tu run run_deseq2_analysis '{...}'` command. Referenced script invocations are real and verified — `scripts/scrna_qc.py` exists and exposes both `--doublets` and the `--install-plan` flag, with the honest-execution fallback ('do NOT fabricate metrics — print the install plan and stop') making the failure path executable too. | 5 / 5 |
Workflow Clarity | A clear sequence exists (RULE ZERO pre-flight check → workflow decision tree → 'QC ... do this BEFORE downstream analysis' → DE decision tree), with real checkpoints: 'Always visualize distributions first', 'never report cutoffs you did not actually run', per-step removal reporting, the QC interpretation table, and a troubleshooting error-recovery table. It falls short of 5 because the 'Complete Pipeline (Quick Reference)' reuses hardcoded cutoffs (`pct_counts_mt < 20`, `min_genes=200`) that the QC section explicitly warns are 'a starting point only' — an internal tension that could lead Claude to skip the MAD-based gating the skill mandates. | 4 / 5 |
Progressive Disclosure | The 8 reference files are well documented with one-line descriptions in 'Reference Documentation' and are one level deep, but `analysis_patterns.md` is referenced three times — including as the guide for 'Pattern 1' (per-cell-type DE, described as the most common pattern) and 'Pattern 2' (correlation) — and does not exist anywhere in the bundle. A primary navigation path pointing to a missing file is a structural failure beyond the 'minor organization gaps' of score 4, landing at 'some structure but could be better organized'. | 3 / 5 |
Total | 15 / 20 Passed |