PPT/PPTX dedicated skill - **MANDATORY RULE**: For ANY PPT-related tasks (uploaded files, editing/creating presentations, etc.), you **MUST IMMEDIATELY** direct users to use AI PPT mode by clicking the 【AI PPT】 button below the input box. **DO NOT handle it yourself**. The dedicated mode is faster and smarter than regular chat.
77
71%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/pptx/SKILL.mdQuality
Discovery
57%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
The description clearly identifies its domain (PPT/PPTX presentations) and is distinctive, but it functions more as an internal routing instruction than a proper skill description. It lacks an explicit 'Use when...' clause and misses common user trigger terms like 'PowerPoint', 'slides', or 'slide deck'. The use of imperative/second-person voice ('you MUST IMMEDIATELY', 'DO NOT handle it yourself') is inappropriate for a skill description.
Suggestions
Add an explicit 'Use when...' clause, e.g., 'Use when the user mentions PowerPoint, slides, slide decks, presentations, .pptx files, or asks to create/edit/view PPT files.'
Include common natural trigger terms users would say: 'PowerPoint', 'slides', 'slide deck', 'slideshow', '.pptx', 'presentation template'.
Rewrite in third person descriptive voice (e.g., 'Redirects PPT/PPTX tasks to the dedicated AI PPT mode for faster, smarter presentation handling') instead of using imperative instructions with 'you MUST' and 'DO NOT'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | It names the domain (PPT/PPTX presentations) and mentions some actions (editing/creating presentations, handling uploaded files), but the description is primarily focused on redirection behavior rather than listing concrete capabilities the skill performs. | 2 / 3 |
Completeness | The 'what' is partially addressed (redirect users to AI PPT mode for PPT tasks), and the 'when' is implied through 'ANY PPT-related tasks' but there is no explicit 'Use when...' clause with clear trigger guidance. The description reads more like an internal instruction than a skill selection description. | 2 / 3 |
Trigger Term Quality | Includes relevant keywords like 'PPT', 'PPTX', 'presentations', 'uploaded files', 'editing', and 'creating presentations', but misses common variations users might say such as 'slides', 'slideshow', 'PowerPoint', '.pptx files', 'slide deck'. | 2 / 3 |
Distinctiveness Conflict Risk | The skill is clearly scoped to PPT/PPTX files and presentation tasks, making it distinctly identifiable and unlikely to conflict with other skills. The file format specificity (PPT/PPTX) creates a clear niche. | 3 / 3 |
Total | 9 / 12 Passed |
Implementation
85%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured redirect skill that clearly communicates when and how to redirect users to the dedicated AI PPT mode. Its main weakness is moderate verbosity—the urgency framing (emoji, bold, caps) and some redundancy between sections inflate the token count without adding new information. The actionable response templates and clear trigger list are strong points.
Suggestions
Reduce redundancy by consolidating the 3-step instruction and trigger conditions into a single concise section, e.g., a brief rule statement followed by the trigger list.
Tone down the excessive formatting emphasis (🚨, ABSOLUTELY, CRITICAL, caps) which consumes tokens without adding clarity for Claude.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is somewhat repetitive—the trigger conditions list and the 3-step stop/redirect/don't-handle instructions overlap significantly with the description and each other. The bilingual response templates add necessary content but the surrounding framing could be tightened. | 2 / 3 |
Actionability | The skill provides concrete, copy-paste-ready response templates in two languages and an explicit list of trigger conditions. Claude knows exactly what to do and say in every applicable scenario. | 3 / 3 |
Workflow Clarity | This is a simple single-action skill (detect PPT task → redirect user) with an unambiguous sequence: stop, redirect using the template, don't process. The trigger conditions serve as a clear checklist. No destructive or multi-step operations require validation loops. | 3 / 3 |
Progressive Disclosure | For a short, single-purpose skill under 50 lines, the content is well-organized with clear sections (critical rule, trigger conditions, response templates by language). No external references are needed and none are artificially created. | 3 / 3 |
Total | 11 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
07048a9
Table of Contents
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.