CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

hgnc-api

Access the HGNC (HUGO Gene Nomenclature Committee) database to search for and retrieve gene information including symbols, names, IDs, and other metadata.

Quality

66%

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

Fix and improve this skill with Tessl

tessl review fix ./scientific-skills/Evidence Insight/hgnc-api/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

57%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 body provides concrete, executable commands for all three subcommands and is well-structured for a small single-script skill. However, it is padded with generic template sections (Key Features, Implementation Details, boilerplate When to Use bullets) that add tokens without adding skill-specific knowledge, and its run plan references a CONFIG block the script does not have.

Suggestions

Cut the template boilerplate sections (Key Features, Implementation Details, and generic When to Use bullets) that restate the description or give generic process advice.

Add one fully worked example, e.g., `python scripts/hgnc.py fetch "BRAF"` with the key fields of the expected output, instead of only placeholder commands.

Fix the run plan: remove the step about editing an in-file CONFIG block, which does not exist in scripts/hgnc.py, and make the verification step concrete (e.g., check the returned JSON for the expected hgnc_id/symbol).

DimensionReasoningScore

Conciseness

Several sections are template boilerplate rather than skill-specific instruction: "Scope-focused workflow aligned to: …", "Use this skill when a evidence insight task needs a packaged method instead of ad-hoc freeform output", and the generic "Implementation Details" bullets ("validate the request, choose the packaged workflow, and produce a bounded deliverable"). It is not 3 because the padding spans multiple whole sections (Key Features, Implementation Details, parts of When to Use and Dependencies), not just isolated spots; not 1 because the Tools section itself is lean and concrete.

2 / 5

Actionability

Concrete, mostly copy-paste-ready commands are provided ("python scripts/hgnc.py fetch \"{term}\" --field \"{field}\"", "python -m py_compile scripts/hgnc.py") with example values ("BRAF", "HGNC:1097") in the parameter docs. It is not 5 because no fully worked invocation with real values and expected output is shown, leaving minor gaps.

4 / 5

Workflow Clarity

The "Example run plan" lists a 4-step sequence, but checkpoints are vague ("Review the generated output and return the final artifact") and step 2 instructs editing an in-file "CONFIG block" that does not exist in scripts/hgnc.py. It is not 4 because validation is only implicit and one step is inaccurate; not 2 because the sequence is present and the operations (read-only API queries) are correctly outlined.

3 / 5

Progressive Disclosure

A small, single-script skill with well-organized sections; the only bundle file referenced ("scripts/hgnc.py") exists and is correctly referenced throughout, and there is no content that warrants splitting into reference files. It is not 4 because navigation and content placement are appropriate for a skill of this size with no external references needed.

5 / 5

Total

14

/

20

Passed

Description

61%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 what the skill does within a well-defined niche, with solid natural trigger terms for the gene-nomenclature domain. Its main weakness is the complete absence of explicit "when to use" guidance, and its action list is minimal with a vague "other metadata" tail.

Suggestions

Add an explicit trigger clause, e.g., "Use when the user mentions HGNC, HUGO gene names, official gene symbols, or HGNC IDs, or asks to look up human gene nomenclature."

Replace "and other metadata" with the concrete actions available, e.g., "fetch gene records by symbol or HGNC ID, search genes by keyword, and check service info."

Mention human-specificity explicitly to reduce overlap with general gene-database skills (e.g., NCBI/Ensembl).

DimensionReasoningScore

Specificity

Names the domain ("HGNC (HUGO Gene Nomenclature Committee) database") and two concrete actions ("search for and retrieve gene information including symbols, names, IDs"), but coverage is not comprehensive and "other metadata" is vague filler. It is not 4 because only two actions are listed with a generic tail; not 2 because real domain and real actions are named.

3 / 5

Completeness

The "what" is clear ("Access the HGNC database to search for and retrieve gene information…") but there is no "Use when…" clause or equivalent explicit trigger guidance, which caps completeness at 3. It is not 4 because the "when" is entirely absent rather than merely implicit or underspecified.

3 / 5

Trigger Term Quality

Good natural keyword coverage: "HGNC", "HUGO Gene Nomenclature Committee", "gene information", "symbols, names, IDs" — terms a user working with gene nomenclature would actually say. It is not 5 because common variations like "gene lookup", "official gene symbols", or "human gene names" are missing.

4 / 5

Distinctiveness Conflict Risk

"HGNC (HUGO Gene Nomenclature Committee) database" is a clear niche with mostly distinct triggers, but the broad wording "gene information including symbols, names, IDs, and other metadata" could overlap with other genomics/database skills (e.g., NCBI gene lookups). It is not 5 because no distinct trigger phrase carves out its specific territory.

4 / 5

Total

14

/

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/hgnc-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.