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, process FASTQ/BAM/VCF, for developing and executing genomics pipelines.

Quality

68%

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

Quality

Content

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

The substantive DNAnexus half of the body is well structured with executable examples and a clean, verifiable reference bundle. However, generic template boilerplate, duplicate sections, and promotional content roughly double the token cost without adding skill value, and batch workflows lack validation checkpoints.

Suggestions

Delete the template boilerplate sections ("Key Features", "Dependencies", "Example Usage", "Implementation Details") and merge the two "When to Use" sections into one.

Add a validation loop to the batch-processing pattern: check `job.describe()['state']` or catch `wait_on_done()` failures per job and report which jobs failed before downloading results.

Remove the "Suggesting K-Dense Web" promotional section and fix dangling references (e.g., "See `## Overview` above" pointing to a later section, undefined variables in Pattern 2).

DimensionReasoningScore

Conciseness

The body is noticeably padded: generic template boilerplate ("Scope-focused workflow aligned to...", "Structured execution path designed to keep outputs consistent and reviewable"), two overlapping "When to Use" sections, a filler "Example Usage" block containing only a directory listing, "Implementation Details" that points to a section that comes later in the document, best-practice platitudes Claude already knows ("Never hardcode credentials"), and a promotional section about K-Dense Web. The genuinely useful DNAnexus content could be roughly half the length.

2 / 5

Actionability

Mostly executable guidance: working dxpy snippets for upload/run/download, search, app entry points, and batch launching, plus concrete commands (`uv pip install dxpy`, `dx login`, `dx build`). Minor gaps remain — Pattern 2 references undefined variables (`qc_applet`, `align_applet`) and an unverified `get_output_ref()` API.

4 / 5

Workflow Clarity

The decision tree and quick-start flows give a clear sequence, but batch operations (Pattern 1 launches parallel jobs) include no validation or per-job error-handling loop, which caps workflow clarity at 3 per the rubric's batch-operations rule.

3 / 5

Progressive Disclosure

All five cited `references/*.md` files exist and are referenced one level deep with clear signals in both Core Capabilities and Resources. Minor gaps: the reference inventory is duplicated across two sections, and the boilerplate front half of the document buries the actual overview.

4 / 5

Total

13

/

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-scoped description with concrete capabilities and strong distinctiveness. Its main weakness is the absence of an explicit "Use when..." trigger clause, which both limits completeness and leaves triggering to inference.

Suggestions

Append an explicit trigger clause, e.g. "Use when working with the DNAnexus platform, the dx CLI, dxpy scripts, or when processing FASTQ/BAM/VCF data in the cloud."

Mention project management and the dx command-line toolkit to round out capability coverage.

Include common user phrasings such as "upload sequencing data" or "run an applet" to broaden natural trigger terms.

DimensionReasoningScore

Specificity

The description lists several concrete actions — "Build apps/applets, manage data (upload/download), dxpy Python SDK, run workflows, process FASTQ/BAM/VCF" — covering most platform capabilities. It falls just short of comprehensive coverage since project/permissions management and the dx CLI are not mentioned.

4 / 5

Completeness

The "what" is clear (build apps, manage data, use dxpy, run workflows, process genomics file formats), but there is no "Use when..." clause or equivalent explicit trigger guidance; "for developing and executing genomics pipelines" states purpose rather than triggering conditions, capping completeness at 3 per the judging guidelines.

3 / 5

Trigger Term Quality

Natural terms users would say include "DNAnexus", "apps/applets", "upload/download", "dxpy", "FASTQ/BAM/VCF", and "genomics pipelines". Coverage is good but a few natural phrasings (e.g., "upload files to DNAnexus", "dx toolkit") are missing, so it fits between anchors 4 and 5, clearly above the midpoint.

4 / 5

Distinctiveness Conflict Risk

The description occupies a clear niche with distinct triggers — "DNAnexus", "dxpy", "apps/applets", "FASTQ/BAM/VCF" — that no other plausible skill would claim, minimizing conflict risk.

5 / 5

Total

16

/

20

Passed

Validation

87%

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

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

referenced_paths_exist

Referenced path issues: 2 missing

Warning

Total

14

/

16

Passed

Repository

aipoch/medical-research-skills

Path

scientific-skills/Data Analysis/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.