AC pptx
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 content afterward. If a .pptx file needs to be opened, created, or touched, use this skill.
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…
As a process C 59/100 · Has gaps — weak spots: result and completion, consistency, running it twice
How to improve
- Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 0
✓ No critical or high findings
Files scanned: 20. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
✓ No remarks against the Agent Skills spec
Process rating: all ten parameters 59/100
- 0Result and completion. Does not say what the result is
- 0Progress reporting. Says nothing while it works
- 30Running it twice. 9 mutating operations with no state check
- 40Consistency. Frontmatter name (pptx) differs from the folder (pptx-en)
- 50Failures and branches. 0 branches, has a failure section
- 60Tools and files. Uses tools (python, node) that frontmatter does not declare
- 70Inputs and preconditions. Inputs and preconditions are listed
- 85Steps. 40 steps, 1 vague phrases
- 100When it triggers. States when to use and when not to
- 100Execution cost. Instruction body is 2194 tokens
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +4Description does not say when NOT to use the skill (false activations)
- +3Output format is not stated: the model decides each time
- -33 of 4 scripts are never mentioned in SKILL.md
- +2Single-language instructions
- +5Description quotes 2 example trigger phrases
- +3Description length 688: enough signal without eating the budget
- +4Structure: 18 headings
- +3Step-by-step instructions: 40 items
- +4Has examples (6 code blocks)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 87.