CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

chea-api

Access ChEA3 and Harmonizome ChEA data for transcription factor enrichment analysis and metadata retrieval. Use when the user needs to perform ChEA3 enrichment analysis on a gene set, get metadata about the ChEA dataset, or retrieve information about a specific transcription factor (attribute).

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 ./scientific-skills/Evidence Insight/chea-api/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

50%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 core Usage and CLI sections are accurate and executable against the bundled script, but they are buried in a large amount of generic, non-specific boilerplate (When to Use, Key Features, Implementation Details, Output Contract, Failure Handling) that adds no information. Peripheral validation guidance is also broken — the --help command and its expected output do not match the script, and one example references a nonexistent path.

Suggestions

Delete the generic template sections (When to Use, Key Features, Dependencies, Example Usage, Implementation Details, When Not to Use, Required Inputs, Recommended Workflow, Output Contract, Validation and Safety Rules, Failure Handling, Quick Validation) — roughly 60% of the body — and keep only the Usage, CLI Usage, and Requirements sections.

Fix the broken Quick Validation guidance: replace `python scripts/chea_client.py --help` with the script's actual no-arg usage output, and remove the fabricated "Result file: chea_api_result.md" expected-output block, since the script prints JSON to stdout.

Remove the bogus `cd "20260316/scientific-skills/Evidence Insight/chea-api"` line and the self-referential "See `## Usage` above" pointer; move the real Usage content to the top so the executable examples come before any supporting text.

DimensionReasoningScore

Conciseness

The majority of the body is generic template padding — "Use this skill when the request matches its documented task boundary", "Structured execution path designed to keep outputs consistent and reviewable", plus the boilerplate Output Contract / Failure Handling / Validation and Safety sections that state nothing skill-specific. Not 1 because it never lectures on concepts Claude already knows and the Usage/CLI code sections themselves are lean; not 3 because the padding is pervasive, not incidental.

2 / 5

Actionability

The Usage and CLI examples (enrich with a gene list, get_dataset_metadata, get_attribute_info("CREB1"), and the enrich/metadata/attribute subcommands) are copy-paste ready and match the actual script. Not 5 because peripheral commands are broken: the script has no --help flag (it only prints usage with no args), the "Example Usage" block cd's into a bogus hardcoded path ("20260316/scientific-skills/Evidence Insight/chea-api"), "See ## Usage above" is a self-referential pointer, and the "Expected output format" for --help is fabricated (the script prints JSON, not "Result file: chea_api_result.md").

4 / 5

Workflow Clarity

"Recommended Workflow" and the "Example run plan" list coherent sequences, but validation checkpoints are either generic ("Run a final validation pass for completeness, consistency, and safety") or broken (the Quick Validation --help command fails with "Unknown command"). Not 4 because the one explicit checkpoint command does not execute; not 2 because the primary workflows themselves are single, unambiguous commands.

3 / 5

Progressive Disclosure

Section headers are clear and the single bundled script reference (scripts/chea_client.py) is real and one level deep, but there is no references/ split and roughly 60% of the body is inline boilerplate (Key Features, Implementation Details, Required Inputs, etc.) that buries the genuinely useful Usage and CLI sections. Not 4 because content that should be cut or split is inlined and the useful material is interleaved with filler.

3 / 5

Total

12

/

20

Passed

Description

92%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 is strong: it uses third-person voice, enumerates all three concrete capabilities, and pairs them with an explicit, specific "Use when" trigger clause. The only weakness is modest synonym coverage (e.g., no mention of over-representation analysis, gene lists, or ChIP-seq vocabulary).

DimensionReasoningScore

Specificity

"perform ChEA3 enrichment analysis on a gene set, get metadata about the ChEA dataset, or retrieve information about a specific transcription factor (attribute)" lists multiple concrete actions that comprehensively cover the API's capabilities (matching the script's three functions). Not 4 because coverage leaves no minor gaps.

5 / 5

Completeness

Explicitly answers both what ("Access ChEA3 and Harmonizome ChEA data for transcription factor enrichment analysis and metadata retrieval") and when ("Use when the user needs to perform ChEA3 enrichment analysis on a gene set, get metadata about the ChEA dataset, or retrieve information about a specific transcription factor"). Not 4 because both halves are fully explicit with concrete trigger phrases.

5 / 5

Trigger Term Quality

Natural domain terms like "ChEA3 enrichment analysis", "gene set", "transcription factor", and "metadata" are present. Not 5 because common variations users might say ("over-representation analysis", "gene list", "ChIP", "TF enrichment") are missing.

4 / 5

Distinctiveness Conflict Risk

ChEA3/Harmonizome transcription factor enrichment is a clear niche with distinct triggers; no realistically adjacent skill would collide with these terms. Not 4 because there is no meaningful overlap risk with closely related skills.

5 / 5

Total

19

/

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

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository

aipoch/medical-research-skills

Path

scientific-skills/Evidence Insight/chea-api/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.