CtrlK
BlogDocsLog inGet started
Tessl Logo

ngs-atacseq-peaks-qc

Run or plan ATAC-seq QC, alignment, TSS enrichment, fragment-size, blacklist, peak-calling, consensus peak, and differential accessibility workflows.

70

Quality

85%

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

87%Weight 40%Scale 1-3

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A concise, highly actionable skill with copy-paste commands and a well-organized section structure. The only notable gap is the lack of an explicit validation/retry feedback loop for the batch pipeline, which caps workflow clarity.

Suggestions

Add a validate→fix→retry loop, e.g. after the QC Gates list: "If a sample fails a gate, rerun with adjusted parameters (e.g. --min-mapping-quality) and re-review before proceeding."

Number the route steps (preflight → run → QC Gates review → outputs) to make the sequence explicit rather than leaving it implied by section order.

DimensionReasoningScore

Conciseness

Lean imperative/bulleted body with no explanation of concepts Claude already knows (no "ATAC-seq is a technique that..." preamble); every section earns its place, matching the lean-and-efficient anchor.

3 / 3

Actionability

Provides three fully executable, copy-paste-ready bash commands with concrete flags and paths (ngs_preflight.py, run_fastq_assay_package.py, run_atacseq_peaks_qc.py) plus the nf-core invocation, not pseudocode.

3 / 3

Workflow Clarity

Has a sequenced route and a QC Gates checklist with a "Do not proceed to differential accessibility if..." gate, but no validate→fix→retry feedback loop, which the scoring notes say should cap batch-operation workflows at 2.

2 / 3

Progressive Disclosure

No bundle files exist and the body is organized into clear single-purpose sections (Essential Inputs, Route, QC Gates, Outputs) with no nested references or monolithic wall of text.

3 / 3

Total

11

/

12

Passed

Description

82%Weight 40%Scale 1-3

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-targeted description that names many concrete ATAC-seq actions and natural trigger terms. Its main gap is the absence of an explicit "Use when..." trigger clause, which caps completeness.

Suggestions

Add an explicit trigger clause, e.g. ". Use when the user mentions ATAC-seq, open-chromatin accessibility, Tn5, or wants ATAC QC/peak calling."

Mention input types (FASTQ/BAM) in the description so the trigger surface matches the body's Essential Inputs.

DimensionReasoningScore

Specificity

Lists many concrete actions ("QC, alignment, TSS enrichment, fragment-size, blacklist, peak-calling, consensus peak, and differential accessibility") rather than vague language, matching the multiple-specific-actions anchor.

3 / 3

Completeness

Strongly answers "what" but has no "Use when..." clause or equivalent explicit trigger guidance, so the missing "when" caps completeness at 2 per the guideline.

2 / 3

Trigger Term Quality

Covers natural domain terms a user would actually say ("ATAC-seq", "TSS enrichment", "fragment-size", "peak-calling", "differential accessibility"), giving good keyword coverage.

3 / 3

Distinctiveness Conflict Risk

ATAC-seq is a distinct niche with assay-specific triggers (TSS enrichment, fragment-size) that distinguish it from sibling skills like ChIP-seq/CUT&RUN, making misfiring unlikely.

3 / 3

Total

11

/

12

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
openai/plugins
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.