CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

fda-guideline-search

Search FDA industry guidelines by therapeutic area or topic.

Quality

60%

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

Quality

Content

50%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 delivers genuinely useful operational detail — a complete parameter table, runnable examples, and real bundle references — but it is buried in a large amount of generic template boilerplate and meta-commentary that dilutes the signal. Cutting the padding and making the workflow section describe the actual search procedure would lift it substantially.

Suggestions

Cut the generic template sections (Security Checklist, Risk Assessment, Lifecycle Status, Evaluation Criteria, Response Template, Output Requirements) or move them to a references/ file — they add little FDA-search-specific value and roughly halve the token footprint.

Remove the 'See `## X` above for related details' pointers and merge the duplicated sections (When to Use vs Input Validation, Key Features vs Features, Example Usage vs Usage, Workflow vs Implementation Details) into single, concrete sections.

Rewrite the 'Workflow' section as the actual executable sequence (validate input → query/search → optional download → report results with assumptions) with the rate-limit and API-failure checkpoints inline, and fix the non-portable 'cd "20260318/..."' example path.

DimensionReasoningScore

Conciseness

The ~260-line body is noticeably verbose with substantial template padding: a generic Security Checklist (12 unchecked boxes), Risk Assessment table, Lifecycle Status, Evaluation Criteria, Output Requirements, Error Handling, Input Validation, and Response Template sections that are boilerplate rather than FDA-search-specific knowledge, plus odd self-referential pointers ('See `## Features` above for related details', 'See `## Prerequisites` above') and a garbled trigger sentence ('the task needs Search FDA industry guidelines'). This matches 'Noticeably verbose; several unnecessary explanations or padded sections' rather than score 3's mostly-efficient baseline.

2 / 5

Actionability

Concrete, executable guidance is present: a full parameter table with defaults and required flags, three copy-paste-ready example invocations ('python scripts/main.py --area oncology'), a Quick Check ('python -m py_compile scripts/main.py'), and a worked JSON output example. Minor gaps keep it below 5: the Example Usage 'cd "20260318/scientific-skills/..."' path is a non-portable build-artifact path, and the 'Example run plan' mixes executable steps with abstract direction.

4 / 5

Workflow Clarity

A sequence exists and some validation checkpoints are present (py_compile quick check, --help inspection, Error Handling fallbacks), matching 'Steps listed but validation gaps'. However the numbered 'Workflow' section is generic governance prose ('Confirm the user objective...', 'switch to the fallback path') rather than the actual search workflow, and the network/ scraping path (rate-limited FDA API) lacks concrete retry/validation checkpoints, so it does not reach score 4's 'clear sequence with most checkpoints present'.

3 / 5

Progressive Disclosure

The three referenced files (references/search-strategy.md, references/area-mappings.json, references/fda-api-notes.md) all exist in the bundle and are clearly listed one level deep in a References section, and scripts/main.py exists. But significant content that belongs in separate files is inlined (risk table, security checklist, lifecycle, response template), the 'See `## X` above' cross-references are confusing non-standard navigation, and the body's cache location ('references/cache/') does not exist in the bundle — matching 'Some structure but could be better organized' rather than score 4.

3 / 5

Total

12

/

20

Passed

Description

53%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.

The description is clear, third-person, and honest about scope, with a well-defined FDA niche. It is held back by stating only one action, omitting natural trigger phrasing (notably 'FDA guidance', the FDA's own term), and lacking any 'use when' guidance for invocation.

Suggestions

Enumerate the concrete capabilities the skill actually has: e.g. 'Search FDA guidance documents by therapeutic area, filter by document type and year, download PDFs, and search within document content.'

Add an explicit trigger clause, e.g. 'Use when the user asks about FDA guidance/guidelines, regulatory requirements, or industry guidance for a therapeutic area.'

Include the synonym 'guidance' alongside 'guideline' (and optionally 'CDER/CBER') since FDA's own terminology and most user requests use 'guidance'.

DimensionReasoningScore

Specificity

The description names a concrete domain ('FDA industry guidelines', 'therapeutic area or topic') and one concrete action ('Search'), matching the anchor 'Names domain and 1-2 concrete actions, but not comprehensive' rather than score 4's 'several specific actions' since only a single action is stated.

3 / 5

Completeness

The 'what' is clear ('Search FDA industry guidelines by therapeutic area or topic') but there is no 'Use when...' clause or equivalent trigger guidance, which per the judging guidelines caps completeness at 3 — matching the anchor 'Has a clear what but when is missing or only weakly implied' rather than score 4 which requires an explicit when.

3 / 5

Trigger Term Quality

Relevant keywords exist ('Search', 'FDA', 'guidelines', 'therapeutic area', 'topic'), but common natural variations are missing — FDA officially publishes 'guidance' (not 'guideline') documents, and terms users would naturally say like 'FDA guidance', 'guidance documents', or 'CDER/CBER' are absent, fitting the 'some relevant keywords but missing common variations or synonyms' anchor.

3 / 5

Distinctiveness Conflict Risk

'FDA industry guidelines' is a clear, well-defined niche with distinct triggers (FDA, guidelines, therapeutic area), but there is minor overlap risk with closely related literature-search or regulatory-search skills, placing it at 'Mostly distinct; minor overlap risk' rather than the fully minimal-conflict anchor at 5.

4 / 5

Total

13

/

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

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

referenced_paths_exist

Referenced path issues: 2 missing

Warning

Total

14

/

16

Passed

Repository

aipoch/medical-research-skills

Path

scientific-skills/Evidence Insight/fda-guideline-search/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.