CtrlK
BlogDocsLog inGet started
Tessl Logo

medical-translation

Use medical translation for academic writing workflows that need structured execution, explicit assumptions, and clear output boundaries.

42

Quality

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

Quality

Content

35%

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

The skill body is functional with real scripts and a usable example, but it is bloated with redundant and boilerplate content, weak on the primary translation command, and poorly structured for progressive disclosure. Most dimensions land at 2 with conciseness at 1.

Suggestions

Strip the repeated description and generic boilerplate (Security Checklist, Risk Assessment, Evaluation Criteria, Lifecycle Status); keep only sections that add skill-specific guidance.

Show the actual translation command that maps to the example, e.g. `python scripts/main.py "Acute Myeloid Leukemia" English Chinese`, and remove the duplicated smoke_test.py line.

Move detailed audit/risk/security material into references/ and fix the broken "See above" cross-references so the SKILL.md is a lean overview pointing one level deep.

DimensionReasoningScore

Conciseness

The body is heavily padded: the description is repeated verbatim multiple times ("Use medical translation for academic writing workflows..." appears in When to Use and Key Features), and it carries generic boilerplate (Security Checklist, Risk Assessment, Evaluation Criteria, Lifecycle Status) plus empty cross-references ("See `## Prerequisites` above") that add no skill-specific value.

1 / 3

Actionability

It gives concrete, executable commands (py_compile, smoke_test.py) and a concrete input/output example, but the actual translation invocation that produces the example output is never shown, and the Audit-Ready Commands section duplicates `python scripts/smoke_test.py` twice.

2 / 3

Workflow Clarity

The Workflow section lists a clear 5-step sequence with a scope-validation stop and a fallback path, plus a Quick Check verification command, but the checkpoints are mostly governance/scope checks rather than concrete validation of the translation output.

2 / 3

Progressive Disclosure

The single reference (references/audit-reference.md) and the scripts are real and one level deep, but the body itself is a monolithic 25-section document with inline boilerplate that should be split out, and the "See `## X` above" cross-references point to sections that appear later, making navigation confusing.

2 / 3

Total

7

/

12

Passed

Description

50%

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 identifies a real niche but is padded with abstract process language instead of concrete actions and natural trigger terms. It answers what and when only weakly, capping most dimensions at the 2 level.

Suggestions

Replace abstract qualifiers ("structured execution, explicit assumptions, clear output boundaries") with concrete translation actions, e.g. "Translate medical terms and passages between language pairs such as Chinese-English and Spanish-English".

Add a natural trigger clause like "Use when the user asks to translate medical terminology, drug names, or clinical text for academic writing."

Include common variations users would say ("medical terms", "terminology translation", specific language pairs) to improve trigger coverage and distinctiveness.

DimensionReasoningScore

Specificity

It names the domain and a single action ("medical translation") but pads the rest with abstract process qualities ("structured execution, explicit assumptions, and clear output boundaries") rather than listing concrete translation actions, so it is not comprehensive enough for a 3.

2 / 3

Completeness

It states what the skill does (medical translation) and includes a "Use ... for" trigger clause, but the "when" portion describes abstract workflow qualities rather than concrete natural triggers, so it does not clearly answer both what and when at the 3 level.

2 / 3

Trigger Term Quality

"medical translation" and "academic writing" are natural terms, but the phrase "structured execution, explicit assumptions, and clear output boundaries" is not something a user would say, and common variations like "translate medical terms", "terminology", or language pairs are missing.

2 / 3

Distinctiveness Conflict Risk

"medical translation for academic writing" is a recognizable niche, but it could still overlap with a general translation skill and the abstract qualifiers dilute the distinct trigger signal.

2 / 3

Total

8

/

12

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.

Validation15 / 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
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.