pptx
An AI agent skill from eigent-ai/eigent, scored 79 out of 100 by code.
Code score by group
It loses the most points in Description (9), the group that checks whether the description says what the skill does and when to use it.
What the author says it does
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 content will be used elsewhere, like in an email or summary); editing, modifying, or updating existing presentations; combining or splitting slide files; working with templates, layouts, speaker notes, or comments. Trigger whenever the user mentions "deck," "slides," "presentation," or references a .pptx filename, regardless of what they plan to do with the co…
This is the description in the skill's own SKILL.md, written by its author, not by SkillCheatSheet.
- Repository
- eigent-ai/eigent
- Folder
- resources/example-skills/pptx
- License
- Apache-2.0
- GitHub stars
- 15,808
- SKILL.md lines
- 203
- Other files
- 58
Add pptx to your agent
npx skills add eigent-ai/eigent --skill pptx
The command uses the open skills CLI. A skill is instructions and scripts your agent will follow, so read it first: open the folder on GitHub at the commit that was scored.
Labelled for
More skills from eigent-ai/eigent
-
docx
Use this skill whenever the user wants to create, read, edit, or manipulate Word documents (.docx files). Triggers include: any mention of "Word doc", "word document", ".docx", or…
Verified81B -
skill-security-auditor
Security auditing for code, configs, and infrastructure. Use when the user wants to audit or improve security: scan for vulnerabilities (SQL injection, XSS, command injection, pat…
70B -
skill-creator
Guide for creating effective skills. Use when creating a new skill or updating an existing skill that extends agent capabilities with specialized knowledge, workflows, or tool int…
65C
All skills in eigent-ai/eigent
Scores come from a snapshot of 300 public GitHub repositories taken on 12 November 2026. Every score is the result of fixed checks run by code; no AI is involved. How scoring works.