CtrlK
BlogDocsLog inGet started
Tessl Logo

genebass-gene-burden-skill

Submit compact Genebass gene burden requests for one Ensembl gene ID and one burden set. Use when a user wants concise Genebass PheWAS summaries

68

Quality

83%

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

100%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 content is a well-structured, lean, single-purpose skill body with fully executable guidance, a clear single-step workflow with error handling, and appropriate sectioning without unnecessary external references. It exemplifies efficient progressive disclosure for a small skill.

DimensionReasoningScore

Conciseness

The ~32-line body is lean, assumes Claude's competence, and never explains concepts Claude already knows (no definition of Genebass, PheWAS, or burden sets); every bullet is actionable guidance that earns its place.

5 / 5

Actionability

Provides a copy-paste-ready bash command, exact JSON for both string and object input forms, and concrete burden-set values (pLoF, missense|LC, synonymous), covering the common cases fully.

5 / 5

Workflow Clarity

As a simple single-purpose skill the single action (pipe JSON to the script, parse output, return markdown) is unambiguous, and error handling is specified (ok=false with error.code/message); the simple-skill exception applies and no destructive/batch cap is triggered.

5 / 5

Progressive Disclosure

Under 50 lines with no external references needed (explicitly stated), organized into clear sections (Operating rules, Execution behavior, Input, Output, Execution, References), and the referenced bundle file scripts/genebass_gene_burden.py exists and is correctly pointed to.

5 / 5

Total

20

/

20

Passed

Description

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

The description clearly states a distinct niche capability and includes an explicit "Use when..." trigger, but it describes only one concrete action and lacks synonym/variation coverage in its trigger terms. It is solid and distinguishable yet not maximally comprehensive.

Suggestions

Add one or two more concrete actions (e.g., return association counts, summarize truncated result sets) to lift specificity toward comprehensive coverage.

Broaden trigger terms with natural synonyms a user might say, such as "gene-based PheWAS", "phenome-wide association", or "burden test", to improve trigger-term quality.

Expand the "Use when..." clause with an additional concrete trigger phrase (e.g., "or when the user asks for gene-based burden test summaries") to push completeness to the top anchor.

DimensionReasoningScore

Specificity

Names the domain and a concrete action ("Submit compact Genebass gene burden requests for one Ensembl gene ID and one burden set") but lists only one action rather than comprehensive coverage, matching the anchor that names domain plus 1-2 concrete actions.

3 / 5

Completeness

Both "what" (submit gene burden requests) and an explicit "Use when..." clause (concise Genebass PheWAS summaries) are present; it is not a 5 because the trigger is a single phrase rather than the multiple concrete triggers in the top anchor.

4 / 5

Trigger Term Quality

Relevant niche keywords appear ("Genebass", "gene burden", "Ensembl gene ID", "PheWAS summaries") but common variations or synonyms are absent, fitting the anchor for some relevant keywords missing common variations.

3 / 5

Distinctiveness Conflict Risk

Highly specific niche triggers (Genebass, Ensembl gene ID, PheWAS burden sets) make conflict with other skills minimal, matching the clear-niche anchor.

5 / 5

Total

15

/

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.

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.