CtrlK
BlogDocsLog inGet started
Tessl Logo

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".

61

Quality

73%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

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

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 with concrete commands and templates and a clear sequenced workflow, but it is verbose (duplicated KDD config, repeated stubs, basic explanations) and lacks a verification step before destructive batch operations; everything is inlined in one large file with no reference split.

Suggestions

Add an explicit validation/verification step before cleanup completion, e.g. run a dry-run latex compile or verify main.tex resolves all \input and \bibliography paths, since the workflow performs destructive batch file removal.

De-duplicate the KDD 2026 acmart configuration — present it once and cross-reference it from the conference-types table — and collapse the five identical TODO section stubs into a single parameterized pattern.

Move time-sensitive version strings (neurips_2025, iclr2025_conference, aaai25, KDD 2026) into a clearly marked section so they do not penalize conciseness, or extract the README template and conference-types reference into a separate reference file to improve progressive disclosure.

DimensionReasoningScore

Conciseness

The ~510-line body is mostly useful but contains padding: the KDD 2026 acmart configuration is duplicated (Step 5 and the conference-types section), five near-identical TODO section stubs are inlined, and a basic file-type table plus time-sensitive version strings (neurips_2025, iclr2025_conference, aaai25, KDD 2026) appear without a deprecation section.

3 / 5

Actionability

It provides concrete, copy-paste-ready bash (unzip, find, mkdir, cp, grep, rm), full LaTeX main.tex and section-file templates, and a complete README template covering the common cases.

5 / 5

Workflow Clarity

Steps 1–7 are clearly sequenced with an explicit user-confirmation checkpoint, but there is no validation/verification step (e.g. a compile test or output-structure check) before the destructive batch cleanup (rm -f sample-*, rm -rf temp), which caps this dimension at 3 per the rubric.

3 / 5

Progressive Disclosure

No bundle files exist and all ~510 lines live in a single SKILL.md; section headers give some structure, but content that could be split out (README template, conference-types table, KDD config) is inlined with no one-level-deep references.

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: third-person, explicit what-and-when, with natural trigger phrases and a clearly distinct niche. The only weakness is that it names one compound action rather than enumerating several concrete capabilities.

DimensionReasoningScore

Specificity

"Organize messy conference LaTeX template .zip files into clean Overleaf-ready structure" names the domain plus one concrete compound action, but does not list multiple distinct concrete actions (e.g. extract, restructure, rename) so it is not comprehensive.

3 / 5

Completeness

It explicitly states what the skill does (organize conference LaTeX template zips into Overleaf-ready structure) and when to use it with concrete quoted trigger phrases, satisfying both halves of the anchor.

5 / 5

Trigger Term Quality

The "Use when" clause supplies natural trigger phrases ("organize LaTeX template", "clean up .zip template", "prepare Overleaf submission template") with the .zip extension, giving good coverage, though a few common variants (e.g. bare "LaTeX", "Overleaf project") are missing.

4 / 5

Distinctiveness Conflict Risk

The niche is narrow and specific (conference LaTeX template .zip → Overleaf) with distinct triggers, making overlap with other skills minimal.

5 / 5

Total

17

/

20

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

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