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

65%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

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

Quality

Content

65%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 is well-structured and actionable with verified executable commands and excellent progressive disclosure, but it is dragged down by template filler and a workflow that lacks an explicit validation/feedback loop. Tightening the prose and adding a verify-on-error step would raise the weaker dimensions.

Suggestions

Add an explicit validation checkpoint in the run plan (e.g., check the JSON output for an 'error' key / non-zero exit and retry or adjust the field before returning).

Trim generic template phrasing in 'Key Features' and 'Implementation Details' that restates the description or states obvious process hygiene.

Include one concrete worked example (e.g., 'python scripts/hgnc.py fetch BRAF') so the actionability reaches fully copy-paste-ready coverage.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with short bullets and executable commands, but several generic template phrases ('structured execution path', 'produce a bounded deliverable') and a When-to-Use bullet restating the description are padding Claude does not need.	3 / 5
Actionability	Each tool ships a concrete, copy-pasteable command with documented parameters and a py_compile/--help smoke test, verified against the actual script subcommands; just short of 5 because no end-to-end concrete example term is shown.	4 / 5
Workflow Clarity	A clear run-plan sequence exists (confirm input, configure, run, review) but lacks an explicit validation checkpoint or error feedback loop for the network fetches, capping it at 3 per the batch/external-operation rule.	3 / 5
Progressive Disclosure	A short, single-purpose skill under 50 lines with clean section headers and no need for external reference files; the one bundle file (scripts/hgnc.py) is correctly referenced and not inlined as a wall of text.	5 / 5
	Total	15 / 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 is specific and distinctive with concrete actions and natural domain terms, but it omits any explicit 'Use when...' trigger guidance, capping its completeness. Adding a when-to-use clause would lift both completeness and trigger quality.

Suggestions

Append an explicit 'Use when...' trigger clause naming concrete user intents (e.g., 'Use when looking up a gene symbol, HGNC ID, or official gene name').

Add common synonyms users say (e.g., 'gene symbols', 'gene names', 'official nomenclature') to broaden trigger coverage toward the comprehensive anchor.

Consider naming the data formats returned (e.g., JSON records) to make the deliverable concrete and reduce the open-ended 'other metadata'.

Dimension	Reasoning	Score
Specificity	Names the HGNC domain plus concrete actions ('search for and retrieve gene information including symbols, names, IDs'), giving several specific actions; held below 5 only because 'other metadata' is open-ended rather than fully enumerated.	4 / 5
Completeness	Clearly states the 'what' but provides no 'Use when...' clause or equivalent explicit trigger guidance, so per the rubric cap it cannot exceed 3.	3 / 5
Trigger Term Quality	Includes natural user terms ('gene information', 'symbols', 'names', 'IDs', 'HGNC') but lacks broader synonyms or extension-style triggers that would push it to comprehensive anchor 5.	4 / 5
Distinctiveness Conflict Risk	HGNC is a clear, narrow niche with distinct gene-symbol triggers and minimal overlap risk; just short of 5 because the missing explicit when-to-use phrasing slightly weakens trigger distinctiveness.	4 / 5
	Total	15 / 20 Passed

Validation

93%

Warnings & errors only

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

Criteria	Description	Result
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
Commit: 63c61d3

Reviewed: 10 hours ago

Table of Contents

Discovery Implementation Validation

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.