CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

openfda-database

Query, search, and download data from the openFDA API for drugs, devices, foods, tobacco, cosmetics, animal and veterinary products, substances, and transparency data. Use for FDA adverse events, recalls, labeling, approvals, shortages, 510(k) clearances, NDC lookups, and any FDA safety or regulatory data query across all 28 API endpoints.

Quality

87%

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

SKILL.md
Quality
Evals
Security

Quality

Content

82%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-crafted, highly actionable skill body with executable commands throughout, clear workflow sequencing, and proper use of bundle files for detail. The main improvement opportunities are deduplicating the repeated rate-limit warnings and the endpoint list, and adding an explicit verification step before exhaustive downloads.

Suggestions

Consolidate the rate-limit/API-key guidance into one place: the warning is repeated nearly verbatim in the prerequisites, the Rate Limiting bullet, and the Warning blockquote.

Replace the inline 28-endpoint listing under 'Available Endpoints' with a pointer to references/api_endpoints.md, which already documents the full list, to remove duplication.

Add an explicit verification checkpoint in the Workflow before exhaustive downloads (e.g., check the reported total_matching from a search before invoking download --all_results).

DimensionReasoningScore

Conciseness

The body is efficient and assumes Claude's competence (no explanation of what the FDA or an API is), but the rate-limit warning is repeated three times ("Always set an API key before running multi-query workflows" appears in both the Rate Limiting bullet and the Warning blockquote, plus again in the prerequisites) and the Recipes section restates the description's full category enumeration verbatim. These are minor trimmable instances matching the 4 anchor rather than the fully lean 5 anchor.

4 / 5

Actionability

Every subcommand (search, count, download) has a complete, copy-paste-ready `uv run scripts/openfda_query.py` invocation with all options documented, plus concrete executable examples for the key gotchas (quoting hyphenated NDCs, `.exact` matching with a fallback strategy). This fully matches the 5 anchor's 'copy-paste ready commands covering common cases'.

5 / 5

Workflow Clarity

The Workflow section gives a clear 5-step sequence, and the content includes genuine error-recovery feedback loops (retry without `.exact` if 0 results; fall back from drug/ndc to drug/label for discontinued products). It falls short of the 5 anchor because the batch `download` path lacks an explicit verification checkpoint (e.g., checking `total_matching` before an exhaustive `--all_results` pull), leaving a minor validation gap consistent with the 4 anchor.

4 / 5

Progressive Disclosure

SKILL.md is a well-organized overview with clearly signaled, one-level-deep references to references/api_endpoints.md and references/recipes.md (both verified to exist with no nested references), and bulk API detail is appropriately split out. Minor gaps keep it below the 5 anchor: the full 28-endpoint list is duplicated inline in the body, and references/citation.bib is present in the bundle but never referenced or explained.

4 / 5

Total

17

/

20

Passed

Description

87%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 clearly states both capabilities and explicit usage triggers with FDA-specific keywords. Its only weaknesses are the near-synonymous action verbs (query/search/download) and a few missing natural synonyms such as "side effects".

DimensionReasoningScore

Specificity

The description lists several concrete actions ("Query, search, and download data") with comprehensive domain coverage (drugs, devices, foods, tobacco, cosmetics, animal and veterinary, substances, transparency) across "all 28 API endpoints". It falls short of the 5 anchor only because the action verbs are near-synonyms for an API skill rather than the distinct action variety of the top anchor, while clearly exceeding the '1-2 concrete actions' of the 3 anchor.

4 / 5

Completeness

Explicitly answers both: what ("Query, search, and download data from the openFDA API for [all product categories]") and when ("Use for FDA adverse events, recalls, ... and any FDA safety or regulatory data query across all 28 API endpoints") with concrete trigger phrases, matching the top anchor exactly; the 4 anchor's 'when could be more explicit' does not apply here.

5 / 5

Trigger Term Quality

Strong natural keywords users would actually say: "FDA adverse events, recalls, labeling, approvals, shortages, 510(k) clearances, NDC lookups". A few natural synonyms are missing (e.g., "side effects", "FDA database"), placing it at good-but-not-comprehensive coverage rather than the 5 anchor.

4 / 5

Distinctiveness Conflict Risk

The openFDA/FDA-regulatory niche is unambiguous and every trigger term is FDA-specific, so it is clearly distinguishable from other skills with minimal conflict risk, matching the 5 anchor's 'clear niche with distinct triggers'.

5 / 5

Total

18

/

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

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository

google-deepmind/science-skills

Path

skills/openfda_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.