BF premium-html-studio
Generate professional-grade single-file HTML technical docs and proposals (方案) with two premium design systems. (1) International: Playfair Display + Inter + JetBrains Mono, indigo/purple palette, Stripe/Linear/Apple Docs quality for API docs, architecture, workflow analysis, research reports. (2) Chinese Technical Spec style (中文技术规格, Multi-ES style): Noto Sans SC + Noto Serif SC + JetBrains Mono, deep-purple gradient cover with KPI stats, numbered Part dividers, vertical pipeline flow charts with colored stage bars, data-flow funnel, tinted callouts — ideal for Chinese 流程详解/模式详解/链路图/节点拆解/参数说明 docs. Pairs with Prism.js syntax highlighting, layered shadows, gradient accents, publication-quality SVG diagrams. Triggers on: 技术文档, HTML 文档, 技术方案, 项目方案, 架构方案, 设计方案, 实施方案, 研究报告, 流程详解, 模式详解, 链路图, 流程图, 节点详解, pipeline 说明, proposal, premium docs, 专业文档, 漂亮的页面, 生成 HTML, make a professional HTML doc, write a proposal, generate a doc like Multi-ES, 按 Multi-ES 样式.
Generate professional-grade single-file HTML technical docs and proposals (方案) with two premium design systems.
As a process F 45/100 · Will not run — References files that are not bundled: templates/css-system-cn.css, templates/css-system.css, templates/svg-components.svg
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- The SKILL.md body is over 5,000 tokens: move reference detail into references/ and load it when needed.
- The text references files that are not there: add them or drop the references.
- 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: 1. 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") - warning
body-longSKILL.md body ≈ 19099 tokens (recommended < 5000); move details to references/ - warning
missing-refreference to a missing file: templates/css-system-cn.css - warning
missing-refreference to a missing file: templates/css-system.css - warning
missing-refreference to a missing file: templates/svg-components.svg
Process rating: all ten parameters 45/100
- 0Tools and files. 3 referenced file(s) missing: templates/css-system-cn.css, templates/css-system.css, templates/svg-components.svg
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 10Execution cost. Instruction body is 19099 tokens: crowds the task out of the window
- 30Running it twice. 4 mutating operations with no state check
- 85Steps. 112 steps, 1 vague phrases
- 100When it triggers. States when to use and when not to
- 100Failures and branches. 1 branches, has a failure section
- 100Consistency. Name and required fields are in place
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low 32 top-level sections: this looks like several domains in one skill
- low The response is described with custom markup (50 tags): a typed call is more reliable
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 960: 120–800 characters recommended
- +3Output format is not stated: the model decides each time
- -247 emoji in the instructions: noise for the model
- +1No license
- +2Single-language instructions
- +4Structure: 92 headings
- +3Step-by-step instructions: 112 items
- +4Has examples (112 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 45.