Content
68%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.
Highly actionable with executable code throughout and a well-structured bundle, but the body is over-long for an overview and the destructive QC/filtering workflow lacks explicit validation checkpoints. Tightening redundant summary sections and adding verify-after-filter steps would lift both weak dimensions.
Suggestions
Add explicit validation checkpoints after destructive filtering (e.g., 'Verify adata.n_obs and re-check QC violin plots before proceeding; adjust thresholds and re-filter if needed') to satisfy the workflow_clarity validation requirement.
Collapse the redundant 'Common Pitfalls and Best Practices' and 'Tips for Effective Analysis' sections into the relevant workflow steps or move them into references/standard_workflow.md to reduce overlap and token cost.
Trim the inlined full-workflow code in SKILL.md to a concise quick-start and delegate the complete step-by-step to references/standard_workflow.md to better realize the progressive-disclosure overview pattern.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The ~375-line body is mostly actionable code rather than concept fluff, but redundant summary sections ('Common Pitfalls and Best Practices', 'Tips for Effective Analysis', and 'Bundled Resources' re-describing each reference) overlap content already covered earlier, so it could be tightened. | 3 / 5 |
Actionability | Provides copy-paste executable code for every pipeline stage (loading, QC, normalization, PCA/UMAP, clustering, markers, annotation, plotting, trajectory, DE, scoring, batch correction) plus concrete CLI invocations for the bundled QC script, matching the fully-executable anchor. | 5 / 5 |
Workflow Clarity | The Standard Analysis Workflow is a clearly numbered 7-step sequence, but destructive/batch filtering operations (filter_cells, filter_genes, high-MT% removal) lack explicit validate→fix→retry checkpoints, triggering the cap-at-3 rule for destructive operations without validation. | 3 / 5 |
Progressive Disclosure | Real one-level-deep bundle files (api_reference.md, plotting_guide.md, standard_workflow.md, qc_analysis.py, analysis_template.py) are present and clearly signaled with 'Read this reference when…' guidance, but the body inlines a full workflow that overlaps standard_workflow.md, leaving a minor organization gap short of a clean overview. | 4 / 5 |
Total | 15 / 20 Passed |