ectd-xml-compiler

Automatically convert uploaded drug application documents (Word/PDF) into XML skeleton structure compliant with eCTD 4.0/3.2.2 specifications.

Quality

48%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./scientific-skills/Academic Writing/ectd-xml-compiler/SKILL.md

Quality

Content

42%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 contains genuine, actionable eCTD CLI documentation and structure guidance, but it is buried under heavy templated boilerplate and inconsistent cross-references. Validation is documented as an option rather than integrated as a workflow checkpoint.

Suggestions

Remove generic templated filler (Risk Assessment, Security Checklist, Lifecycle Status, Evaluation Criteria, Response Template) or move it to a separate reference file, keeping SKILL.md a lean overview.

Fix the broken/placeholder cross-references (e.g., 'See ## Usage above', 'See ## Workflow above') and reconcile the two conflicting command paths (scripts/main.py vs skills/ectd-xml-compiler/scripts/main.py).

Promote validation into the workflow itself as an explicit checkpoint ('generate XML, then run --validate, only proceed if valid') to lift workflow clarity past the batch-operation cap.

Dimension	Reasoning	Score
Conciseness	The body is noticeably verbose, padded with templated boilerplate (Risk Assessment, Security Checklist, Lifecycle Status, Evaluation Criteria) and mismatched 'When to Use' text that does not earn its context-window cost.	2 / 5
Actionability	A real CLI interface with arguments/options tables and runnable examples is documented, but inconsistent command paths, placeholder filenames, and broken cross-references ('See ## Usage above') leave gaps.	3 / 5
Workflow Clarity	A sequenced workflow with a fallback path is present, but the batch/file-writing operation lacks an inline validation checkpoint, capping workflow clarity at 3 per the rubric.	3 / 5
Progressive Disclosure	Real one-level-deep references (references/audit-reference.md, scripts/main.py) are signaled, but large amounts of boilerplate that belong in separate files are inlined, weakening organization.	3 / 5
	Total	11 / 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 clearly conveys a specific regulatory niche and a concrete core action, but it omits any explicit 'when to use' trigger guidance and is somewhat jargon-heavy. It is distinct yet not fully self-activating.

Suggestions

Add a 'Use when ...' clause naming concrete trigger phrases (e.g., 'Use when preparing eCTD submissions, converting NDA/BLA documents, or generating Module 1-5 XML skeletons').

Include file extensions and synonyms (e.g., '.docx', '.pdf', 'NDA', 'BLA', 'regulatory submission') to broaden natural trigger coverage.

List 1-2 additional concrete actions (e.g., 'validate generated XML against DTDs') to lift specificity beyond a single action.

Dimension	Reasoning	Score
Specificity	Names the domain (drug application documents, Word/PDF, eCTD) and one concrete action ('convert ... into XML skeleton structure'), but lists only a single action rather than multiple specific actions.	3 / 5
Completeness	The 'what' is stated clearly, but there is no 'Use when...' clause or equivalent trigger guidance, capping completeness at 3 per the rubric guidelines.	3 / 5
Trigger Term Quality	Relevant niche terms ('eCTD', 'drug application documents', 'Word/PDF', 'XML skeleton') are present, but the phrasing is jargon-heavy and misses common synonyms and file extensions users might say.	3 / 5
Distinctiveness Conflict Risk	The eCTD regulatory XML niche is clearly distinct with minimal overlap risk, though the absence of an explicit trigger phrase keeps it just below the top anchor.	4 / 5
	Total	13 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
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/ectd-xml-compiler/SKILL.md
Commit: 63c61d3

Reviewed: 7 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.