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

64

Quality

77%

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%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A highly actionable, well-structured workflow with concrete commands and templates, held back by duplicated KDD configuration content, missing validation checkpoints around destructive/batch operations, and an absence of progressive disclosure for a skill of this size.

Suggestions

De-duplicate the KDD 2026 anonymous-submission configuration: keep it in one place and cross-reference it from the other section.

Add a verification step before cleanup (e.g., attempt a test compile of main.tex and only run `rm -rf` on the temp dir after the output is confirmed valid) to satisfy the validation requirement for destructive/batch operations.

Move the conference template-types table and the README template into reference files (e.g., CONFERENCES.md, README_TEMPLATE.md) referenced one level deep from SKILL.md to improve progressive disclosure.

DimensionReasoningScore

Conciseness

The body is mostly lean and actionable with no padding about concepts Claude already knows, but the KDD 2026 anonymous-submission configuration appears twice in near-identical code blocks (Step 5 and the Common Conference Template Types section) and the bracketed README template is verbose, so it could be tightened.

2 / 3

Actionability

It provides fully executable bash commands (unzip, find, mkdir, cp, rm), complete LaTeX templates for main.tex and section files, a copy-paste example-table.tex heredoc, and a concrete README template — all specific and ready to apply.

3 / 3

Workflow Clarity

Steps 1–7 are clearly sequenced with an explicit user-confirmation checkpoint and an Error Handling table, but the destructive `rm -rf` cleanup and batch `rm -f sample-*` deletions lack a validation step, and there is no compile-to-verify check before declaring output complete.

2 / 3

Progressive Disclosure

The skill is organized into clear sections, but it is a single ~500-line monolithic SKILL.md with no bundle files and no external references; substantial reference-style content (per-conference configs, the README template) that could live in separate files is inline.

2 / 3

Total

9

/

12

Passed

Description

90%

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 well-crafted description with explicit trigger phrasing and a clear, distinctive niche; its only weakness is that the action verbs are somewhat general rather than enumerating multiple concrete operations.

Suggestions

Expand the action list with specific concrete verbs (e.g., "extract, identify the main file, strip example content, split sections, and restructure for Overleaf") to raise specificity.

Consider adding a natural trigger variation mentioning "Overleaf" project setup to broaden trigger coverage.

DimensionReasoningScore

Specificity

The description names a concrete domain ("conference LaTeX template .zip files") and a clear transformation ("into clean Overleaf-ready structure"), but relies on general verbs like "organize" rather than enumerating multiple distinct concrete actions, so it stops short of a comprehensive action list.

2 / 3

Completeness

It explicitly states both what the skill does (organize messy .zip templates into Overleaf-ready structure) and when to use it via an explicit "Use when..." trigger clause, satisfying both halves of the completeness criterion.

3 / 3

Trigger Term Quality

It provides several natural phrasings a user would actually say ("organize LaTeX template", "clean up .zip template", "prepare Overleaf submission template"), giving good coverage of the common ways this request is expressed.

3 / 3

Distinctiveness Conflict Risk

The niche (conference LaTeX template .zip to Overleaf submission) is narrow and the triggers are specific enough that this skill is unlikely to fire for unrelated LaTeX or file-organization tasks.

3 / 3

Total

11

/

12

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.