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

60%

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

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 delivers a clear, actionable conversion workflow with validation and well-signaled one-level references to real bundle files, but it is substantially verbose due to repeated restatement of the same rules across multiple sections. Tightening the redundancy would materially improve token efficiency without losing clarity.

Suggestions

Collapse the redundant rule restatements: merge Task, Core Function, Hard Rules, and What This Skill Should Not Do into a single concise rules section, since they overlap almost entirely.

Add one or two short worked examples (e.g. a sample LaTeX title-page block or a source-to-LaTeX mapping snippet) to lift actionability toward fully copy-paste-ready.

Move the long Scope Boundary / Important Distinctions material into a reference file and keep only a brief pointer in the body, improving progressive disclosure and conciseness together.

Dimension	Reasoning	Score
Conciseness	The same rules (do not invent template rules, preserve meaning, explain boundaries, request missing material) are restated across Task, Core Function, Execution, Hard Rules, and What This Skill Should Not Do, creating several redundant padded sections; it is noticeably verbose though it avoids explaining concepts Claude already knows.	2 / 5
Actionability	Concrete, specific guidance is provided throughout — an 8-step execution sequence and a mandatory A–H output structure with explicit sub-prompts — but there are no worked LaTeX examples or snippets, leaving minor gaps below fully copy-paste-ready.	4 / 5
Workflow Clarity	Steps 1–8 are clearly sequenced with an explicit validation checkpoint (clarify before converting, Input Validation section) and an output checklist (A–H structure), but the feedback loop is clarification rather than error-recovery, keeping it just below 5.	4 / 5
Progressive Disclosure	Seven reference files are listed and all exist, each signaled one level deep with a path and usage note; however the body itself is heavy and inlines significant redundant content that could be slimmer, so organization is good but not exemplary.	4 / 5
	Total	14 / 20 Passed

Description

61%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 states a clear, specific purpose but omits any "Use when..." trigger guidance and lacks synonyms/file extensions, capping completeness and trigger coverage. It is specific enough to be distinctive but not comprehensive.

Suggestions

Add an explicit "Use when..." clause naming concrete triggers (e.g. "Use when converting a manuscript to LaTeX for journal or conference submission, adapting a draft to a target template, or cleaning up LaTeX for resubmission").

Include natural synonyms and file extensions such as "paper", "submission", ".tex", and ".cls" to improve trigger-term coverage.

Enumerate two or three concrete actions (e.g. convert, restructure, clean up) rather than a single conversion action to lift specificity toward 5.

Dimension	Reasoning	Score
Specificity	The description names the domain and one concrete action — "Converts existing manuscript content into LaTeX format aligned with a target journal, conference, or template" — but does not enumerate multiple distinct actions, so it falls short of the "several specific actions" anchor at 4.	3 / 5
Completeness	The "what" is clear (convert manuscript content into submission-oriented LaTeX), but there is no "Use when..." clause or equivalent explicit trigger guidance, which caps completeness at 3 per the rubric guideline.	3 / 5
Trigger Term Quality	Natural terms a user would say are present ("manuscript", "LaTeX", "journal", "conference", "template"), but synonyms (e.g. "paper", "submission") and file extensions (.tex, .cls) are missing, keeping it just below comprehensive.	4 / 5
Distinctiveness Conflict Risk	The niche (LaTeX manuscript conversion for journals/conferences/templates) is mostly distinct with only minor overlap risk against general LaTeX or document-conversion skills, but the absence of explicit trigger phrases keeps it below 5.	4 / 5
	Total	14 / 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: awesome-med-research-skills/Academic Writing/latex-manuscript-format-converter/SKILL.md
Commit: f5ef65b

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