CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

gwas-pipeline

End-to-end GWAS automation wrapping PLINK2 for genotype QC and REGENIE for two-step whole-genome regression association testing. Produces Manhattan plots, QQ plots, clumped lead variants, and structured summary statistics.

Quality

76%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/gwas-pipeline/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

71%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-organized, mostly actionable body with concrete CLI examples and a clearly sequenced workflow that includes up-front validation. The key weaknesses are a dangling reference to an unbundled script, unstated QC/analysis parameters, and no error-recovery guidance for a long batch pipeline.

Suggestions

Bundle the referenced gwas_pipeline.py under scripts/ (and point the CLI examples at that path) so the skill is self-contained and the commands are actually runnable.

State the concrete QC thresholds (e.g., variant/sample missingness, MAF, HWE cutoffs) inline or in a references/qc-thresholds.md file, since the skill's value proposition is 'field-standard' thresholds rather than ad hoc ones.

Add brief failure-handling checkpoints between pipeline stages (what to do if QC exhausts variants, REGENIE exits nonzero, or zero variants reach P < 5e-8) to upgrade workflow clarity.

DimensionReasoningScore

Conciseness

The body is largely lean — a workflow list, an input-format table, and concrete CLI commands with no tutorials on concepts Claude already knows. Minor trimmable padding remains (the "Why This Exists" rationale section and a Dependencies list that duplicates the frontmatter's install/requires metadata), so it sits at level 4 rather than level 5's every-token-earns-its-place.

4 / 5

Actionability

Concrete, copy-paste-ready commands are provided for demo and real-data runs ("python skills/gwas-pipeline/gwas_pipeline.py --demo --output /tmp/gwas_demo" and the multi-flag real-data invocation), plus a table of input formats and required fields. It is not a 5: the actual QC thresholds and REGENIE parameters the skill claims to apply are never stated, and the referenced script is not part of the skill bundle, leaving minor but real execution gaps.

4 / 5

Workflow Clarity

The Workflow section gives a clear six-step sequence that opens with an explicit validation step ("Validate: Check input files exist, detect format, verify binaries on PATH") and ends with a defined report artifact set. It falls short of level 5 because there are no error-recovery/feedback loops for failure modes (e.g., QC filtering out all samples, REGENIE step failure, empty results) even though this is a multi-stage batch pipeline.

4 / 5

Progressive Disclosure

Section headers are clear and content is well-divided, but the skill's only external reference — "skills/gwas-pipeline/gwas_pipeline.py" — does not exist in the bundle (no references/, scripts/, or assets/ directories), and operational details (QC thresholds, REGENIE flag sets, output formats) are neither inlined nor split into a reference file. This matches level 3 ('some structure but could be better organized') better than level 4, where references would be present and mostly clear.

3 / 5

Total

15

/

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, well-scoped description that names tools, methods, and outputs without fluff. Its main weakness is the complete absence of a 'when to use' trigger clause, which caps completeness, and slightly thin synonym coverage for trigger terms.

Suggestions

Append an explicit trigger clause, e.g. "Use when the user mentions GWAS, genome-wide association studies, case-control or quantitative trait analysis, or provides PLINK/BGEN genotype files with a phenotype file."

Add natural synonyms and file extensions users would mention, such as "genome-wide association study", "case-control", ".bed/.bgen", and "summary statistics".

Add a short differentiator from sibling skills (e.g., "for running analyses — for lookup or PRS see gwas-lookup/gwas-prs") to reduce routing overlap within the gwas-* skill family.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions with named tools: "wrapping PLINK2 for genotype QC and REGENIE for two-step whole-genome regression association testing" plus concrete outputs ("Manhattan plots, QQ plots, clumped lead variants, and structured summary statistics"). Coverage spans inputs, analysis, and outputs comprehensively, matching the level-5 anchor rather than the level-4 anchor with only 'minor gaps'.

5 / 5

Completeness

The 'what' is clear and detailed, but there is no 'Use when...' clause or equivalent explicit trigger guidance anywhere in the description — per the judging guidelines this caps completeness at 3. It is not a 4 because the 'when' is entirely absent rather than present-but-imprecise.

3 / 5

Trigger Term Quality

Good natural keyword coverage — "GWAS", "Manhattan plot", "QQ plot", "association testing", "PLINK2", "REGENIE" are terms domain users actually say. A few natural variations are missing (e.g., "genome-wide association study" spelled out, "case-control", file extensions like .bgen/.bed), so it fits the level-4 'good coverage, a few natural terms missing' anchor rather than level 5's comprehensive synonym/extension coverage.

4 / 5

Distinctiveness Conflict Risk

The niche is clear (running QC + association testing with PLINK2/REGENIE), but generic triggers like "GWAS" and "Manhattan plot" overlap with closely related skills in the same family (the body names gwas-lookup and gwas-prs as chaining partners). This matches level 4 ('mostly distinct; minor overlap risk with closely related skills') better than level 5's minimal conflict risk.

4 / 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_field

'metadata' should map string keys to string values

Warning

Total

15

/

16

Passed

Repository

ClawBio/ClawBio

Path

skills/gwas-pipeline/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.