latex-conference-template-organizer

Organize messy conference LaTeX template .zip files into clean Overleaf-ready structure. Use when the user asks to "organize LaTeX template", "clean up .zip template", or "prepare Overleaf submission template".

Quality

73%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/latex-conference-template-organizer/SKILL.md

Quality

Content

65%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.

Highly actionable content with concrete commands and templates throughout, undermined by a missing post-cleanup compile-validation step, duplicated conference-specific configuration, and a monolithic single-file layout that inlines material better suited to reference files.

Suggestions

Add an explicit validation step after cleanup — e.g., run `latexmk -pdf output/main.tex` (or `pdflatex`) locally — and iterate on errors before reporting completion, instead of deferring compilation testing to the user on Overleaf.

Deduplicate the KDD 2026 anonymous-submission configuration: it appears almost verbatim in both Step 5 and the 'Common Conference Template Types' section; keep a single canonical version and cross-reference it.

Move per-conference configurations (the conference template table, KDD notes) and the README template into `references/` files, leaving SKILL.md as a lean workflow overview with one-level-deep pointers.

Dimension	Reasoning	Score
Conciseness	Mostly actionable commands, but the KDD 2026 anonymous configuration appears nearly verbatim twice (Step 5 and the 'Common Conference Template Types' section), and generic LaTeX how-to snippets (figure/table/reference examples) pad the body. Not 4 because the duplication and boilerplate are more than minor trimming; not 2 because the bulk is concrete instruction rather than explanation of known concepts.	3 / 5
Actionability	Copy-paste-ready bash commands for extraction, copying, and cleanup; complete LaTeX templates for main.tex, section files, and the KDD configuration; and a full README template. Not 4 because the common cases (ACM/acmart, main-file identification, output structure) are covered by executable, specific examples.	5 / 5
Workflow Clarity	A clear 7-step sequence with a user-confirmation checkpoint before destructive cleanup and an error-handling table, but no validation step verifying the cleaned template compiles — it defers testing to the user ('upload the output/ directory to Overleaf to test compilation'). Per the rubric guideline, a destructive/batch workflow without validation is capped at 3; not 2 because the sequence, checkpoints, and error handling are otherwise explicit.	3 / 5
Progressive Disclosure	The single SKILL.md is well-sectioned with clear step headers, but ~500 lines are inlined with no reference files at all — per-conference configurations and the README template clearly belong in separate reference files. Not 4 because content that should be split out (conference table, README template, KDD notes) is inline with no navigation to bundles; not 2 because the section structure itself is organized, not a wall of text.	3 / 5
	Total	14 / 20 Passed

Description

82%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.

A strong description with an explicit 'Use when...' clause carrying three natural quoted trigger phrases and a well-defined niche. The only gap is that the 'what' is a single compound action rather than an enumeration of the skill's concrete capabilities.

Dimension	Reasoning	Score
Specificity	The description names the domain ('conference LaTeX template .zip files') and one compound action ('Organize ... into clean Overleaf-ready structure'), but does not list multiple distinct concrete actions such as extracting, diagnosing, or restructuring. It is above anchor 2 because the action and target are concrete, but below anchor 4 because coverage of what the skill actually does is not enumerated.	3 / 5
Completeness	Explicitly answers both what ('Organize messy conference LaTeX template .zip files into clean Overleaf-ready structure') and when ('Use when the user asks to...') with three concrete trigger phrases, matching the top anchor. Not 4 because the when-clause is fully explicit with quoted triggers rather than merely present.	5 / 5
Trigger Term Quality	Includes three natural quoted trigger phrases ('organize LaTeX template', 'clean up .zip template', 'prepare Overleaf submission template') plus keywords LaTeX, Overleaf, and the .zip extension. Not a 5 because common variations such as 'submission template', 'camera-ready', or 'tidy up template' are missing.	4 / 5
Distinctiveness Conflict Risk	Occupies a clear niche (conference LaTeX template cleanup for Overleaf submission) with distinct trigger phrases unlikely to fire for other skills. Not 4 because nothing in the description overlaps meaningfully with general file, document, or PDF skills.	5 / 5
	Total	17 / 20 Passed

Validation

87%

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 — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
skill_md_line_count	SKILL.md is long (510 lines); consider splitting into references/ and linking	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	14 / 16 Passed

Repository: Galaxy-Dawn/claude-scholar
Path: skills/latex-conference-template-organizer/SKILL.md
Commit: 9037873

Reviewed: 2 days 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.