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

77%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./bundled/skills/fda-database/SKILL.md

Quality

Content

72%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A highly actionable, well-structured skill with strong progressive disclosure and executable examples, weakened only by some verbosity and the absence of explicit validation checkpoints in its batch workflows.

Suggestions

Trim redundancy between the 'Key capabilities', 'When to Use This Skill', and per-category sections, and drop the introductory explanation of what openFDA is, to tighten conciseness.

Add an explicit validate→fix→retry feedback loop for batch operations (e.g., around query_all pagination) to raise workflow clarity.

Consolidate the duplicated 'run examples' guidance (Quick Start section 3 vs. the Scripts section) into a single reference.

Dimension	Reasoning	Score
Conciseness	Mostly efficient and code-driven, but the ~500-line body includes redundancy ('Key capabilities', 'When to Use This Skill', and per-category sections overlap the description) and mild concept explanation ('openFDA, the FDA's initiative to provide open APIs...'), so it does not reach the lean level-3 anchor.	2 / 3
Actionability	Provides abundant executable, copy-paste-ready code (e.g., 'from scripts.fda_query import FDAQuery' and concrete query calls) across categories and patterns, matching the fully-executable level-3 anchor.	3 / 3
Workflow Clarity	Multi-step patterns (safety profile, temporal trends, comparative analysis) are sequenced and an error-handling section exists, but there are no explicit validate→fix→retry checkpoints for batch operations like query_all pagination, capping workflow clarity at 2.	2 / 3
Progressive Disclosure	SKILL.md is a clear overview with well-signaled, one-level-deep references to six reference files and two scripts, all verified to exist, matching the level-3 anchor for clear overview with easy navigation.	3 / 3
	Total	10 / 12 Passed

Description

82%

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, domain-distinct description that names concrete capabilities and natural trigger terms, but it omits an explicit 'Use when...' clause, which caps completeness at 2.

Suggestions

Add an explicit 'Use when...' clause (e.g., 'Use when researching FDA drug/device safety, adverse events, recalls, or regulatory submissions') to lift completeness to 3.

Consider including a few everyday phrasings (e.g., 'drug safety', 'FDA data') alongside the clinical jargon to broaden trigger coverage.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions and entities ('Query openFDA API for drugs, devices, adverse events, recalls, regulatory submissions (510k, PMA), substance identification (UNII)'), matching the anchor for listing several specific concrete actions.	3 / 3
Completeness	Clearly answers 'what' but lacks an explicit 'Use when...' trigger clause; the judging guideline states a missing explicit trigger guidance should cap completeness at 2, so it does not reach level 3.	2 / 3
Trigger Term Quality	Includes natural terms a user would say when needing this skill ('drugs, devices, adverse events, recalls, FDA regulatory data analysis, safety research'), with good coverage; technical tokens like 510k/PMA/UNII are appropriate for this domain.	3 / 3
Distinctiveness Conflict Risk	Occupies a clear niche (openFDA regulatory data) with distinct triggers, making it unlikely to conflict with unrelated skills; not level 2 because it is far more specific than 'Works with document files'.	3 / 3
	Total	11 / 12 Passed

Validation

87%

Warnings & errors only

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

Criteria	Description	Result
skill_md_line_count	SKILL.md is long (516 lines); consider splitting into references/ and linking	Warning
metadata_version	'metadata.version' is missing	Warning

	Total	14 / 16 Passed

Repository: foryourhealth111-pixel/Vibe-Skills
Path: bundled/skills/fda-database/SKILL.md
Commit: f627ab5

Reviewed: about 9 hours ago

Table of Contents

Discovery Implementation Validation

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.