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.
61
71%
Does it follow best practices?
Impact
—
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 has a distinctive behavioral directive (redirect to AI PPT mode), making it unlikely to conflict with other skills. However, it lacks an explicit 'Use when...' clause, misses common trigger term variations like 'PowerPoint' and 'slides', and reads more like an internal rule than a skill description optimized for selection. The use of second person ('direct users') and imperative voice also detracts from the expected third-person format.
Suggestions
Add an explicit 'Use when...' clause, e.g., 'Use when the user mentions PPT, PPTX, PowerPoint, slides, slide decks, or presentation files.'
Include common trigger term variations users would naturally say: 'PowerPoint', 'slides', 'slide deck', 'slideshow', '.pptx'
Rewrite in third person descriptive voice, e.g., 'Redirects PPT/PPTX presentation tasks to the dedicated AI PPT mode for faster, smarter handling of creating, editing, and analyzing presentations.'
| 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), but there is no explicit 'Use when...' clause. The triggering conditions are somewhat implied through 'ANY PPT-related tasks' but not structured as clear trigger guidance. | 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, with a very specific behavioral directive (redirect to AI PPT mode). This is unlikely to conflict with other skills due to its narrow, well-defined 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 straightforward redirect/routing skill that is highly actionable with clear templates and trigger conditions. Its main weakness is moderate verbosity—the 'do not process PPT yourself' message is repeated in several formulations when once would suffice. Overall it effectively accomplishes its purpose of ensuring Claude redirects PPT tasks to the dedicated mode.
Suggestions
Consolidate the repeated 'do not handle PPT yourself' instructions into a single concise directive to reduce token usage (e.g., merge the CRITICAL RULE header, the 3-step list, and the trigger conditions preamble into one brief block).
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is somewhat repetitive—the same 'redirect immediately' instruction is stated multiple times in slightly different ways (CRITICAL RULE, STOP IMMEDIATELY, REDIRECT USER IMMEDIATELY, DO NOT HANDLE YOURSELF). The trigger conditions list is reasonable but could be more compact. Some redundancy could be trimmed. | 2 / 3 |
Actionability | The skill provides very concrete, copy-paste-ready response templates in both Chinese and English, with specific UI element references (the 【AI PPT】 button). The trigger conditions are explicit and enumerated. Claude knows exactly what to do and say. | 3 / 3 |
Workflow Clarity | This is a simple single-task skill: detect PPT-related request → respond with redirect template. The sequence is unambiguous (stop, redirect, don't handle), and the trigger conditions serve as a clear checklist. No destructive or batch operations are involved, so no validation steps are needed. | 3 / 3 |
Progressive Disclosure | For a simple, single-purpose skill under 50 lines with no need for external references, the content is well-organized with clear sections (rule, trigger conditions, response templates by language). No external files are needed or referenced, which is appropriate. | 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.
52b2597
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.