scientific-analysis

Runs open-ended calibration investigations that produce figures and evidence-cited analysis logs.

Updated Aug 28, 2026
One-click install
npx skills add https://github.com/jingtao-lbl/A2MC --skill scientific-analysis-jingtao-lbl
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: scientific-analysis
Source: https://github.com/jingtao-lbl/A2MC/tree/main/.claude/skills/scientific-analysis
Command: npx skills add https://github.com/jingtao-lbl/A2MC --skill scientific-analysis-jingtao-lbl

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Free-form scientific questions about model calibration ("is P uptake growth-limited?", "what caused the R2 to R4 change?") often get answered ad hoc, with unreproducible figures and uncited claims. This Skill codifies the investigation workflow so every exploratory analysis ends in a reproducible figure and a properly recorded ana_log. ## Core Features & Use Cases - Structured investigation workflow: Pose a falsifiable question, scope the exact ensemble/run data needed, compute the actual statistic (correlation, attribution, regression), and quote numbers rather than hand-waving. - Knowledge-base-first mechanism checks: Queries all five knowledge surfaces (codebase wiki, RAG vector index, knowledge graph, model-level and site-level adaptive memory) before confirming load-bearing claims in model source code. - Reproducible deliverables: Figures follow a round + axis-mode + case-count filename convention, and every quantitative claim in the ana_log cites its figure, statistic, or data file inline. - Use Case: Investigate whether a PFT's nutrient uptake is growth-limited or stoichiometric by pulling ensemble data with existing analysis tools, computing the correlation, rendering a manuscript figure, and writing an evidence-cited ana_log. ## Quick Start Ask the agent to investigate whether a specific model output is correlated with a given parameter or mechanism and produce a figure plus an ana_log for the current calibration round.

Frequently Asked Questions about scientific-analysis

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

FAQPage Schema
How do I investigate whether a model parameter controls an output?▼

Pose the question as a falsifiable statement, scope the round and ensemble data, then compute the actual statistic such as a correlation or attribution. Check the model's knowledge base first for mechanism context, confirm in source code, and record the result in an ana_log with cited evidence.

When should I use scientific-analysis instead of summarize-calibration-round?▼

Use scientific-analysis for free-form exploratory questions like mechanism attribution or cross-regime comparisons. Use summarize-calibration-round for the standardized single-round report and compare-calibration-rounds for cross-round figures.

What knowledge sources should I check before reading model source code?▼

Query all five surfaces: the codebase wiki, the RAG vector index, the knowledge graph, model-level adaptive memory, and site-level adaptive memory. Then confirm load-bearing claims at the cited file and line in the model source, since descriptions can be wrong.

Does this skill work with models other than FATES?▼

Yes, the workflow is model-agnostic and applies to any onboarded model such as EcoSIM, PFLOTRAN, or ATS. Each onboarded model has its own knowledge base directory, and only the per-PFT extraction helpers are FATES-specific.

Why must every quantitative claim in the ana_log cite a source?▼

Citations make the analysis reproducible and auditable, since figures are gitignored and the filename is the only durable pointer. A claim without a cited figure, statistic, or data file is treated as a red flag and must be sourced or softened.