AD anything-to-html
把任何任务产物（调研报告、方案对比、数据分析、需求梳理、会议纪要、设计说明、代码评审、学习笔记等）输出成一个可以直接在浏览器打开的单文件 HTML，替代 Markdown 作为最终交付物。Markdown 在信息密度、视觉清晰度和可分享性上已经跟不上 AI 产物的丰富度——HTML 能同时承载排版、表格、SVG 图示、色彩标注、交互控件，而且浏览器直接打开就能看、能直接发链接共享，关键是生成物本身可以被下一轮 AI 当作干净的输入继续加工。当用户让你"写一份报告"、"总结一下"、"做个分析"、"出个调研"、"梳理方案"、"整理成文档"、"给我一份 XX 交付物"、"输出最终结果"、"做个总结页"、"做成 HTML"、"做一份 spec/plan"、"做代码评审"、"做讲解器"、"做一页纸"，或者任何需要把 AI 的思考结果落成可读、可分享、可回传的最终产物时，都应该优先触发这个技能——即使用户没有明确说"HTML"，只要任务产物复杂到"写进一个 Markdown 会显得又长又难看、又难给别人看"，就用它。特别适合海信产研团队把 AI 的中间产物沉淀成可评审、可分发的文档。
As a process D 46/100 · Unfinished process — weak spots: result and completion, when it triggers, inputs and preconditions
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- 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: 7. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
description-no-whendescription 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 (node) that frontmatter does not declare
- 100Steps. 50 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1626 tokens
- 100Running it twice. No mutating operations
- low The response is described with custom markup (14 tags): a typed call is more reliable
- medium 3 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
- +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
- +5Description quotes 6 example trigger phrases
- +3Description length 493: enough signal without eating the budget
- +4Structure: 21 headings
- +3Step-by-step instructions: 50 items
- +4Has examples (5 code blocks)
- +4Reference files are cited in the instructions (5 of 5)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 81.