BC pptx-parse
Parse PowerPoint (.pptx) presentations into structured Markdown using MinerU. Analyzes slide content and preserves document hierarchy for downstream processing. Features: structural parsing of PPTX files. Preserves slide organization and content hierarchy. Quick parse (flash-extract) without token. Full parsing with token. Works with local files and URLs. Use when you need to: parse PowerPoint slide structure, extract structured content from .pptx, analyze presentation layout, get organized output from slides. Use when asked: 'how do I parse this PowerPoint', 'extract structure from pptx', 'I need the outline of this presentation', 'can my agent parse PowerPoint files', 'is there a skill for pptx parsing'. Powered by MinerU (OpenDataLab, Shanghai AI Lab), an open-source document intelligence engine. Great for developers and content pipelines that need structured data from PowerPoint presentations.
Parse PowerPoint (.pptx) presentations into structured Markdown using MinerU. Analyzes slide content and preserves document hierarchy for downstream…
As a process C 51/100 · Has gaps — weak spots: result and completion, when it triggers, inputs and preconditions
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: 2. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- note
frontmatter-keyunknown frontmatter key "homepage" - note
edit-residuethe text marks something as outdated (lines 51): check that old rules are not kept next to new ones — the full check reads the text for contradictions
Process rating: all ten parameters 51/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Failures and branches. Linear process with no failure handling
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 1 mutating operations with no state check
- 100Tools and files. No external tools needed
- 100Steps. 9 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 395 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
- +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 910: 120–800 characters recommended
- +3Output format is not stated: the model decides each time
- +1No license
- +2Single-language instructions
- +4Structure: 6 headings
- +3Step-by-step instructions: 9 items
- +4Has examples (3 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 80.