CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

pubmed-database

Direct REST API access to PubMed. Advanced Boolean/MeSH queries, E-utilities API, batch processing, citation management. For Python workflows, prefer biopython (Bio.Entrez). Use this for direct HTTP/REST work or custom API implementations.

Quality

72%

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/pubmed-database/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

53%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 thorough, well-referenced skill with strong query examples and executable API code, undermined by significant duplication between SKILL.md and its own reference files plus across its internal sections. The workflows are clearly sequenced but lack validation checkpoints for the batch operations they perform.

Suggestions

Cut duplicated content: state rate limits, search-history expiry, and clipboard limits once and remove the redundant repetitions in the Tips, API Usage, and Limitations sections; trim sections 7–8 (My NCBI, RSS, clipboard) to one-line pointers.

Move the MeSH subheading list, publication-type list, and detailed API parameter documentation into the existing reference files, keeping SKILL.md as an overview with example queries and the two core code blocks.

Add validation checkpoints to Workflow 3 (Programmatic Data Extraction): check HTTP response status and esearchresult count before fetching, implement the exponential-backoff retry on HTTP 429 that the tips recommend, and verify record count after EFetch.

DimensionReasoningScore

Conciseness

The ~460-line body is noticeably verbose: rate limits appear three times (§4, Tips, Limitations), search-history expiry and clipboard limits each appear twice, and sections 7–8 explain web-UI features (My NCBI, RSS feeds, clipboard) tangential to what the skill is invoked for. The 'mostly efficient' bar of 3 is exceeded by this padding, though the core query/API detail is genuinely non-obvious domain knowledge.

2 / 5

Actionability

Two complete, executable Python blocks cover the common search-then-fetch cases, and example queries are copy-paste ready. Minor gaps: the elink and batch-export examples are bare URL query strings rather than runnable requests, and exponential backoff is recommended but never shown.

4 / 5

Workflow Clarity

Five numbered workflows are clearly sequenced, but the programmatic workflows involve batch operations (EPost, bulk EFetch, batch export) with no validation or verification checkpoints — no response-status checks, retry-on-failure, or verify-output steps. Per the batch-operations rule, workflow clarity is capped at 3.

3 / 5

Progressive Disclosure

Reference signaling is excellent: per-section 'When to consult X.md' bullets, grep patterns for locating content, and a dedicated 'Working with Reference Files' section with a loading strategy; references are one level deep and real. The gap is that the body inlines substantial detail (MeSH subheading lists, publication types, API parameters) that duplicates the reference files, keeping it below the 'appropriately split' bar of 5.

4 / 5

Total

13

/

20

Passed

Description

80%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 with concrete, domain-specific capabilities and an explicit 'Use this for...' trigger clause. Its main weakness is a when-clause scoped to implementation style rather than user goals, which narrows discoverability for literature-search requests the skill clearly serves.

DimensionReasoningScore

Specificity

The description lists multiple specific concrete actions — 'Direct REST API access', 'Advanced Boolean/MeSH queries, E-utilities API, batch processing, citation management' — giving comprehensive coverage of the skill's domain. Score 4's 'minor gaps' doesn't apply since search, API access, batch, and citation work are all named.

5 / 5

Completeness

Both 'what' ('Direct REST API access to PubMed...') and 'when' ('Use this for direct HTTP/REST work or custom API implementations') are present. The when-clause is narrow and implementation-focused, omitting the literature-search triggers that the skill body itself emphasizes, so it doesn't reach the concrete-trigger-phrases bar of 5.

4 / 5

Trigger Term Quality

Good natural keywords users would say: 'PubMed', 'REST API', 'citation management', 'biopython'. Missing common variations and synonyms like 'literature search', 'biomedical literature', or 'MEDLINE', so it falls short of the comprehensive anchor at 5.

4 / 5

Distinctiveness Conflict Risk

'PubMed', 'MeSH', and 'E-utilities' form a clear niche with distinct triggers, and the biopython pointer actively routes Python work away from this skill. Minor overlap risk remains from 'citation management' and the generic 'custom API implementations' trigger.

4 / 5

Total

17

/

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/pubmed-database/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.