SKILLEMALL.ai

CB pptx-official

Use this skill whenever a Microsoft PowerPoint (.pptx) file is being produced, opened, transformed, or read. That includes: authoring slide decks, pitch decks, executive readouts, training material, or any presentation deliverable; extracting text or structure from an existing .pptx; filling a .pptx template with values; converting a deck to PDF or images; splitting or merging decks; inspecting slides, layouts, masters, tables, images, charts, speaker notes, or comments. Trigger on words like 'deck', 'slides', 'presentation', 'pitch deck', 'keynote' (when a .pptx is expected as output), or any filename ending in .pptx. Do NOT trigger when the primary deliverable is a Word document, spreadsheet, PDF report, HTML site, or Google Slides API call, even if presentation-shaped content appears along the way.

XiaomiMiMo/MiMo-Code Agent Skills author: XiaomiMiMo MIT 17 files · 12 scripts body ≈ 6 555 tokens Open the sourcegithub.com↗ analyzed 6 d ago

pptx) file is being produced, opened, transformed, or read.

As a process B 69/100 · Nearly there — weak spots: result and completion, running it twice

ProcedurePowerPointWordPDFSoftware developmenttype and topics are labelled automatically from the skill text
JSON
Technical rating
C
81/100
safety, quality, tests
Safety 60%
85
Quality 40%
75
Run on models
none yet
Process rating
B
69/100
Nearly there
Result and completion w 14
0
Running it twice w 4
30
Tools and files w 18
60
the three weakest of ten parameters · all ten

What is at stake

Medium-severity findings: the skill is probably honest, but read what alarmed the scanner.

Dangerous commands medium severity

Below is the worst case for this category. The finding here is medium: the guard saw a sign, not a proof.

If you install

The skill contains commands that delete files, rewrite disks or execute code fetched from the network. The agent may run them without asking if it believes the instructions require it.

For the author

Replace destructive commands with safe equivalents that ask for confirmation, scope them to one folder, and stop piping curl into a shell: pin a version and a checksum.

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 · 3

✓ No critical or high findings

Medium and low: 3
  • medium Dangerous commands cmd-pipe-to-shell-known-host SKILL.md:42
    Pipe-to-shell installer from a well-known host (still executes remote code)
    curl -LsSf https://astral.sh/uv/install.sh | sh
  • medium Dangerous commands cmd-execpolicy-bypass SKILL.md:43
    Runs PowerShell with execution policy bypassed
    # Windows: powershell -ExecutionPolicy ByPass -c "irm https://astral.sh/uv/install.ps1 | iex"
  • medium Dangerous commands cmd-pipe-to-shell-known-host SKILL.md:47
    Pipe-to-shell installer from a well-known host (still executes remote code)
    curl -fsSL https://bun.sh/install | bash

Files scanned: 17. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning body-long SKILL.md body ≈ 6555 tokens (recommended < 5000); move details to references/
  • note edit-residue the text marks something as outdated (lines 112, 400): check that old rules are not kept next to new ones — the full check reads the text for contradictions

Process rating: all ten parameters 69/100

  • 0Result and completion. Does not say what the result is
  • 30Running it twice. 15 mutating operations with no state check
  • 60Tools and files. Uses tools (bash, web, python, node) that frontmatter does not declare
  • 70Inputs and preconditions. Inputs and preconditions are listed
  • 70Execution cost. Instruction body is 6555 tokens
  • 85Steps. 55 steps, 1 vague phrases
  • 100When it triggers. States when to use and when not to
  • 100Failures and branches. 2 branches, has a failure section
  • 100Consistency. Name and required fields are in place
  • 100Progress reporting. Reports progress
  • medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
  • low 13 top-level sections: this looks like several domains in one skill

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)
  • +3Description length 812: 120–800 characters recommended
  • +3Output format is not stated: the model decides each time
  • +2Single-language instructions
  • +4Structure: 22 headings
  • +3Step-by-step instructions: 55 items
  • +4Has examples (17 code blocks)
  • +3All 12 scripts are documented
  • +1License stated

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