CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

tooluniverse-data-wrangling

Universal data access patterns for downloading and parsing scientific data when ToolUniverse tools don't cover the source, only return metadata, or you need bulk records. Use for VCF/h5ad/BAM/SDF/GCT parsing, multi-step API workflows (search to filter to download to parse), thousands of records at once, or sources with no dedicated tool. Write Python code via Bash for every step.

Quality

93%

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

The canonical home for this skill is tooluniverse-data-wrangling in mims-harvard/ToolUniverse

SKILL.md
Quality
Evals
Security

Quality

Content

90%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 excellent reference-style skill: dense, executable code with real endpoints and non-obvious operational knowledge (pagination cursors, rate-limit retries, HTML error-page guards), a clear tool-vs-code decision table, and a well-signaled one-level-deep reference file for specialized domains. The main improvement opportunities are a marginally long main body and the absence of one fully worked, checkpoint-validated end-to-end workflow.

DimensionReasoningScore

Conciseness

The body is lean code-first reference material: every block carries non-obvious domain knowledge ("# VCF (no cyvcf2 needed)", "# Guard against HTML error pages (CDC, NCBI return 200 with HTML for missing files)", batch sizes, cursor-pagination details) with no explanations of concepts Claude already knows. It matches the 'every token earns its place' anchor; there is no padded prose to trim for score 4's 'minor instances'.

5 / 5

Actionability

All guidance is fully executable, copy-paste-ready Python with real endpoints and parameters: the NCBI esearch→efetch batching loop, UniProt cursor pagination via the Link header, the GDC filters JSON POST, the GTEx gct.gz URL, and the retry/backoff helper. It matches the anchor for executable code covering common cases; it is not score 4 because no example is pseudocode or missing key details.

5 / 5

Workflow Clarity

Sequencing is present and validated — the "Decision: Tool vs Code" table, the named "search -> filter -> download -> parse" workflow, an end-to-end exemplar (NCBI esearch → idlist → batched efetch), and Section D error handling (status-code checks, HTML error-page guard, JSON decode) provide checkpoints, so the batch-operation cap does not apply. It falls short of anchor 5 because there is no single explicit numbered workflow with validate-and-recover checkpoints at each stage; it sits noticeably above anchor 3 since validation patterns are concretely shown.

4 / 5

Progressive Disclosure

The 14 specialized domains are correctly split into references/specialized-domains.md (verified to exist), referenced one level deep and clearly signaled by a table with a "When to Read" column. It falls short of anchor 5 because the main body is ~390 lines and sections like the 14-row restricted-sources table and the full format cookbook could arguably be split out as well — good structure with minor organization gaps, matching anchor 4 rather than a pure overview.

4 / 5

Total

18

/

20

Passed

Description

92%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 strong description: it states concrete capabilities with named scientific formats, gives an explicit 'Use for' trigger list, and defines a distinct niche as the fallback when ToolUniverse tools are insufficient. The only minor gap is trigger-term breadth — a few natural database-name and format keywords are absent. Voice is appropriately third-person/imperative throughout.

DimensionReasoningScore

Specificity

Names multiple concrete actions with specific formats — "downloading and parsing scientific data", "VCF/h5ad/BAM/SDF/GCT parsing", "multi-step API workflows (search to filter to download to parse)", and "Write Python code via Bash for every step" — covering the what, the formats, and the execution method. This matches the anchor for multiple specific concrete actions with comprehensive coverage; score 4 would require minor gaps, but no capability area is left unnamed.

5 / 5

Completeness

Explicitly answers both questions: what it does ("Universal data access patterns for downloading and parsing scientific data... Write Python code via Bash for every step") and when to use it ("Use for VCF/h5ad/BAM/SDF/GCT parsing... thousands of records at once, or sources with no dedicated tool"). This matches the anchor for clearly and explicitly answering both with concrete trigger phrases; it is not score 4 because the 'when' clause is already fully explicit.

5 / 5

Trigger Term Quality

Includes natural terms users would say: "VCF/h5ad/BAM/SDF/GCT", "bulk records", "thousands of records", "multi-step API workflows", and "only return metadata". Coverage is good but a few natural triggers are missing — no individual database names (TCGA, GEO, UniProt, NHANES) and no other common formats (FASTA, CSV) — so it sits between anchor 4 and 5, closer to 4.

4 / 5

Distinctiveness Conflict Risk

The trigger "when ToolUniverse tools don't cover the source, only return metadata, or you need bulk records" carves out a clear niche with minimal overlap risk. It is not score 4 because the triggers are conditional on a specific ecosystem (ToolUniverse) and specific formats, making conflict with generic data or document skills unlikely.

5 / 5

Total

19

/

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

mims-harvard/ToolUniverse

Path

plugins/tooluniverse/skills/tooluniverse-data-wrangling/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.