SKILLEMALL.ai

AD pptx

Presentation creation, editing, and analysis. When Claude needs to work with presentations (.pptx files) for: (1) Creating new presentations, (2) Modifying or editing content, (3) Working with layouts, (4) Adding comments or speaker notes, or any other presentation tasks

LeoYeAI/openclaw-master-skills Agent Skills author: LeoYeAI MIT 19 files body ≈ 6 294 tokens Open the sourcegithub.com analyzed 2 d ago

Presentation creation, editing, and analysis.

As a process D 40/100 · Unfinished process — weak spots: result and completion, inputs and preconditions, consistency

AnalyzerPowerPointWriting and documentstype and topics are labelled automatically from the skill text
JSON
Technical rating
A
91/100
safety, quality, tests
Safety 60%
100
Quality 40%
78
Run on models
none yet
Process rating
D
40/100
Unfinished process
Result and completion w 14
0
Inputs and preconditions w 11
0
Progress reporting w 2
0
the three weakest of ten parameters · all ten

How to improve

  1. The SKILL.md body is over 5,000 tokens: move reference detail into references/ and load it when needed.
For the model run — optional
  • 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: 19. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning body-long SKILL.md body ≈ 6294 tokens (recommended < 5000); move details to references/

Process rating: all ten parameters 40/100

  • 0Result and completion. Does not say what the result is
  • 0Inputs and preconditions. Does not say what the process needs to start
  • 0Progress reporting. Says nothing while it works
  • 30Running it twice. 16 mutating operations with no state check
  • 40Consistency. Frontmatter name (pptx) differs from the folder (x-92bilal26-pptx)
  • 50When it triggers. No condition that starts the skill
  • 55Failures and branches. 1 branches
  • 60Tools and files. Uses tools (bash, python, node) that frontmatter does not declare
  • 60Steps. 187 steps, 7 vague phrases
  • 70Execution cost. Instruction body is 6294 tokens
  • medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
  • low The response is described with custom markup (7 tags): a typed call is more reliable

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

  • +5Description has no quoted example phrases that should trigger the skill
  • +4Description does not say when NOT to use the skill (false activations)
  • +3Output format is not stated: the model decides each time
  • +2Single-language instructions
  • +3Description length 271: enough signal without eating the budget
  • +4Structure: 22 headings
  • +3Step-by-step instructions: 187 items
  • +4Has examples (16 code blocks)
  • +3All 5 scripts are documented
  • +1License stated

Quality base 70; lint remarks subtract, signals add up to 100. Result: 78.