AD ppt-style-matcher
PPT风格分析与匹配工具。提取已有PPT的设计规范（配色/字体/布局/装饰元素），指导新页面或修改页保持风格统一。 Use when user asks to PPT风格匹配、修改几页风格不一致、分析PPT设计规范、提取PPT配色字体、新页面怎么跟原PPT风格一致、PPT重设计。 不适用于从头创建全新PPT、不需要保持风格一致的场景、非PPTX格式文件。
PPT风格分析与匹配工具。提取已有PPT的设计规范（配色/字体/布局/装饰元素），指导新页面或修改页保持风格统一。 Use when user asks to PPT风格匹配、修改几页风格不一致、分析PPT设计规范、提取PPT配色字体、新页面怎么跟原PPT风格一致、PPT重设计。…
As a process D 41/100 · Unfinished process — 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: 5. 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 41/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
- 40Consistency. Frontmatter name (ppt-style-matcher) differs from the folder (ppt-matcher)
- 60Tools and files. Uses tools (python) that frontmatter does not declare
- 100Steps. 12 steps
- 100Execution cost. Instruction body is 538 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
- +1No license
- +2Single-language instructions
- +3Description length 178: enough signal without eating the budget
- +4Structure: 12 headings
- +3Step-by-step instructions: 12 items
- +4Has examples (3 code blocks)
- +4Reference files are cited in the instructions (1 of 1)
- +3All 1 scripts are documented
Quality base 70; lint remarks subtract, signals add up to 100. Result: 91.