paper-compile
Compile LaTeX paper to PDF, fix errors, and verify output. Use when user says \"编译论文\", \"compile paper\", \"build PDF\", \"生成PDF\", or wants to compile LaTeX into a submission-ready PDF.
90
88%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Quality
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a strong skill description that concisely covers specific capabilities, includes bilingual trigger terms, and clearly delineates both what the skill does and when it should be used. The LaTeX compilation focus gives it a clear, distinct niche. The use of third person voice and explicit 'Use when' clause follow best practices.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Compile LaTeX paper to PDF', 'fix errors', and 'verify output'. These are clear, actionable capabilities. | 3 / 3 |
Completeness | Clearly answers both 'what' (compile LaTeX to PDF, fix errors, verify output) and 'when' (explicit 'Use when' clause with specific trigger phrases and a general condition about compiling LaTeX). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms in both English and Chinese: '编译论文', 'compile paper', 'build PDF', '生成PDF', 'compile LaTeX', 'submission-ready PDF'. These are terms users would naturally say. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive niche targeting LaTeX paper compilation specifically. The combination of LaTeX, PDF compilation, and academic paper context makes it very unlikely to conflict with other skills like general PDF manipulation or generic document processing. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a strong, highly actionable skill with excellent workflow clarity and concrete executable guidance for LaTeX compilation. Its main weakness is length — the venue requirements table, detailed error patterns, and submission readiness checks could be split into referenced files to improve token efficiency. The iterative fix loop with rescue mechanism and explicit validation checkpoints demonstrate thoughtful workflow design.
Suggestions
Move the venue requirements table to a separate VENUES.md reference file and link to it, reducing the main skill's token footprint.
Move the detailed error diagnosis patterns (Step 3) to a separate LATEX_ERRORS.md file, keeping only a brief summary in the main skill with a reference link.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is fairly comprehensive but includes some unnecessary verbosity — e.g., the installation instructions for LaTeX (Claude can figure this out), the explanation of what latexmk does, and the venue requirements table which could be a separate reference file. However, most content is genuinely useful and not padded with basic concept explanations. | 2 / 3 |
Actionability | Excellent actionability throughout — concrete bash commands, specific error messages with exact fix instructions, executable Python snippets for page counting, and copy-paste ready compilation commands. The error diagnosis section maps specific log messages to specific fixes. | 3 / 3 |
Workflow Clarity | Clear 8-step sequential workflow with explicit validation checkpoints (Step 5 post-compilation checks, Step 6 page count verification), an iterative fix loop with MAX_COMPILE_ATTEMPTS, and a rescue mechanism (RESCUE_ON_REPEAT_FAILURE) for persistent failures. The checklist format in Steps 5 and 7 provides clear verification gates. | 3 / 3 |
Progressive Disclosure | The content is well-structured with clear sections and headers, but it's a long monolithic file (~200 lines) that could benefit from splitting the venue requirements table and detailed error diagnosis into separate reference files. No external file references are used despite the content length warranting it. | 2 / 3 |
Total | 10 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Commit
700fbe2
- 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.