CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

latex-manuscript-format-converter

Converts existing manuscript content into LaTeX format aligned with a target journal, conference, or template while preserving manuscript meaning and structural integrity.

Quality

57%

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 ./awesome-med-research-skills/Academic Writing/latex-manuscript-format-converter/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

45%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 clearly sequenced workflow with explicit validation checkpoints and a genuinely well-wired one-level-deep reference bundle, but the body is heavily redundant (whole sections and reference files restated inline) and contains no concrete LaTeX examples, leaving the actual conversion guidance abstract. It would benefit most from consolidation and from concrete source-to-LaTeX mapping examples.

Suggestions

Cut duplicated sections: remove 'Hard Rules' (verbatim in references/hard-rules.md), fold 'Core Function' into 'Task', fold 'What This Skill Should Not Do' into 'Scope Boundary', and let references/clarification-first-rule.md carry the Input Validation content.

Add concrete source-to-LaTeX mapping examples in references/structure-conversion-rules.md or a short inline example (e.g., Word heading '1.1 Results' → \subsection{Results}; figure caption → \begin{figure}...\caption{}), and show a minimal skeleton (\documentclass, \title, \author, abstract, bibliography) to anchor the target-template discussion.

Specify bibliography handling options concretely (e.g., .bst/.bib availability determines \bibliography{...} vs a manual thebibliography conversion) under the compile-boundary discussion.

DimensionReasoningScore

Conciseness

The ~280-line body is pervasively redundant: 'Task' vs 'Core Function', 'Scope Boundary' vs 'What This Skill Should Not Do', 'Hard Rules' duplicated verbatim from references/hard-rules.md, and 'Input Validation' repeating both Execution Step 1 and references/clarification-first-rule.md. This matches 'noticeably verbose; several unnecessary explanations or padded sections'; it is not 1 because it never explains basic concepts Claude already knows.

2 / 5

Actionability

There is no concrete LaTeX anywhere — no source-to-LaTeX mapping example (e.g., a Word heading becoming \section{}), no sample \title{}/\author{}/abstract block, and no bibliography handling specifics; guidance stays at the level of 'State how the manuscript should be organized in LaTeX.' This matches 'minimal concrete guidance; high-level hints but missing the specific steps to execute'; the mandatory A-H output template is the only concrete scaffold, keeping it above 1.

2 / 5

Workflow Clarity

The Execution section gives a coherent 8-step sequence (clarify → identify target → identify source → map components → define scope → check boundaries → explain → produce output) with an explicit upfront validation checkpoint (Step 1 'Clarify before converting' plus the 'Input Match Check' output section). It is not 5 because there is no feedback loop or re-check after the final output is produced.

4 / 5

Progressive Disclosure

Seven reference files all exist, are one level deep, and are clearly signaled under 'Reference Module Integration' with a purpose for each; however, the body inlines duplicated reference content (the verbatim Hard Rules copy, Input Validation duplicating clarification-first-rule.md) instead of purely pointing to the files, which is the minor organization gap that keeps it below 5.

4 / 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 gives a clear, correctly third-person statement of what the skill does and carves out a distinct niche, but it entirely lacks 'when to use it' trigger guidance and misses common trigger terms like '.tex', 'Word', and 'submission'. Adding a 'Use when...' clause would address the completeness cap and likely lift trigger-term quality.

Suggestions

Append a 'Use when' clause with concrete triggers, e.g. 'Use when the user wants to convert a manuscript (Word, plain text, or LaTeX draft) into journal or conference LaTeX format, adapt a draft to a target template, or clean up LaTeX for submission.'

Include common trigger terms and file extensions users would naturally say: '.tex', 'Word', 'reformat', 'resubmission', 'submission-ready'.

Enumerate 2-3 more concrete actions (e.g., converts title page, abstract, sections, captions, and references into template-aligned LaTeX) to raise specificity.

DimensionReasoningScore

Specificity

The description names the domain ('LaTeX format') and one concrete action ('Converts existing manuscript content into LaTeX format aligned with a target journal, conference, or template') plus a preservation qualifier, but does not enumerate the concrete conversion actions (title page, abstract, sections, references, equations). It matches the 'names domain and 1-2 concrete actions, but not comprehensive' anchor rather than the 'several specific actions' of 4.

3 / 5

Completeness

The 'what' is clear (converts manuscript content into journal/conference-aligned LaTeX), but there is no 'Use when...' clause or equivalent trigger guidance at all, which the guidelines cap at 3; this matches the 'clear what but when is missing' anchor exactly.

3 / 5

Trigger Term Quality

Terms like 'manuscript', 'LaTeX', 'journal', 'conference', and 'template' are natural user phrasings, but common variations users would actually say — '.tex', 'Word', 'reformat', 'submission' — are absent, matching the 'some relevant keywords but missing common variations or synonyms' anchor.

3 / 5

Distinctiveness Conflict Risk

The journal/conference/template LaTeX-conversion niche is mostly distinct with only minor overlap risk against generic document-conversion or LaTeX-authoring skills; it lacks the explicit trigger phrasing that would merit a 5.

4 / 5

Total

13

/

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

awesome-med-research-skills/Academic Writing/latex-manuscript-format-converter/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.