document-pptx

I took a look at your document-pptx skill and wanted to share some thoughts.

Links:

• GitHub
• Your agentic skill in the SkillzWave marketplace

The TL;DR

You're at 70/100, solid C-grade territory. This is based on Anthropic's skill best practices rubric. Your Ease of Use is strong (19/25) — the "When to Use This Skill" section and Quick Reference table are genuinely helpful. But Progressive Disclosure Architecture is dragging you down (17/30) with some structural issues that are fixable.

What's Working Well

• Clear trigger section — "When to Use This Skill" has concrete use cases that make it obvious when someone should reach for this
• Practical code examples — Both Python (python-pptx) and Node.js (pptxgenjs) examples show real input/output patterns
• Good Quick Reference table — Gives developers a fast way to find operations without reading the whole file

The Big One: Referenced Files Don't Exist

Here's the thing holding you back the most: Your Navigation section references 6 files that don't exist — resources/pptx-layouts.md, resources/pptx-charts.md, templates/pitch-deck.md, and others. These broken references hurt the Progressive Disclosure Architecture score because they promise structure that isn't there.

The fix: Either create those reference files with the actual content (layouts, templates, data sources) or remove the Navigation section entirely. If you go the creation route, even stub files with basic examples would help. This one fix alone could pull you up by ~6 points.

Other Things Worth Fixing

1. Add trigger phrases to your description — Currently it just lists features. Add "Use when asked to 'create presentations', 'edit Pow...