CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

ngs-atacseq-peaks-qc

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

67

Quality

84%

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

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

An excellent, dense operational skill: executable commands with real flags, explicit QC gates before interpretation, and a clean section flow with zero filler. The only gaps are a missing error-recovery loop for failed samples and no reference files to offload runner-option and sample-sheet detail.

Suggestions

Add a short feedback loop for QC-gate failures (e.g. what to check/rerun when TSS enrichment or replicate concordance fails) to make the batch workflow self-correcting rather than just gated.

Move the detailed runner/resource-plan flag documentation into a single one-level reference file and link it from the Route section, keeping the top-level commands minimal.

Document or link the expected sample-sheet format (atac_samples.csv columns) so the commands are executable without guessing the input schema.

DimensionReasoningScore

Conciseness

The body is lean and imperative throughout — an inputs checklist, routing commands, QC gates, and outputs — with no explanation of concepts Claude already knows and no padding. Every line carries non-obvious domain specifics (flags, output paths, gates), matching the 'every token earns its place' anchor rather than the score-4 'minor trim' anchor.

5 / 5

Actionability

Three fully-flagged, copy-paste-ready commands (preflight, shared epigenomics package, dedicated ATAC runner) plus concrete artifact names ('qc/atacseq_qc_summary.{tsv,json}', 'qc/atacseq_qc_dashboard.html', 'tracks/', 'resources/resource_plan.json') cover the common cases. This meets the 'fully executable; copy-paste ready; covers common cases' anchor, exceeding score 4 which permits minor gaps.

5 / 5

Workflow Clarity

There is a clear sequence (confirm essential inputs → route/preflight → run the appropriate runner → review QC gates → emit outputs) with an explicit checkpoint ('Review before biological interpretation'; 'Do not proceed to differential accessibility if replicate quality or metadata is insufficient'). It stops short of score 5 because there is no fix-and-retry feedback loop for failing samples and the failed-sample handling is only referenced as an output flag.

4 / 5

Progressive Disclosure

Sections are well-organized with no nested references and clearly signaled external script paths, but the body inlines a substantial amount of runner-flag and resource-plan documentation that would fit a one-level-deep reference file, and details like the sample-sheet format are never linked. This matches the 'good structure; most content appropriately placed; minor organization gaps' anchor rather than the fully split score-5 structure.

4 / 5

Total

18

/

20

Passed

Description

71%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 highly specific, domain-comprehensive description with strong natural trigger terms, undermined only by the complete absence of a 'when to use' clause. Adding an explicit 'Use when...' sentence with synonyms like chromatin accessibility would lift it to top marks.

Suggestions

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

Include common synonyms and file extensions users naturally say: 'chromatin accessibility', 'open chromatin', 'FRiP', 'FASTQ/BAM'.

State the boundary with the sibling epigenomics skill in the description itself (e.g. not for ChIP-seq/CUT&RUN) to reduce conflict risk.

DimensionReasoningScore

Specificity

The description enumerates concrete pipeline actions — 'ATAC-seq QC, alignment, TSS enrichment, fragment-size, blacklist, peak-calling, consensus peak, and differential accessibility' — giving comprehensive domain coverage. It exceeds the score-4 anchor ('several specific actions; minor gaps') because there is no meaningful capability gap.

5 / 5

Completeness

The 'what' is clearly and comprehensively stated, but there is no 'Use when...' clause or equivalent explicit trigger guidance — the rubric explicitly caps completeness at 3 in that case. It is not a 4 because the 'when' is entirely missing rather than merely imprecise.

3 / 5

Trigger Term Quality

Good coverage of natural terms an ATAC-seq user would say ('ATAC-seq', 'peak-calling', 'TSS enrichment', 'differential accessibility'), but common synonyms like 'chromatin accessibility', 'open chromatin', 'FRiP', and file extensions (.fastq/.bam) are absent. This matches the 'good keyword coverage; a few natural terms missing' anchor rather than the comprehensive score-5 anchor.

4 / 5

Distinctiveness Conflict Risk

'ATAC-seq' plus assay-specific deliverables (TSS enrichment, consensus peaks, differential accessibility) carve a clear niche with minimal conflict risk, but closely related NGS-epigenomics skills (the body references 'ngs-chip-cutrun-peaks-qc') could overlap on generic terms like 'QC' and 'peak-calling'. This is the 'mostly distinct; minor overlap risk' anchor, not the fully distinct score-5 anchor.

4 / 5

Total

16

/

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

openai/plugins

Path

plugins/ngs-analysis/skills/ngs-atacseq-peaks-qc/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.