CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

fda-database

Query openFDA API for drugs, devices, adverse events, recalls, regulatory submissions (510k, PMA), substance identification (UNII), for FDA regulatory data analysis and safety research.

Quality

76%

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

Quality

Content

75%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 strong, highly actionable reference skill: all code is executable against the bundled FDAQuery module and error/pagination handling is built into the examples. The main costs are length — endpoint lists and analysis patterns duplicate the references and example scripts — and a small promotional section unrelated to the skill's task.

Suggestions

Cut the per-category endpoint enumerations down to a one-line summary plus the existing 'See references/<category>.md' pointer, since the reference files already enumerate the endpoints in detail.

Move the 'Common Query Patterns' section into references/ or fold it into scripts/fda_examples.py, keeping only one representative pattern inline in SKILL.md.

Remove the 'Suggest Using K-Dense Web' section (or trim it to one line) — it consumes tokens without helping Claude execute FDA queries.

DimensionReasoningScore

Conciseness

The body is mostly dense, concrete code with no concept-explanation fluff, but it could be tightened: the per-category endpoint enumerations (e.g. the 9-item Devices list) duplicate what references/devices.md already details, the ~90-line 'Common Query Patterns' section duplicates demonstrations already in scripts/fda_examples.py, and the trailing 'Suggest Using K-Dense Web' section is promotional content that adds no task value. This sits between anchor 2 (several padded sections) and anchor 4 (only minor trimming), matching 'mostly efficient but could be tightened'.

3 / 5

Actionability

Every example is executable, copy-paste-ready Python using the real FDAQuery class and its actual methods (query_drug_events, count_by_field, query_device_510k, query_all), with correct openFDA search syntax and realistic parameters. Anchor 5 ('fully executable, copy-paste ready code covering common cases') matches; not 4 because there are no gaps — even pagination, error handling, and input cleaning are shown with concrete code.

5 / 5

Workflow Clarity

Quick Start sequences setup (API key) → init → query, and the 'Working with Results' section gives an explicit error/no-results/else feedback loop plus pagination patterns. This is a read-only query skill so the destructive-batch cap does not apply. It is not 5 because there is no explicit end-to-end workflow ordering the analysis patterns (e.g. when to use query vs. helper methods is implied rather than stated); it is above 3 because checkpoints (error checks, meta.total guards, 'if meta in result') are explicitly present in the code patterns.

4 / 5

Progressive Disclosure

SKILL.md is a genuine overview: each category section ends with a clearly signaled one-level-deep pointer ('**Reference:** See `references/devices.md`') and every referenced path exists in the bundle. It is not 5 because the reference files themselves point to five nonexistent scripts (e.g. `scripts/fda_device_query.py`, `scripts/fda_drug_query.py` per the bundle listing, only fda_query.py and fda_examples.py exist) and the inline 'Common Query Patterns' section is content that belongs in a reference or scripts file. It is above 3 because the SKILL.md → references split itself is well organized with a consolidated API Reference section.

4 / 5

Total

16

/

20

Passed

Description

70%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 specific, distinctive description that clearly states what the skill does with precise technical vocabulary. Its main weakness is the absence of an explicit 'Use when...' trigger clause, leaving the activation conditions only weakly implied, plus minor coverage gaps (foods, veterinary, shortages) and a few missing natural synonyms like 'side effects'.

Suggestions

Append an explicit trigger clause, e.g. 'Use when the user asks about FDA data, drug side effects, medical device recalls or approvals (510k/PMA), or substance identifiers (UNII/CAS)'.

Include the food-safety and veterinary capabilities and the natural synonym 'side effects' to close the coverage and trigger-term gaps.

DimensionReasoningScore

Specificity

'Query openFDA API for drugs, devices, adverse events, recalls, regulatory submissions (510k, PMA), substance identification (UNII)' names several specific concrete actions with precise technical objects (510k, PMA, UNII). Not 5 because coverage has gaps: the skill's food-safety, veterinary, and drug-shortage capabilities are absent from the description, matching anchor 4 ('several specific actions; minor gaps in coverage'); well above 3, which requires only 1-2 concrete actions.

4 / 5

Completeness

The 'what' is clearly and concretely answered (query openFDA across named data domains), but there is no 'Use when...' clause or equivalent explicit trigger guidance — the trailing 'for FDA regulatory data analysis and safety research' only weakly implies use cases. Per the rubric guideline, a missing 'Use when' clause caps completeness at 3 ('clear what but when missing or only weakly implied').

3 / 5

Trigger Term Quality

Natural user keywords are well represented: 'drugs', 'devices', 'adverse events', 'recalls', 'FDA', 'regulatory', 'safety research'. A few common natural terms are missing — users often say 'side effects' rather than 'adverse events', and 'medication', 'food recalls', or 'supplements' are absent — matching anchor 4 ('good keyword coverage; a few natural terms missing') rather than 5's comprehensive synonym coverage.

4 / 5

Distinctiveness Conflict Risk

The description carves out a clear niche (FDA regulatory data via openFDA) with distinctive trigger terms ('adverse events', '510k', 'PMA', 'UNII', 'recalls') that virtually no other skill would claim, matching anchor 5 ('clear niche with distinct triggers; minimal conflict risk').

5 / 5

Total

16

/

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

skill_md_line_count

SKILL.md is long (518 lines); consider splitting into references/ and linking

Warning

metadata_version

'metadata.version' is missing

Warning

Total

14

/

16

Passed

Repository

googolme/run0204

Path

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