scientific eda

Data Community

Skill notes

Usage

Use this skill when the user provides one or more data files (CSV, FASTA, or other scientific formats) and wants to explore or analyze them. Start by capturing context—do not load or plot data until the problem (biological, chemical, or data-science question) is clearly stated and the agent is aligned as a guided assistant.

Requirements

uv for running Python scripts: every script uses PEP723 inline script metadata and is run with uv run script.py. Do not run ad-hoc Python or raw interpreters; each script declares and manages its own dependencies. Ability to read the relevant data formats (pandas, BioPython, etc.) via dependencies declared in the script block.

What It Does

Context first – Capture and record the problem context (what question, what domain) before touching the data. Single first step – Help the user narrow to one first plot or one first summary (not a barrage of code or plots). Human-guided execution – Take instruction on what to do next; when the user says "make this plot" or "give me that table," ask why before doing it, then execute. Session layout – Each analysis is a session: one folder under analysis/ with a descriptive name and start date/time, containing journal.md, plots/, and scripts/.

Phase 1: Capture context (before touching data)

Do not open the data file and start coding or plotting. Ask for or confirm: the problem context—biological, chemical, or data-science question; what the user hopes to learn or decide; and any constraints (e.g. specific variables, subsets). Record this in the session’s journal.md (see Phase 3). Only after context is recorded and agreed, proceed to inspect data shape and plan the first step.

Phase 2: Start a data analysis session

Create one session folder under analysis/ (or a project-agreed base). Name it descriptive + ISO datetime at session start, e.g. analysis/2025-02-05T14-30-00-protein-binding/. Canonical layout for each session folder: journal.md – append-only running journal for this session plots/ – all figures (WebP only for matplotlib) scripts/ – disposable scripts that load data, summarize, or make plots

Fluxly profile Runtime and permissions are inferred by Fluxly static checks, not author declarations or runtime test results.
Domain
Data
Author-declared agents
No explicit declaration found; this is not inferred or tested compatibility
Static check
94 / 100 · heuristic scan, not runtime safety proof
Runtime evidence
Not run; no isolated runtime test evidence is currently recorded
Author / version / license
@ericmjl · MIT
Token usage
Lean
Setup complexity
Guided setup
External API key
Not required
Operating systems
Unspecified (assume cross-platform)
Runtime requirements
Python
Detected file/system behavior
  • Read-only
  • Write / modify
  • Shell exec
Network behavior
Local-only
Install commands
None (reference only)

Heads up: Tool permissions are not declared; actual access depends on the runtime.

01
Phase 1: Capture context (before touching data)

Do not open the data file and start coding or plotting. Ask for or confirm: the problem context—biological, chemical, or data-science question; what the user hopes to learn or decide; and any constraints (e.g. specific variables, subsets). Record this in the session’s `journal.md` (see Phase 3). Only after context is recorded and agreed, proceed to inspect data shape and plan the first step.

02
Phase 2: Start a data analysis session

Create one session folder under `analysis/` (or a project-agreed base). Name it descriptive + ISO datetime at session start, e.g. `analysis/2025-02-05T14-30-00-protein-binding/`. Canonical layout for each session folder: `journal.md` – append-only running journal for this session `plots/` – all figures (WebP only for matplotlib) `scripts/` – disposable scripts that load data, summarize, or make plots

03
Phase 3: Journal (append-only, per session)

Before each substantive action, read the session’s `journal.md`. Record in the journal: Data shape: after loading or inspecting the data, jot columns (and types if relevant), row count, and any structure (e.g. multi-index, FASTA count, key fields). Do this as soon as shape is known and after any major data step. What was done (which script, which plot, which summary) Findings, surprises, and follow-up ideas

04
Phase 4: Understand shape, then one first step

Shape of the data: Before proposing or making plots, ensure the agent (and user) knows: what columns/fields exist, how many rows/records, and any critical structure. Record this in `journal.md` under a `[SHAPE]` entry. Single first plot (or table): Help the user choose one first visualization or summary (e.g. one distribution, one overview table). Do not generate many plots at once; get alignment on that single step, then execute.

05
Phase 5: Human-guided execution and "ask why"

Take instruction: The user may ask for a specific plot, table, or filter. Execute only after clarity. Ask why before doing: When the user says "make this plot" or "give me that table," briefly ask why (e.g. what decision or question it supports). Then run the script and record the outcome in the journal. After each action: Suggest the most logical next step (one step), and let the user confirm or redirect. Do not auto-execute a long pipeline.

06
Phase 6: Scripts (disposable, PEP723, uv run)

All Python used for this EDA lives in scripts under the session’s `scripts/` folder. Every script has PEP723 inline script metadata at the top (`# /// script`, `requires-python`, `dependencies`, `# ///`). Run with `uv run script.py` (or `uv run scripts/script_name.py` with CWD = session folder). Do not run raw `python` or paste code in a REPL; the script is the unit of execution and owns its environment.

07
Phase 7: Plots (WebP only for matplotlib)

Save all matplotlib (and similar) figures as WebP, not PNG, to keep image sizes small. Use e.g. `fig.savefig("plots/overview.webp", format="webp")`. Write plot files into the session’s `plots/` directory. Name files descriptively (e.g. `distribution_response.webp`, `first_ten_records.webp`). Reference these plots in the journal when you record what was done.

Discussion

Powered by GitHub Discussions. Sign in with GitHub to comment, react, or subscribe.