CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

pydeseq

Differential gene expression analysis for bulk RNA-seq count matrices using a DESeq2-like workflow in Python; use when you need Wald tests, FDR correction, and optional LFC shrinkage for condition/batch/covariate designs.

Quality

81%

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

68%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 highly actionable body: the single complete runnable example, explicit contrast/design syntax, and a real, well-partitioned bundle make it easy to execute correctly. Weaknesses are redundancy (Key Features vs. Implementation Details vs. the description), pinned time-sensitive versions, the absence of explicit validation checkpoints for a batch analysis, and hedged, non-linked pointers to the bundle files.

Suggestions

Delete the 'Key Features' section (it duplicates the description and Implementation Details), trim the volcano-plot block to a few lines or move it to references/workflow_guide.md, and relocate the pinned dependency versions (pandas >= 1.4.3, etc.) to references/api_reference.md to improve conciseness.

Add explicit validation checkpoints before fitting in the example script — e.g., assert counts are non-negative integers, confirm all design variables exist in metadata columns, and verify sample alignment — with a brief fix-and-retry note, raising workflow_clarity above the batch-operation cap.

Replace the conditional 'If your repository includes them, use:' phrasing with direct markdown links to references/api_reference.md, references/workflow_guide.md, and scripts/run_deseq2_analysis.py since the files verifiably exist in the bundle.

DimensionReasoningScore

Conciseness

The body is mostly efficient (the example script and Implementation Details earn their tokens), but there is measurable padding: the "Key Features" section ("End-to-end DESeq2-like workflow: normalization (size factors), dispersion estimation/shrinkage...") restates the description and Implementation Details; the ~30-line volcano-plot block is generic matplotlib Claude already knows; and pinned version numbers ("pandas >= 1.4.3", "numpy >= 1.23.0", "scipy >= 1.11.0") are time-sensitive without being in a deprecated/old-patterns section, which the guidelines explicitly penalize. Not anchor 2 because the majority of the body is domain-specific and non-redundant; not anchor 4 because the redundancy exceeds minor trimmable instances.

3 / 5

Actionability

The "Example Usage" section is a complete, runnable, copy-paste-ready script covering load, sample alignment ("common = counts_df.index.intersection(metadata.index)"), filtering, fitting ("dds.deseq2()"), Wald testing with contrast ("contrast=[\"condition\", \"treated\", \"control\"]"), shrinkage, export, and plotting. Concrete extras: install command ("uv pip install pydeseq2"), design-formula strings, and contrast format. This matches anchor 5 — fully executable code covering the common treated-vs-control case.

5 / 5

Workflow Clarity

The example script has a clear numbered sequence ("1) Load inputs" through "6) Minimal volcano plot") and some implicit input cleaning (intersection alignment, "metadata.dropna(subset=[\"condition\"])", low-count filtering). But this is a batch operation over a whole count matrix, and there are no explicit validation checkpoints or error-recovery loops: nothing verifies the documented requirements ("non-negative integer counts", design variables present in metadata, samples matched) before fitting, and no verify-then-proceed guidance exists — per the rubric's cap, a batch workflow without validation cannot score above 3.

3 / 5

Progressive Disclosure

The bundle is real and well-partitioned (references/api_reference.md, references/workflow_guide.md, scripts/run_deseq2_analysis.py all exist), and the "Notes on bundled references/scripts" section signals each file's purpose with one-level-deep references. Minor gaps keep it at anchor 4 rather than 5: the pointers use hedged conditional phrasing ("If your repository includes them, use:") instead of direct links, and the ~110-line inline example plus ~50 lines of Implementation Details push the SKILL.md toward monolith territory that a slimmer body plus the existing script could absorb.

4 / 5

Total

15

/

20

Passed

Description

87%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 names the domain, the workflow style, and multiple concrete statistical operations, and pairs them with an explicit 'use when' trigger clause covering condition/batch/covariate designs. The only deductions are the second-person 'use when you need' phrasing and a few missing natural synonyms (e.g., 'DE', 'padj', 'volcano plot').

DimensionReasoningScore

Specificity

"Differential gene expression analysis for bulk RNA-seq count matrices" plus "Wald tests, FDR correction, and optional LFC shrinkage" lists multiple concrete actions with near-comprehensive coverage (anchor 5). However, the "use when you need" clause is second-person voice, and the rubric mandates a 1-point specificity reduction for non-third-person voice, dropping it to 4. It is not a 3 because the domain and three-plus specific actions are all explicitly named.

4 / 5

Completeness

Explicitly answers both questions: the "what" is "Differential gene expression analysis for bulk RNA-seq count matrices using a DESeq2-like workflow in Python" and the "when" is the explicit trigger clause "use when you need Wald tests, FDR correction, and optional LFC shrinkage for condition/batch/covariate designs". This matches anchor 5 exactly (clear what AND when with concrete trigger phrases), unlike anchor 4 where the "when" is generic.

5 / 5

Trigger Term Quality

Strong natural keywords users would actually say: "Differential gene expression", "bulk RNA-seq", "DESeq2" (via "a DESeq2-like workflow"), "Wald tests", "FDR correction", "LFC shrinkage". It falls short of anchor 5 because common synonyms like "DE analysis", "padj", "adjusted p-values", or "volcano plot" are absent; it exceeds anchor 3 because coverage goes well beyond a single keyword.

4 / 5

Distinctiveness Conflict Risk

The niche is unambiguous — Python DESeq2-style bulk RNA-seq DE analysis — with distinct triggers ("DESeq2", "Wald tests", "FDR", "LFC shrinkage") that no adjacent skill (single-cell, plotting, general stats) would claim. Clear anchor 5 fit; not anchor 4 since there is no meaningful overlap risk with closely related skills.

5 / 5

Total

18

/

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: 1 missing

Warning

Total

14

/

16

Passed

Repository

aipoch/medical-research-skills

Path

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