CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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

62%

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/ectd-xml-compiler/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 skill has a solid executable core — usage tables, realistic examples, a real script and reference file, and built-in validation options. But the body is heavily padded with generated template boilerplate, repeats its own description multiple times, contains internal contradictions (Dependencies vs. Prerequisites, two different script paths), and buries its actual workflow under generic process text.

Suggestions

Delete the template boilerplate sections (Key Features, Risk Assessment, Security Checklist, Evaluation Criteria, Lifecycle Status, Output Requirements) and the duplicated description in When to Use/Overview — they consume context without adding skill-specific knowledge.

Replace the generic Workflow section with the script's real pipeline (parse input → auto-detect module via keyword rules → generate module XML + index.xml + MD5 → run `--validate`, fix and re-validate on DTD errors) as an explicit numbered sequence with the existing validate command as a checkpoint.

Fix the contradictions: unify the script path across sections (`scripts/main.py` vs. `skills/ectd-xml-compiler/scripts/main.py`) and reconcile Dependencies (python-docx, PyPDF2, lxml) with the Prerequisites claim that no packages are required.

DimensionReasoningScore

Conciseness

The body repeats the description verbatim three times ("When to Use", "Key Features", "Overview") and carries several padded template sections ("Key Features", "Risk Assessment", "Security Checklist", "Evaluation Criteria", "Lifecycle Status") that a competent model needs no instruction on. Not score 1: genuinely useful, non-derivable content remains (usage/options tables, module auto-recognition rules, eCTD directory layout). Not score 3: the volume of boilerplate and duplication goes well beyond a few trimmable spots — entire sections could be deleted.

2 / 5

Actionability

Concrete, executable guidance dominates the useful parts: a usage line, argument/options tables with defaults, four realistic example commands, and a Quick Check (`python -m py_compile scripts/main.py`). Not score 5: the example commands use the inconsistent path `skills/ectd-xml-compiler/scripts/main.py` while the Example Usage section cds into `20260318/scientific-skills/Academic Writing/ectd-xml-compiler`, so commands are not copy-paste ready without adjustment. Not score 3: the commands and tables are real and complete enough to run, not high-level hints or pseudocode.

4 / 5

Workflow Clarity

The "Workflow" section is generic template boilerplate ("confirm the user objective... return a structured result") rather than the actual parse→classify→generate→validate sequence, and the "Example Usage" section self-references "See `## Usage` above". Checkpoints do exist elsewhere (py_compile Quick Check, `--validate` for DTD validation), but for an XML/document-manipulation skill there is no validate→fix→retry feedback loop, capping workflow clarity at 3 per the rubric's feedback-loop note. Not score 2: runnable commands and some validation steps are present, so the sequence is not wholly absent.

3 / 5

Progressive Disclosure

The bundle is one level deep and real: `references/audit-reference.md` (linked in the body, exists on disk) and `scripts/main.py` (referenced throughout). However, the ~310-line body inlines large blocks that belong in reference files or nowhere — Risk Assessment, Security Checklist, Evaluation Criteria, Lifecycle Status — and the single reference link is buried near the end, while the Dependencies section contradicts Prerequisites ("No additional Python packages required"). Not score 4: significant content that should be split out or removed is inlined and navigation between sections is muddied by duplicate/self-referential headers. Not score 2: the document does have clear section headers and a valid, one-level-deep reference.

3 / 5

Total

12

/

20

Passed

Description

57%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 has a clear, concrete "what" anchored in a well-defined regulatory niche, giving it strong distinctiveness and reasonable specificity. Its main weakness is the complete absence of a "Use when..." trigger clause and the lack of natural synonyms and file extensions, which limits both completeness and trigger-term quality.

Suggestions

Append an explicit trigger clause, e.g. "Use when converting regulatory submission documents (.docx, .pdf) into eCTD 4.0 or 3.2.2 XML skeletons for FDA/EMA/ICH filings."

Add natural user phrasings and file extensions such as ".docx", ".pdf", "eCTD submission", and "regulatory submission" to broaden trigger coverage.

Consider mentioning secondary capabilities already implemented by the script (module auto-recognition, MD5 checksums, DTD validation) to raise specificity from one action to several.

DimensionReasoningScore

Specificity

"Automatically convert uploaded drug application documents (Word/PDF) into XML skeleton structure compliant with eCTD 4.0/3.2.2 specifications" names the domain and one concrete action (convert documents to an eCTD-compliant XML skeleton) with input formats and target standards. Not score 4: it lists only a single action, so coverage is not comprehensive (no mention of validation, checksums, or module mapping in the description itself). Not score 2: the action and domain are concrete, not generic.

3 / 5

Completeness

The description clearly answers "what" (converts Word/PDF drug application documents into eCTD 4.0/3.2.2 XML skeletons) but contains no "Use when..." clause or equivalent explicit trigger guidance, capping completeness at 3 per the judging guidelines. Not score 4: the "when" is entirely absent, not merely implicit-but-present; not score 2: the "what" is specific and unambiguous.

3 / 5

Trigger Term Quality

Relevant keywords are present ("drug application documents", "Word/PDF", "XML", "eCTD"), which a regulatory-submission user would say. Not score 4: common variations and synonyms are missing — no file extensions (.docx, .pdf) and no natural phrases like "regulatory submission" or "convert to eCTD". Not score 2: the terms are domain-relevant rather than generic filler.

3 / 5

Distinctiveness Conflict Risk

"eCTD 4.0/3.2.2 specifications" and "drug application documents" carve out a clear niche (regulatory eCTD submission packaging) with distinct triggers; no other common skill would fire on these phrases. Not score 4: the eCTD/regulatory qualifier is specific enough that even generic document-conversion skills would not plausibly conflict.

5 / 5

Total

14

/

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/ectd-xml-compiler/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.