CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

exploratory-data-analysis

Performs bounded, local exploratory analysis of explicitly supported scientific files. Supports redacted CSV/TSV/JSON profiles; optional NumPy, HDF5, FASTA/FASTQ, and basic image metadata inspection; missingness/leakage audits; outlier and transformation sensitivity; and rigorous EDA report scaffolds. Other domain formats are reference-only and unknown formats fail closed.

Quality

83%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

86%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

An exceptionally well-engineered skill body: copy-paste-ready CLI examples at every step, an explicit capability matrix with fail-closed routing, validation gates in the workflow, and a properly structured one-level-deep reference bundle that was verified to exist. The only meaningful weaknesses are minor token overhead from the dated version-pin and citation sections and the lack of an explicit error-recovery loop in the workflow.

DimensionReasoningScore

Conciseness

The body consistently assumes Claude's competence — no basic concept is explained; every section is dense task-specific policy (capability matrix, I/O contract, 10 EDA rules, output-interpretation caveats). Minor trimmable spots remain: the dated version-pin table and the multi-paragraph citation instructions are time-sensitive content outside any 'old patterns'/'deprecated' section. Fits anchor 4 (efficient, minor instances that could be trimmed) — not anchor 5 given those sections, and clearly above anchor 3 since nothing teaches Claude what it already knows.

4 / 5

Actionability

Every workflow step is backed by copy-paste-ready commands with concrete flags: `python scripts/capability_manifest.py inspect data.csv --root /approved/project --output data.manifest.json`, `eda_analyzer.py ... --max-rows 100000`, `missingness_leakage_audit.py ... --group-column condition`, through `report_scaffold.py --analysis-date 2026-09-30`. The examples cover the common cases across the automated tiers, matching anchor 5 (fully executable, copy-paste ready, common cases covered).

5 / 5

Workflow Clarity

The five-step workflow (confirm authorization → manifest before content → run narrowest tool → add scientific context → create report) is clearly sequenced with explicit validation checkpoints: step 1 stops on unclear authorization, step 2 gates on manifest status ("If status is reference_only, do not run eda_analyzer.py... If unknown, stop"), and the Output interpretation section acts as a result-verification checklist. It falls short of anchor 5 only in lacking an explicit error-recovery feedback loop (what to do when a command fails or output looks anomalous mid-run); it is well above anchor 3's implicit/missing checkpoints. The destructive/batch cap does not apply since the skill is read-only by design.

4 / 5

Progressive Disclosure

Verified against the actual bundle: all six `references/*.md` files, `assets/report_template.md`, and every invoked `scripts/*.py` exist; the body is a true overview (capability matrix, routing, workflow) with a well-signaled one-level-deep reference table plus the instruction "Read the one relevant format reference. Do not load every reference"; reference files link only to external sources, with no nested chains. This matches anchor 5 (clear overview, well-signaled one-level-deep references, easy navigation).

5 / 5

Total

18

/

20

Passed

Description

71%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A specific, third-person description that clearly states what the skill does across many named scientific formats, with good natural keywords and an explicit fail-closed boundary. Its main weakness is the complete absence of a 'Use when...' trigger clause, which caps completeness and weakens discoverability for users who ask in everyday terms.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user asks to explore, profile, summarize, or audit scientific data files (CSV, TSV, JSON, NumPy, HDF5, FASTA/FASTQ, microscopy images) before modeling or confirmatory analysis."

Include common natural synonyms and file extensions — "exploratory data analysis", "EDA", "data profiling", "data audit", ".csv", ".h5", ".fastq" — so the description matches how users actually phrase the request.

Trim evaluative filler ("rigorous", "bounded") in favor of one or two user-facing outcome phrases (e.g. "generates schema, missingness, and outlier reports") to keep every term a trigger or a capability.

DimensionReasoningScore

Specificity

Lists multiple concrete actions with comprehensive coverage: "redacted CSV/TSV/JSON profiles", "missingness/leakage audits", "outlier and transformation sensitivity", "EDA report scaffolds", plus named formats (NumPy, HDF5, FASTA/FASTQ, image metadata). Fits the anchor-5 example style (multiple specific concrete actions); anchor 4 would require noticeable coverage gaps, which are absent.

5 / 5

Completeness

The "what" is clear ("Performs bounded, local exploratory analysis of explicitly supported scientific files" plus enumerated capabilities), but there is no "Use when..." clause or equivalent explicit trigger guidance anywhere in the description — the 'when' is at best weakly implied by "exploratory analysis". Per the judging guideline, a missing 'Use when...' clause caps completeness at 3, and the clear-what/missing-when pattern is exactly anchor 3.

3 / 5

Trigger Term Quality

Good natural keyword coverage ("exploratory analysis", "EDA", "CSV", "TSV", "JSON", "HDF5", "FASTA/FASTQ", "outlier", "missingness") but a few natural terms users would say are missing — literal file extensions (.csv, .h5) and synonyms like "data profiling" or "explore my data". Matches anchor 4 (good coverage, a few natural terms missing) rather than anchor 5's comprehensive synonym/extension coverage.

4 / 5

Distinctiveness Conflict Risk

The scientific-EDA niche with distinctive terms (FASTA/FASTQ, HDF5, missingness/leakage audits) and an explicit boundary ("Other domain formats are reference-only and unknown formats fail closed") is mostly distinct with minor overlap risk — generic formats like "CSV/TSV/JSON" could also trigger a general tabular-data or spreadsheet skill. Fits anchor 4 (mostly distinct, minor overlap with closely related skills) rather than anchor 5's minimal conflict risk.

4 / 5

Total

16

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

K-Dense-AI/scientific-agent-skills

Path

skills/exploratory-data-analysis/SKILL.md

Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.