AB html-ppt-to-pdf
Convert any HTML slide deck that uses the `<section class="slide">` convention into a high-fidelity, vector-text PDF using Playwright + Chromium's native `page.pdf()`. Supports decks from the `html-ppt` skill, `frontend-slides` / `frontend-design` skill, and any hand-written HTML that follows the same convention. Triggers on requests like "把 HTML PPT 转 PDF", "这个 HTML 幻灯片导出 PDF", "HTML 转 PDF 出现字体失真/页码错乱/丢页重页/部分内容看不见". DO NOT use for plain web pages (use browser print), Markdown (use pandoc), or `.pptx` (use the pptx skill).
As a process B 76/100 · Nearly there — weak spots: result and completion, progress reporting
How to improve
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 2
✓ No critical or high findings
Medium and low: 2
-
low Secrets in code
secret-high-entropy-tokenscripts/package-lock.json:30High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"integrity": "sha5…ZPC+taih…dxR/LKBa…Qnt+ViGvEIQ==",
detector -
low Secrets in code
secret-high-entropy-tokenscripts/package-lock.json:39High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)"integrity": "sha5…uWm+fFRcIOgKBMiOBP+eXiy…9ab+DDKA==",
quoted
Files scanned: 7. 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 76/100
- 0Result and completion. Does not say what the result is
- 0Progress reporting. Says nothing while it works
- 50Failures and branches. 0 branches, has a failure section
- 70Inputs and preconditions. Inputs and preconditions are listed
- 100Tools and files. No external tools needed
- 100Steps. 23 steps
- 100When it triggers. States when to use and when not to
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 698 tokens
- 100Running it twice. No mutating operations
- low The response is described with custom markup (3 tags): a typed call is more reliable
- medium 1 test cases, all positive: not one "should refuse" or "should ask first"
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
- +3Output format is not stated: the model decides each time
- +2Single-language instructions
- +5Description quotes 3 example trigger phrases
- +4Description says when NOT to use the skill
- +3Description length 528: enough signal without eating the budget
- +4Structure: 7 headings
- +3Step-by-step instructions: 23 items
- +4Has examples (1 code blocks)
- +3All 1 scripts are documented
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 97.