CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

dnanexus-integration

DNAnexus cloud genomics platform. Build apps/applets, manage data (upload/download), dxpy Python SDK, run workflows, FASTQ/BAM/VCF, for genomics pipeline development and execution.

Quality

73%

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/dnanexus-integration/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

65%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 well-structured overview skill with strong progressive disclosure and mostly executable examples, weakened by redundant use-case listing, generic best-practice padding, and the absence of validation/error-recovery checkpoints in its batch and multi-step workflow patterns. Trimming the duplicated bullets and adding explicit failure-handling steps would move it into the top band.

Suggestions

Cut the per-section 'Common Use Cases' bullet lists (they duplicate 'When to Use This Skill') and the generic 10-item Best Practices list, keeping only DNAnexus-specific guidance.

Add an error-recovery checkpoint to the batch pattern, e.g. check each job's state after wait and re-launch or inspect logs on failure, so batch workflows are not capped at workflow clarity 3.

Replace the promotional K-Dense Web section (or move it out of the operational flow) — it is non-actionable for the task and consumes context.

DimensionReasoningScore

Conciseness

The body is mostly efficient lists and code, but padding is noticeable: each capability section repeats a three-bullet 'Common Use Cases' list that duplicates the 'When to Use This Skill' section, the 10-item 'Best Practices' list contains generic guidance Claude already knows ("Never hardcode credentials", "Use semantic versioning"), and the closing K-Dense Web promotion section adds no operational value. This fits 'mostly efficient but includes some unnecessary explanation or could be tightened' rather than the noticeably-verbose level 2, since there is little concept over-explanation.

3 / 5

Actionability

Concrete, largely executable guidance throughout: install/login commands (`uv pip install dxpy`, `dx login`, `dx --version`), copy-paste-ready upload/run/download, search-and-download, app creation, and batch examples using real dxpy APIs. It stops short of 5 because a few examples are illustrative rather than complete (the app example shells out to a nonexistent `quality_filter` tool, and IDs like "applet-xxxx" are unexplained placeholders).

4 / 5

Workflow Clarity

The numbered decision tree gives a clear routing sequence and the Quick Start examples show ordered steps, but there are no validation checkpoints or error-recovery loops anywhere. The batch-processing pattern (launch parallel jobs, `wait_on_done` for all) involves batch operations with no per-job failure handling, which per the guidelines caps workflow clarity at 3.

3 / 5

Progressive Disclosure

The body is a clear overview that consistently pushes detail to five one-level-deep references (app-development.md, data-operations.md, job-execution.md, python-sdk.md, configuration.md), each verified to exist and each signaled both from its capability section ('See references/x.md for:...') and again in a Resources section. Not a 4 because navigation is genuinely easy and the split is appropriate with no inline walls of reference material and no nested references.

5 / 5

Total

15

/

20

Passed

Description

70%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, well-keyed description for a clearly distinct platform skill that suffers from one structural flaw: it answers 'what' but never 'when'. Adding an explicit 'Use when...' trigger clause would lift completeness and likely overall quality to the top band.

Suggestions

Append an explicit trigger clause, e.g. "Use when working with DNAnexus, dxpy, dxapp.json, or when running genomics pipelines on the DNAnexus platform."

Convert tool/format fragments into actions where possible (e.g., "process FASTQ, BAM, and VCF files") so every phrase names a concrete capability.

Add common user phrasings such as "sequencing data" or file extensions (.fastq, .bam, .vcf) to round out trigger coverage.

DimensionReasoningScore

Specificity

The description lists several concrete actions — "Build apps/applets", "manage data (upload/download)", "run workflows" — plus the concrete dxpy SDK and FASTQ/BAM/VCF formats. It falls just short of a 5 because fragments like "dxpy Python SDK" and "FASTQ/BAM/VCF" name tools/formats rather than actions, leaving minor coverage gaps.

4 / 5

Completeness

The 'what' is clearly stated (build apps/applets, manage data, run workflows, dxpy SDK) but there is no 'Use when...' clause or equivalent explicit trigger guidance, which the guidelines cap at 3. It is not a 4 because the 'when' is entirely absent rather than merely implicit-and-improvable; it is not a 2 because the 'what' is concrete and multi-faceted.

3 / 5

Trigger Term Quality

Strong natural keywords users would say: "DNAnexus", "genomics", "apps/applets", "upload/download", "workflows", "dxpy", "FASTQ/BAM/VCF", "pipeline". A few natural variations are missing (e.g., ".bam/.fastq file extensions", "sequencing data", "bioinformatics"), so it fits the 'good keyword coverage; a few natural terms missing' anchor rather than the comprehensive one.

4 / 5

Distinctiveness Conflict Risk

DNAnexus is a clearly niche platform with distinct triggers ("DNAnexus", "dxpy", "apps/applets", "dxapp.json") and minimal conflict risk with other skills. Adjacent generic-genomics skills could overlap slightly, but the platform-specific vocabulary makes wrong-skill triggering very unlikely.

5 / 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/dnanexus-integration/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.