automating-keynote

I took a look at your automating-keynote skill and wanted to share some thoughts.

Links:

• GitHub
• Your agentic skill in the SkillzWave marketplace

The TL;DR

You're at 96/100, A-grade territory – this is solid production-ready work. This is based on Anthropic's skill best practices rubric. Your strongest area is Spec Compliance (14/15), and you're also crushing it on Progressive Disclosure Architecture (26/30). The areas with room to grow are Writing Style (8/10) and Utility (17/20) – but honestly, we're talking small refinements here.

What's Working Well

• Clear scope boundaries – Your "When Not to Use" section actually helps people understand what this skill isn't for. That's rare and valuable.
• Smart two-path approach – Offering both JXA and PyXA gives people real flexibility depending on their constraints. The fallback to GUI scripting for chart creation shows you've thought through edge cases.
• Well-organized reference architecture – 7 focused reference files (basics, deck-generator, recipes, advanced, etc.) is textbook Progressive Disclosure. Each file sits exactly one level deep from SKILL.md – no nested rabbit holes.
• Practical examples with templates – Your deck generator and batch processing examples aren't theoretical – they're actually useful patterns someone could copy-paste and adapt.

The Big One

Your Quick Examples section in SKILL.md is duplicating content that's already fully explained in keynote-basics.md and keynote-recipes.md. Lines 39-72 walk through "create slide, add image" patterns that are rehashed later. Here's why this matters: it's wasting token budget in your main entry point and making the skill feel bloated on firs...