CtrlK
BlogDocsLog inGet started
Tessl Logo

latex-paper-conversion

This skill should be used when the user asks to convert an academic paper in LaTeX from one format (e.g., Springer, IPOL) to another format (e.g., MDPI, IEEE, Nature). It automates extraction, injection, fixing formatting, and compiling.

68

Quality

83%

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

The canonical home for this skill is latex-paper-conversion in administrakt0r/AI-Agents-Safe-Coding-Skills

SKILL.md
Quality
Evals
Security

Quality

Content

75%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 is a well-structured, mostly actionable guide for LaTeX paper conversion with a sensible workflow and validation loop. It could improve by including a runnable extraction-script skeleton and making the compile-retry loop an explicit checkpoint.

Suggestions

Provide a minimal runnable Python extraction-script skeleton (e.g., regex-based body extraction + preamble/body/backmatter merge) rather than only describing the script, to lift actionability to 5.

Make the compilation feedback loop an explicit validation checkpoint (e.g., "Repeat pdflatex→bibtex→pdflatex until the .log shows zero errors; only then report success") to strengthen workflow_clarity.

Trim the Overview paragraph's explanation of journal structural differences to a single line, since Claude already understands LaTeX template variation.

DimensionReasoningScore

Conciseness

The body is mostly lean and assumes LaTeX competence, but the Overview paragraph explaining that journals have different structural requirements is mild context that could be trimmed; efficient with minor over-explanation.

4 / 5

Actionability

Concrete LaTeX fixes (\begin{theorem}→\begin{Theorem}, tabular→tabularx, [h!]→[H]) and a pdflatex→bibtex→pdflatex build cycle give mostly executable guidance, but no runnable extraction-script template is provided, leaving minor gaps.

4 / 5

Workflow Clarity

A clear four-step sequence is present with a compile→log-check→fix feedback loop in Step 4; it is not 5 because the retry-until-clean loop is implied rather than stated as an explicit validation checkpoint with an error-recovery checklist.

4 / 5

Progressive Disclosure

Content is well-organized into Overview, When to Use, How It Works, Examples, Best Practices, and Pitfalls with a single external link; no bundle files exist so there is no nested-reference problem, but at ~60 lines with no separate reference files it is a solid 4 rather than a clean 5.

4 / 5

Total

16

/

20

Passed

Description

92%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 is strong: it clearly states a distinct niche, concrete capabilities, and explicit trigger conditions. Its only weakness is slightly limited keyword breadth (no .tex extension or "template" synonyms).

DimensionReasoningScore

Specificity

"automates extraction, injection, fixing formatting, and compiling" lists four concrete actions with comprehensive coverage, matching the score-5 anchor; not 4 because coverage is broad rather than having minor gaps.

5 / 5

Completeness

It explicitly states both what ("automates extraction, injection, fixing formatting, and compiling") and when ("when the user asks to convert an academic paper in LaTeX from one format ... to another") with concrete trigger phrases, matching the score-5 anchor.

5 / 5

Trigger Term Quality

Natural terms like "convert an academic paper in LaTeX" and publisher names (Springer, IPOL, MDPI, IEEE, Nature) give good coverage, but file extensions such as .tex and synonyms like "template"/"journal" are missing, so it stops short of 5.

4 / 5

Distinctiveness Conflict Risk

The niche—converting LaTeX papers between specific publisher templates—is highly distinct with minimal overlap risk against other skills.

5 / 5

Total

19

/

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.

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
administrakt0r/AI-Agents-Safe-Coding-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.