CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

regulatory-submission

Prepare FDA/EMA regulatory submissions (IND/NDA/BLA/510(k)/PMA/MAA) in CTD format. Generate module outlines (Modules 1-5), run ICH compliance checks (ALCOA+, E6 GCP, Q1-Q12), verify data integrity, and produce submission-ready dossiers with cover letters and checklists.

Quality

73%

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/Academic Writing/regulatory-submission/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

60%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 is well-structured with a clearly sequenced workflow, explicit checkpoint, and good error handling. It is weakened by redundant content (Key Principles duplicating the workflow, explanatory table columns) and high-level drafting guidance lacking concrete templates or examples.

Suggestions

Remove the redundant "Key Principles" section (its ICH and ALCOA+ content already appears in workflow steps 4-5) and drop the "Purpose" column from the FDA table to tighten token usage.

Add a concrete example — e.g. a sample Module 2 outline skeleton or a short checklist template — so the drafting steps (2-3) have executable guidance rather than high-level direction.

Add an explicit feedback loop after compliance gaps are found, e.g. "remediate critical gaps, then re-run the compliance check until no critical gaps remain."

DimensionReasoningScore

Conciseness

Mostly efficient, but the "Key Principles" section re-states "Follow ICH guidelines (E6 GCP, Q1-Q12)" and ALCOA+ already given in workflow steps 4-5, and the FDA table's "Purpose" column ("Investigational New Drug", "Device clearance", etc.) explains concepts Claude already knows — some unnecessary explanation beyond the 'minor instances' of anchor 4.

3 / 5

Actionability

Workflow steps have defined Input/Output and the Submission Types and CTD Format tables are concrete, but drafting guidance stays high-level — no example Module 2 outline, checklist template, or sample cover letter is provided, leaving key execution details missing.

3 / 5

Workflow Clarity

A clear 6-step sequence with validation steps ("Verify data integrity", "Run compliance check") and an explicit "⛔ Checkpoint: Review gaps with user, prioritize remediation" plus "If Data Incomplete" error handling; however, there is no explicit fix-and-revalidate feedback loop after remediation, so it falls short of anchor 5.

4 / 5

Progressive Disclosure

Well-organized sections with no dangling references (no bundle files exist to reference), though the reference-style Submission Types table and CTD Format section could be externalized to keep the overview leaner — good structure with minor organization gaps.

4 / 5

Total

14

/

20

Passed

Description

75%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, specific description with comprehensive action coverage and domain-native trigger terms. Its main weakness is the absence of an explicit "Use when..." trigger clause, and it misses a few natural synonyms like "eCTD" and "regulatory affairs".

Suggestions

Append a "Use when..." clause, e.g. "Use when the user mentions FDA, EMA, regulatory submissions, eCTD, IND, NDA, BLA, 510(k), dossier, or regulatory affairs."

Add common natural synonyms such as "eCTD", "regulatory affairs", and "clinical trial application (CTA)" to broaden trigger coverage.

DimensionReasoningScore

Specificity

The description lists multiple specific concrete actions — "Generate module outlines (Modules 1-5)", "run ICH compliance checks (ALCOA+, E6 GCP, Q1-Q12)", "verify data integrity", "produce submission-ready dossiers with cover letters and checklists" — comprehensively covering the submission workflow from outline to final package.

5 / 5

Completeness

The "what" is clear and detailed, but there is no "Use when..." clause or equivalent explicit trigger guidance, which caps completeness at 3 per the judging guidelines.

3 / 5

Trigger Term Quality

Strong natural domain keywords (FDA, EMA, IND, NDA, BLA, 510(k), PMA, CTD, dossier) that users would actually say, but a few common variations are missing such as "eCTD", "regulatory affairs", and "clinical trial application".

4 / 5

Distinctiveness Conflict Risk

It occupies a clear regulatory-affairs niche with distinct trigger vocabulary (specific submission types, CTD, ICH); minimal risk of triggering for the wrong skill.

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/Academic Writing/regulatory-submission/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.