What it claims to do
Use this skill any time a .pptx file is involved in any way — as input, output, or both. This includes: creating slide decks, pitch decks, or presentations; reading, parsing, or extracting text from any .pptx file (even if the extracted con…
What we found · 5
- Description doesn’t say WHEN to use itmediumA good description names the trigger (e.g. "when reviewing a PR"). Without it the skill mis-fires or never fires.
- Trigger is too broadmediumWords like "any", "whenever" make it fire everywhere and fight other skills for the same task — the #1 cause of conflicts.
- Bloated: high token costmedium~2,282 tokens on every single call. Compress instructions and trim examples.
- Embedded shell script blockmediumShips runnable command-line scripts. Not necessarily bad, but must be sandboxed and reviewed.
- Description too longlowThe description is read on every trigger check; overly long ones waste tokens and dilute the signal.
Conflicts with · 6
| xlsx | shadow | time, file, input, output, read |
| shadow | read, extract, text | |
| claude-api | shadow | read, file |
| docx | shadow | read |
| frontend-design | shadow | read |
| verification-before-completion | shadow | output |
If you have both installed, they compete for the same triggers — the top cause of an agent picking the wrong skill.
One command grades every skill in your Claude Code / Codex — safety, token bloat, and conflicts, 100% locally.
npx skillmoo scan
Grade computed 2026-07-13 · rubric static-v1. Efficacy shown only when measured on a labeled model + task suite — never invented.
Add this independent grade to the skill's README — the badge links back to this rating and updates when we re-grade.
[](https://skillmoo.com/skill/pptx/)