Content
32%Scale 1-5Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill reads more like a feature overview or documentation landing page than an actionable skill file. It spends significant tokens on capability enumeration and generic best practices while lacking validation steps for its batch and XML-manipulation workflows. The code examples, while present, are incomplete in terms of error handling and practical usability.
Suggestions
Remove the 'Core Capabilities' bullet list and 'When to Use This Skill' section entirely — they describe what the skill does rather than instructing Claude how to do it.
Add explicit validation steps to the template-based generation workflow (e.g., validate the modified content.xml, verify the output ZIP is a valid ODP) and add error handling to the batch conversion loop.
Replace the generic 'Best Practices' list with specific, actionable guidance tied to common failure modes (e.g., 'Always kill existing soffice processes before starting headless conversion to avoid port conflicts').
Split the UNO scripting details and format conversion reference into separate bundle files, keeping SKILL.md as a concise overview with clear pointers.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is noticeably verbose with sections like 'When to Use This Skill' listing obvious use cases, 'Core Capabilities' that merely enumerate features without adding actionable value, and 'Best Practices' that are generic advice Claude already knows. The bulleted capability lists are padding that could be eliminated. | 2 / 5 |
Actionability | There are some concrete code examples (conversion commands, UNO script, template generation), but the UNO example is questionable in practice (requires a running LibreOffice instance with socket), the template generation lacks validation, and many sections are just descriptive bullet lists without executable guidance. The command-line reference section is redundant with earlier examples. | 3 / 5 |
Workflow Clarity | Workflows are loosely presented without clear sequencing or validation checkpoints. The batch conversion loop has no error handling or validation. The template-based generation manipulates XML (a fragile operation) with no validation step after modification, and the UNO workflow doesn't verify the socket connection is available before proceeding. Per rubric guidelines, missing feedback loops for batch and XML manipulation operations should cap this at 3, and the actual content falls below even that threshold. | 2 / 5 |
Progressive Disclosure | No bundle files are provided, yet the skill is ~150 lines with inlined content that could benefit from separation (e.g., UNO API examples, format conversion reference). The 'Core Capabilities' section is a wall of bullet points that adds no navigational value. References to external docs exist but there's no structured layering of content. | 2 / 5 |
Total | 9 / 20 Passed |