office
Generate Office documents (DOCX, XLSX, PDF, PPTX) with TypeScript. Pure JS libraries that work everywhere: Claude Code CLI, Cloudflare Workers, browsers. Uses docx (Word), xlsx/SheetJS (Excel), pdf-lib (PDF), pptxgenjs (PowerPoint). Use when: creating invoices, reports, spreadsheets, presentations, form filling, exporting data to Office formats, or troubleshooting "Packer.toBuffer", "XLSX.utils", "PDFDocument", "pptxgenjs" errors.
84
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
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 an excellent skill description that hits all the key criteria. It provides specific capabilities, comprehensive trigger terms including both user-facing concepts and developer-specific library names, explicit 'Use when' guidance, and clear distinctiveness through its focus on TypeScript-based Office document generation with named libraries.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Generate Office documents (DOCX, XLSX, PDF, PPTX)', 'creating invoices, reports, spreadsheets, presentations, form filling, exporting data'. Also specifies the technology stack (docx, xlsx/SheetJS, pdf-lib, pptxgenjs) and runtime environments. | 3 / 3 |
Completeness | Clearly answers both 'what' (generate Office documents with TypeScript using specific libraries) AND 'when' with an explicit 'Use when:' clause covering use cases (invoices, reports) and troubleshooting scenarios with specific error terms. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: file extensions (DOCX, XLSX, PDF, PPTX), document types (invoices, reports, spreadsheets, presentations), actions (form filling, exporting data), and specific library names/error patterns that developers would search for. | 3 / 3 |
Distinctiveness Conflict Risk | Clear niche focused on Office document generation with TypeScript/JS libraries. The specific library names (docx, xlsx/SheetJS, pdf-lib, pptxgenjs) and error patterns create distinct triggers unlikely to conflict with general document or coding skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
72%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, actionable skill with excellent code examples covering four document formats across multiple runtime environments. The main weaknesses are moderate verbosity (some explanatory text Claude doesn't need) and missing validation steps in workflows. The progressive disclosure and organization are exemplary for a comprehensive multi-library skill.
Suggestions
Trim 'Key Concepts' sections - Claude understands builder patterns and page-based approaches; jump straight to code examples
Add validation checkpoints to workflows, e.g., 'After generating, verify: 1) File size > 0, 2) Opens without error in target app, 3) Content renders as expected'
Consider moving the compatibility comparison table and 'Limitations vs Anthropic's Official Skills' to a separate reference file to reduce main skill length
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is comprehensive but includes some unnecessary explanations (e.g., explaining what each library does when the code examples are self-evident). The compatibility tables and feature comparisons add value, but sections like 'Key Concepts' explaining basic patterns Claude already knows could be trimmed. | 2 / 3 |
Actionability | Excellent executable code throughout - every example is copy-paste ready with proper imports, complete function calls, and multiple export patterns for different environments (Node.js, Browser, Workers). The Quick Start sections provide working code in 30 seconds as promised. | 3 / 3 |
Workflow Clarity | While individual code examples are clear, the skill lacks explicit validation checkpoints. For document generation workflows, there's no guidance on verifying output correctness (e.g., 'open the file to confirm it renders correctly' or error handling patterns). The 'Known Issues Prevention' section helps but is reactive rather than integrated into workflows. | 2 / 3 |
Progressive Disclosure | Well-structured with clear hierarchy: Quick Start → detailed sections per format → Workers integration → troubleshooting. References to templates/, references/, and scripts/ directories provide one-level-deep navigation. The table of contents via headers makes navigation easy. | 3 / 3 |
Total | 10 / 12 Passed |
Validation
75%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 12 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
skill_md_line_count | SKILL.md is long (903 lines); consider splitting into references/ and linking | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
license_field | 'license' field is missing | Warning |
body_steps | No step-by-step structure detected (no ordered list); consider adding a simple workflow | Warning |
Total | 12 / 16 Passed | |
- 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.