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 (compile, fix errors, verify), provides explicit trigger guidance with bilingual keywords, and occupies a clear niche. It uses proper third-person voice and follows the recommended pattern of 'what it does' followed by 'Use when...' with concrete trigger terms.
| 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 catalog, and some explanatory text could be more concise or split into reference files. The iterative fix loop pseudocode and some inline comments are slightly redundant given Claude's capabilities.
Suggestions
Move the venue requirements table to a separate reference file (e.g., VENUES.md) and link to it, reducing the main skill's token footprint.
Remove the pseudocode in Step 4 (the for loop) — the concept is already clear from the surrounding text and Claude doesn't need pseudocode for a simple retry loop.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is fairly comprehensive but includes some unnecessary verbosity — e.g., the pseudocode iterative fix loop in Step 4 adds little value since the concept is obvious, and the venue requirements table, while useful, adds significant length. Some explanations (like what latexmk does) are unnecessary for Claude. However, most content earns its place. | 2 / 3 |
Actionability | Excellent actionability throughout — concrete bash commands, specific error messages with exact fix instructions, executable code for page count verification, 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 3 error diagnosis, Step 4 iterative fix loop, Step 5 post-compilation checks, Step 6 page count verification). Includes feedback loops for error recovery and checklists for complex verification steps. The compile→check→fix→recompile loop is well-defined. | 3 / 3 |
Progressive Disclosure | The content is well-structured with clear headers and logical sections, but it's a long monolithic file (~200+ lines) with no references to external files for detailed content like the venue requirements table or the full error catalog. The venue table and detailed error patterns could be split into reference files. | 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
dc00dfb
- 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.