CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

exploratory-data-analysis

Perform comprehensive exploratory data analysis on scientific data files across 200+ file formats. This skill should be used when analyzing any scientific data file to understand its structure, content, quality, and characteristics. Automatically detects file type and generates detailed markdown reports with format-specific analysis, quality metrics, and downstream analysis recommendations. Covers chemistry, bioinformatics, microscopy, spectroscopy, proteomics, metabolomics, and general scientific data formats.

Quality

77%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./scientific-skills/exploratory-data-analysis/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

71%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.

Well-structured and highly actionable content with excellent progressive disclosure — the SKILL.md serves as an overview pointing to six verified one-level-deep reference files, a script, and a template. The main weakness is redundancy: the workflow and script usage are each repeated across multiple sections, inflating token cost without adding guidance.

Suggestions

Merge "Detailed Format References" and "Script Usage" into the main Workflow section — both currently restate steps already covered, saving ~40 lines of duplicated guidance.

Replace the Python-regex code block for searching reference files with a one-line grep command (e.g. grep -A 15 '^### .fastq' references/bioinformatics_genomics_formats.md); Claude already knows how to search a file.

Trim the worked examples to one full five-step walkthrough and make its analysis code actually executable rather than comment placeholders, or condense the other two to format-detection notes.

DimensionReasoningScore

Conciseness

The workflow is explained three times (Workflow, Detailed Format References, and Script Usage sections) and the three examples restate all five steps, the Python-regex snippet for searching a reference file is over-engineered where grep suffices, and the K-Dense Web promo paragraph is padding. However, it never explains concepts Claude already knows, keeping it above the noticeably-verbose anchor 2.

3 / 5

Actionability

Concrete executable guidance throughout — "python scripts/eda_analyzer.py <filepath> [output.md]", a defined report template path, specific per-datatype analysis lists, and an ImportError handling pattern — but the three worked examples use comment placeholders ("# Calculate: read count, length distribution...") rather than fully executable code, leaving minor gaps versus the copy-paste-ready anchor 5.

4 / 5

Workflow Clarity

A clear five-step sequence (detect → load reference info → analyze → generate report → save) with per-step outputs and a Troubleshooting section giving error-recovery paths for missing libraries, unknown types, and large files. There are no explicit validation checkpoints inside the sequence itself, which keeps it at anchor 4 rather than 5; the destructive/batch cap does not apply since this is read-only analysis.

4 / 5

Progressive Disclosure

The body is a genuine overview navigator: six category-scoped reference files (all verified present, one level deep, with the documented "### .ext" entry structure), each clearly signaled with its path and format count, plus a Resources section listing every bundle file. The script and report template exist and are referenced exactly as described, matching the well-signaled one-level-deep anchor.

5 / 5

Total

16

/

20

Passed

Description

75%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 solid description that explicitly states both capabilities and use conditions with third-person voice and domain scoping. Its main weakness is genericness in the trigger clause — "any scientific data file" — with no concrete user phrases, synonyms, or file extensions that would sharpen both triggering and distinctiveness.

Suggestions

Add concrete trigger phrases to the when-clause, e.g. "Use when the user asks to explore, analyze, or summarize a scientific data file" — this would lift completeness and trigger term quality to anchor 5.

Name the concrete analytical actions (statistical summaries, missing-value and quality checks, per-format metadata extraction) instead of the abstract "comprehensive exploratory data analysis".

Include a few representative file extensions (.fastq, .csv, .mzML, .nd2) to improve natural-term coverage and reduce overlap with generic data-analysis skills.

DimensionReasoningScore

Specificity

The description lists several concrete actions — "Automatically detects file type and generates detailed markdown reports with format-specific analysis, quality metrics, and downstream analysis recommendations" — but "Perform comprehensive exploratory data analysis" is abstract and the underlying analyses (statistical summaries, structure inspection) are not named, so it falls short of the comprehensive coverage of the anchor 5 example.

4 / 5

Completeness

Both what ("Automatically detects file type and generates detailed markdown reports...") and when ("This skill should be used when analyzing any scientific data file...") are explicitly present, but the when-clause is generic ("any scientific data file") without the concrete trigger phrases (user verbs, file mentions) that distinguish anchor 5.

4 / 5

Trigger Term Quality

Natural phrases like "exploratory data analysis", "analyzing any scientific data file", and "structure, content, quality, and characteristics" give good keyword coverage, but common synonyms ("explore", "summarize", "EDA") and file extensions (.fastq, .csv, .mzML) are missing, matching the "a few natural terms missing" anchor rather than the comprehensive one.

4 / 5

Distinctiveness Conflict Risk

The scope is anchored to scientific data across seven named domains (chemistry, bioinformatics, microscopy, spectroscopy, proteomics, metabolomics, general), making it mostly distinct; however "analyzing any scientific data file" is broad enough to overlap with general data-analysis skills, fitting anchor 4 rather than the clear-niche anchor 5.

4 / 5

Total

16

/

20

Passed

Validation

93%

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

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository

googolme/run0204

Path

scientific-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.