CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

fda-database

Query the openFDA API to retrieve FDA regulatory datasets (drugs, devices, adverse events, recalls, submissions, UNII) when you need programmatic safety/regulatory evidence for analysis or research.

Quality

78%

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

Quality

Content

68%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's greatest strength is actionability — a complete, verified, runnable example that exercises nearly every helper in the actual script. It is held back by verbose hedging and maintainer asides, duplicated endpoint detail that belongs in the references, and workflows that mention error guards but never demonstrate a validate/retry checkpoint.

Suggestions

Trim maintainer-oriented and hedged asides (the requirements.txt pinning note, 'typically documented in', 'implementation-dependent' hedges) and delete the inline endpoint/query-syntax lists that duplicate references/, linking each domain to its reference file instead.

Add an explicit validation checkpoint to the workflow: show checking meta.error / empty results in the example script (or a 'verify the response before using totals' step) so the guards become a demonstrated feedback loop rather than a caution list.

Replace the single blockquote reference dump with per-topic pointers under the relevant sections (e.g., 'Drugs: see references/drugs.md') so navigation to each domain's details is clearly signaled.

DimensionReasoningScore

Conciseness

The body is mostly efficient (sectioned, code-forward, no basic-concept explanations), but includes unnecessary padding: maintainer-oriented asides ('If you maintain this skill, pin them in `requirements.txt`...'), hedged meta-commentary ('typically documented in', 'implementation-dependent', 'Exact helper method names ... are implemented in scripts/fda_query.py'), and an endpoint enumeration that duplicates content in the reference files. This fits anchor 3's 'mostly efficient but includes some unnecessary explanation or could be tightened', not 4, because several sections need trimming rather than one or two.

3 / 5

Actionability

The example is fully executable and copy-paste ready: env-var setup, a complete script covering drug safety profiles, aggregations, monthly trends, device/food/substance lookups, and a run command. Method names and signatures (query_drug_events, count_by_field with exact=True, query_food_recalls(reason=...), query_substance_by_unii) were verified against scripts/fda_query.py and match. This matches anchor 5's 'fully executable; copy-paste ready code or commands; specific examples cover the common cases'.

5 / 5

Workflow Clarity

A rough sequence exists ('1) Set an API key', '2) Run a complete script', '3) Run the repository examples') and result handling lists guards ('Always guard for: Missing results, Empty result sets, error objects'), but there are no explicit validation checkpoints or feedback loops — the example script never demonstrates checking meta/error responses or retrying. This matches anchor 3's 'sequence present but checkpoints missing or implicit'; it does not reach 4 because validation is described as a caution rather than shown as a step.

3 / 5

Progressive Disclosure

The skill correctly offloads detail to six real one-level-deep reference files (references/api_basics.md, drugs.md, devices.md, foods.md, animal_veterinary.md, other.md — all verified present), and the SKILL.md stays an overview. Minor gaps keep it at anchor 4 rather than 5: the reference pointer is a single buried blockquote ('> Additional endpoint notes and query syntax are typically documented in: ...') instead of per-topic links, and the 'Implementation Details' section re-inlines endpoint lists and query syntax that overlap the references.

4 / 5

Total

15

/

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: concrete, third-person, with an explicit 'when' clause and a distinct regulatory-data niche. Its main limitations are a single retrieve-style verb (rather than several distinct actions) and slightly abstract trigger phrasing that omits common user variations like '510(k)', 'food recalls', or 'FDA approval'.

DimensionReasoningScore

Specificity

The description gives one concrete action pair ('Query the openFDA API to retrieve FDA regulatory datasets') but enumerates a broad scope '(drugs, devices, adverse events, recalls, submissions, UNII)', placing it between anchor 3 (1-2 concrete actions) and anchor 5 (multiple distinct actions like extract/fill/merge). It is above the midpoint because the enumerated coverage is comprehensive, but below 5 since there is only a single retrieve-style verb.

4 / 5

Completeness

Both parts are explicitly present: what ('Query the openFDA API to retrieve FDA regulatory datasets...') and when ('when you need programmatic safety/regulatory evidence for analysis or research'). The 'when' clause is explicit but phrased as a need-state rather than the concrete user-utterance triggers of anchor 5 ('when the user mentions PDFs, forms, or document extraction'), so it sits at anchor 4.

4 / 5

Trigger Term Quality

Natural terms users would say are present: 'FDA', 'openFDA', 'drugs', 'devices', 'adverse events', 'recalls', 'submissions', 'UNII', 'safety/regulatory'. A few common variations are missing (e.g., '510(k)', 'food recalls', 'FDA approval', 'drug labels'), which fits anchor 4's 'good keyword coverage; a few natural terms missing' rather than 5's exhaustive synonym coverage.

4 / 5

Distinctiveness Conflict Risk

The description occupies a clear niche — the openFDA API, FDA regulatory datasets, and UNII substance identifiers — with trigger terms unlikely to appear when a user wants any other skill. This matches anchor 5's 'clear niche with distinct triggers; minimal conflict risk'.

5 / 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/fda-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.