SKILLEMALL.ai

CD html-to-pptx

把 slide/poster 的 HTML 确定性地转成可编辑 PPTX——每个视觉元素(插画、图标、箭头、装饰线、文字)都是能单独选中拖动的对象,而不是压成一张背景图;也能自动识别并转换 Editable Design 的 editor.html 和 case 的图层展开图 layers.html;并可把产物渲回图片做保真度比对。当用户要导出 pptx/ppt、问「HTML 怎么转 PowerPoint」、想让生成的海报或幻灯片能在 PowerPoint 里继续改、要把图层展开图/拆解图变成 ppt、或需要检查转换后元素是否独立可编辑时使用。

yejy53/Editable-Design Agent Skills author: yejy53 15 files · 8 scripts body ≈ 1 854 tokens Open the sourcegithub.com↗ analyzed 3 d ago

把 slide/poster 的 HTML 确定性地转成可编辑 PPTX——每个视觉元素(插画、图标、箭头、装饰线、文字)都是能单独选中拖动的对象,而不是压成一张背景图;也能自动识别并转换 Editable Design 的 editor.html 和 case 的图层展开图…

As a process D 46/100 · Unfinished process — weak spots: result and completion, when it triggers, inputs and preconditions

ProcedurePowerPointPlaywrightSoftware developmenttype and topics are labelled automatically from the skill text
JSON
Technical rating
C
88/100
safety, quality, tests
Safety 60%
100
Quality 40%
70
Run on models
none yet
Process rating
D
46/100
Unfinished process
Result and completion w 14
0
Inputs and preconditions w 11
0
Failures and branches w 10
0
the three weakest of ten parameters · all ten

How to improve

  1. Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
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: 15. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning description-no-when description does not say WHEN to use the skill (no "use when")

Process rating: all ten parameters 46/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
  • 60Tools and files. Uses tools (bash, python) that frontmatter does not declare
  • 100Steps. 10 steps
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 1854 tokens
  • 100Running it twice. No mutating operations

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
  • -31 of 7 scripts are never mentioned in SKILL.md
  • +2Single-language instructions
  • +3Description length 275: enough signal without eating the budget
  • +4Structure: 10 headings
  • +3Step-by-step instructions: 10 items
  • +4Has examples (8 code blocks)
  • +1License stated

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