CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

imaging-data-commons

Queries and downloads public cancer imaging data from NCI Imaging Data Commons. Supports IDC collection discovery, DICOM access, radiology (CT, MR, PET) and pathology AI datasets, metadata SQL, visualization, licensing, and citations. Uses public metadata and download routes without authentication; optional BigQuery and Google Healthcare routes require Google credentials.

Quality

90%

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

SKILL.md
Quality
Evals
Security

Quality

Content

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

A strong, highly actionable skill body: executable examples throughout, an explicit routing decision procedure with validation checkpoints, and exemplary progressive disclosure via a trigger-based navigation table. The only real weakness is repetition — the install-cost rationale and version-check guidance are each stated twice, keeping it just short of maximal token efficiency.

Suggestions

State the REST-vs-install cost rationale once (in Data Access Options) and have the Overview routing gate simply reference it, removing the duplicated ~77 MB / pandas / pyarrow / duckdb explanation.

Consolidate the repeated check_version.py guidance (Overview, MCP Server section, Best Practices, Troubleshooting) into a single canonical mention plus the routing gate, trimming near-duplicate sentences.

Tighten the longest multi-clause sentences (e.g., the REST row-cap and version-compatibility paragraphs) into shorter statements or table rows.

DimensionReasoningScore

Conciseness

The body is dense and high-value — join tables, argument-order gotchas, exact endpoints, licensing obligations — and avoids explaining concepts Claude already knows. However, the REST-vs-install rationale (the ~77 MB install cost) and the check_version.py guidance each appear in both Overview and Data Access Options, and several long multi-clause sentences could be tightened. This is "efficient with minor instances that could be trimmed" (4), not the lean every-token-earns-its-place level (5).

4 / 5

Actionability

Nearly everything is executable as written: complete SQL queries, a fully copy-paste-ready curl block for the REST path, a correct end-to-end download example that explicitly corrects the most common mistake (DataFrame vs UID list), exact method signatures, and concrete troubleshooting commands. The examples cover the common cases (query, download, visualize, license, cite, no-install metadata), matching the fully-executable 5 anchor rather than the minor-gaps 4.

5 / 5

Workflow Clarity

The core workflow is stated explicitly (query with sql_query → download_from_selection → get_viewer_URL) and the routing gate is a numbered decision procedure with a hard validation checkpoint ("A launch failure is not a pass"). Batch download operations carry safeguards — size checks, LIMIT-first testing, verify UIDs exist, resume/retry guidance — and the Troubleshooting section provides issue→cause→solution feedback loops, so the batch-operation cap does not apply.

5 / 5

Progressive Disclosure

The Quick Navigation table gives each of the 13 reference guides an explicit "When to Load" trigger, every inline references/*.md and scripts/check_version.py path resolves to a real bundled file, and the bulk detail (BigQuery, REST endpoints, pathology, clinical joins) lives in those one-level-deep guides rather than inline. This is a clear overview with well-signaled references and easy navigation.

5 / 5

Total

19

/

20

Passed

Description

82%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, distinctive, well-voiced description that clearly states what the skill does across its full capability range. Its one material weakness is the absence of any "Use when..." trigger guidance, which leaves the when-to-use question only weakly implied and caps completeness.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user mentions Imaging Data Commons, IDC, NCI cancer imaging data, or needs to download or query public DICOM datasets (CT, MR, PET, or slide microscopy)."

Optionally fold a compact when-to-use cue into the first sentence, such as "Use for finding and downloading public cancer imaging data from NCI Imaging Data Commons...", so the trigger survives even if later sentences are trimmed.

Consider mentioning "training datasets" or "AI/annotations datasets" as natural trigger phrases users searching for ML data would say.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions — "Queries and downloads public cancer imaging data", "collection discovery, DICOM access, radiology (CT, MR, PET) and pathology AI datasets, metadata SQL, visualization, licensing, and citations" — with comprehensive coverage and consistent third-person voice ("Queries", "Supports", "Uses"). This matches the 5 anchor (multiple specific concrete actions, comprehensive); a 4 would require minor coverage gaps, and none are evident.

5 / 5

Completeness

The "what" is clearly and specifically answered (querying, downloading, and the full capability list), but there is no "Use when..." clause or equivalent explicit trigger guidance — the authentication sentence describes boundaries, not when to reach for the skill. Per the judging guideline, a missing trigger clause caps completeness at 3.

3 / 5

Trigger Term Quality

It covers the domain's natural vocabulary comprehensively, including synonyms: both the full name "NCI Imaging Data Commons" and the acronym "IDC", plus "cancer imaging data", "DICOM", "CT, MR, PET", and "pathology". A 4 ("a few natural terms missing") would apply if an obvious user phrase were absent, but the terms a user needing this skill would actually say are all present.

5 / 5

Distinctiveness Conflict Risk

It occupies a clear niche (the NCI Imaging Data Commons platform) with distinct triggers — IDC, DICOM, cancer imaging data — that are unlikely to fire for any unrelated skill. This matches the 5 anchor (clear niche, distinct triggers, minimal conflict risk).

5 / 5

Total

18

/

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/imaging-data-commons/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.