analyze

Run convention-aware computational analyses with registered datasets, linting, and reproducible pipelines.

68|2|Updated Feb 25, 2026
One-click install
npx skills add https://github.com/arjunrajlaboratory/mycelium --skill analyze-arjunrajlaboratory
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: analyze
Source: https://github.com/arjunrajlaboratory/mycelium/tree/main/skills/analyze
Command: npx skills add https://github.com/arjunrajlaboratory/mycelium --skill analyze-arjunrajlaboratory

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires scilintr, marimo.

What problem does it solve? Analytical work often loses its context: decisions, conventions, and validation steps are forgotten between sessions, leading to irreproducible results and silent statistical errors. This Skill structures every analysis around registered manifests, installed conventions, and mandatory linting so results stay reproducible and auditable. ## Core Features & Use Cases - Convention-routed analysis: Reads project manifests and installed convention packs (robust-analysis, bioinformatics, image-analysis) to apply the correct methodology for clustering, PCA/UMAP, differential expression, survival models, and statistical tests. - Reproducible execution standards: Enforces marimo for exploration, plain Python scripts for pipelines, and a run.sh or run.py entry point that regenerates final outputs. - Static analysis linting: Runs scilintr after every code change to flag silent scientific commitments such as unseeded RNGs, unchecked joins, and magic thresholds, with a structured waiver mechanism. - Use Case: A researcher continuing an RNA-seq differential expression analysis opens the project, and the Skill loads prior decisions from the manifest, applies the installed bioinformatics conventions, registers reportable values, and lints the new code before completion. ## Quick Start Use the analyze skill to run a differential expression analysis on the registered RNA-seq dataset following this project's installed conventions.

Frequently Asked Questions about analyze

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run a reproducible data analysis with registered conventions?

Start by reading the analysis, data, and algorithm manifests, then create or continue an analysis directory with documentation, scripts, outputs, and reports. The Skill routes execution through installed convention packs and requires a run.sh or run.py that reproduces final outputs.

What is scilintr and how do I lint analysis code with it?

scilintr is a static analyzer that flags silent scientific commitments like broad except blocks, unchecked joins, magic thresholds, and unseeded RNGs. Install it via pip or CRAN, run it after every code edit, and drive findings to zero by fixing patterns or adding structured ANALYSIS_OK waivers.

Can I continue an existing analysis instead of starting a new one?

Yes. Navigate to the existing analysis folder and read its UPPER_SNAKE_CASE documentation file to resume with full context. New analyses that build on a parent record the lineage in the analysis manifest entry.

When should I not use this analysis skill?

Do not use it for merely previewing data, ingesting files, writing reports, brainstorming, repository setup, or unrelated code fixes. It is scoped to executing and debugging computational analyses within the project's convention framework.

How do convention packs like robust-analysis affect my analysis?

When robust-analysis is installed, its conventions become the non-negotiable primary execution guide, covering strict execution, validation checks, sensitivity sweeps, and null hypothesis testing. Domain packs like bioinformatics layer on top, with repo-local conventions taking highest precedence.