Content
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The body is highly actionable with a clear sequenced workflow and validation, but it is verbose and underuses its bundle: the provided reference file is orphaned and overlapping code is duplicated inline rather than split out.
Suggestions
Link references/implementation.md from the body (e.g., a '## Implementation details' section pointing to it) and move the long code blocks there, keeping SKILL.md as a concise overview.
Dedupe the inventory implementation between the body's Step 1 and the reference file so they do not present two divergent versions of the same routine.
Tighten the Overview and inline code comments to remove content that restates what the code already shows, reducing token cost without losing clarity.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is ~255 lines with five large TypeScript blocks and an inventory implementation that duplicates (with different code) the one in references/implementation.md; mostly efficient but could be tightened and deduplicated. | 2 / 3 |
Actionability | Provides concrete executable TypeScript (JSZip/xmldom PPTX extraction, batch migration with pLimit, generateFromTemplate) plus specific endpoints ('POST /v1.0/generations/from-template') and a solutions-oriented error table. | 3 / 3 |
Workflow Clarity | A clear five-step sequence (inventory → extract → batch migrate → template recreation → validation) with an explicit post-migration checklist and an error-handling table mapping issues to fixes. | 3 / 3 |
Progressive Disclosure | A bundle reference file (references/implementation.md) exists but is never linked or signaled from the body, and large code blocks that could live in the reference are inlined, leaving organization incomplete. | 2 / 3 |
Total | 10 / 12 Passed |