CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

biopython-entrez

Use Bio.Entrez to access NCBI databases (e.g., PubMed/GenBank) for searching, fetching summaries, and downloading records when your workflow needs to call the NCBI E-utilities API over the network.

Quality

79%

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/biopython-entrez/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

72%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-structured, highly actionable skill: the worked example is complete and runnable, and the single external reference is real and properly signaled. Weaknesses are duplicated convention guidance (hurting token efficiency) and absent validation/verification steps for batch network operations, which also leaves the retry/backoff guidance as description rather than demonstrated code.

Suggestions

Remove the duplicate "Configuration and I/O conventions" bullets in Implementation Details (or the equivalent bullets in Key Features) — they repeat the same config/task_config.json, python scripts/<task>.py, UTF-8, and ensure_ascii=False guidance verbatim.

Add a validation step to the example workflow for batch operations: verify the returned record count against the esearch hit count, wrap Entrez calls in a retry-with-backoff helper for HTTP 429/5xx, and check for Entrez.ParserError when reading responses.

Trim the overlap between When to Use, Key Features, and the frontmatter description (e.g., fold the two API-key/rate-limit mentions into one place) to reduce token cost without losing information.

DimensionReasoningScore

Conciseness

The body is mostly efficient and free of background-concept padding, but the configuration/invocation conventions appear nearly verbatim twice ("Standardized configuration and invocation conventions" under Key Features and "Configuration and I/O conventions" under Implementation Details), and the When to Use / Key Features lists overlap each other and the description — it could be meaningfully tightened.

3 / 5

Actionability

The example is fully executable end to end: a concrete config/task_config.json, a complete working scripts/pubmed_summaries.py using esearch/esummary with output handling, and the exact run command — copy-paste ready and covering the most common case.

5 / 5

Workflow Clarity

The search → summarize → write sequence is clear and empty-result handling exists, but this is a batch-operation skill with no validation or verification of results (e.g., record counts, parse-error checks) and the retry/backoff feedback loop is only described, never shown — per the batch-operations cap, workflow clarity cannot exceed 3.

3 / 5

Progressive Disclosure

Well-organized overview with a single clearly signaled, one-level-deep reference ("See references/databases.md for database notes and selection guidance") that exists in the bundle; database detail is appropriately offloaded and navigation is easy.

5 / 5

Total

16

/

20

Passed

Description

78%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 strong description that names a distinct niche, multiple concrete actions, and an explicit use condition. Its main weakness is the trigger framing: the when clause is written from the implementer's perspective ("call the NCBI E-utilities API") rather than in terms a user would naturally say, and a few natural synonyms are absent.

Suggestions

Rewrite the when clause in user-natural terms, e.g. "Use when the user wants to search PubMed, download GenBank records, or look up genes/proteins in NCBI databases" instead of "when your workflow needs to call the NCBI E-utilities API over the network".

Add one or two natural synonyms such as "biomedical literature/abstracts" or "nucleotide and protein sequences" to broaden trigger coverage without adding length.

Mention cross-database linking (e.g., PubMed to PMC, Gene to Protein) in the description to close the specificity gap with the body's actual feature set.

DimensionReasoningScore

Specificity

Names the domain (Bio.Entrez, NCBI, PubMed/GenBank) and three concrete actions — "searching, fetching summaries, and downloading records" — but omits cross-database linking (elink) that the body itself covers, so coverage has minor gaps rather than being comprehensive.

4 / 5

Completeness

Both what ("access NCBI databases ... for searching, fetching summaries, and downloading records") and when ("when your workflow needs to call the NCBI E-utilities API over the network") are explicitly present, but the when clause is framed in implementation/API terms rather than concrete user-natural trigger phrases.

4 / 5

Trigger Term Quality

Good natural keyword coverage ("PubMed", "GenBank", "NCBI", "searching", "downloading records") that users would actually say, but common synonyms and variations like "biomedical literature", "abstracts", "nucleotide/protein sequences", or "fetch sequences" are missing.

4 / 5

Distinctiveness Conflict Risk

A clear niche — NCBI E-utilities via Bio.Entrez — with distinct triggers (PubMed, GenBank, E-utilities, NCBI) that no adjacent skill (generic Biopython, generic web APIs) would accidentally claim; minimal conflict risk.

5 / 5

Total

17

/

20

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

referenced_paths_exist

Referenced path issues: 2 missing

Warning

Total

14

/

16

Passed

Repository

aipoch/medical-research-skills

Path

scientific-skills/Evidence Insight/biopython-entrez/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.