BC ui-ux-dev-tool-free
面向个人开发者的自然语言驱动React页面生成工具,通过CDN方式零构建运行, 内置截图视觉审查循环,支持快速原型迭代。核心能力: - 自然语言描述生成React页面(CDN零构建) - 项目配置与偏好管理 - 截图视觉审查与迭代修复 - 基础设计原则自动应用 - 图片转WebP格式优化 - 静态文件导出 适用场景: - 个人开发者快速生成落地页原型 - 独立项目单页面快速开发 - 设计概念验证与视觉迭代 差异化:免费版聚焦单页面快速生成与视觉审查,使用CDN方式零构建, 适合个人快速原型
面向个人开发者的自然语言驱动React页面生成工具,通过CDN方式零构建运行, 内置截图视觉审查循环,支持快速原型迭代。核心能力: - 自然语言描述生成React页面(CDN零构建) - 项目配置与偏好管理 - 截图视觉审查与迭代修复 - 基础设计原则自动应用 - 图片转WebP格式优化 - 静态文件导出…
As a process C 53/100 · Has gaps — 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.
- For Hermes the description must be one sentence under 60 characters; move the conditions to a "When to Use" section.
- 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: 2. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
description-long-hermesdescription is 247 chars; the Hermes authoring standard requires ≤ 60 (one sentence, ending with a period) - warning
description-no-whenneither description nor a "## When to Use" section says when to use the skill - note
frontmatter-keyunknown frontmatter key "slug" - note
frontmatter-keyunknown frontmatter key "displayName" - note
frontmatter-keyunknown frontmatter key "summary" - note
frontmatter-keyunknown frontmatter key "edition" - note
frontmatter-keyunknown frontmatter key "tools" - note
frontmatter-keyunknown frontmatter key "homepage"
Process rating: all ten parameters 53/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
- 100Tools and files. Tools declared in frontmatter
- 100Steps. 32 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 2575 tokens
- 100Running it twice. No mutating operations
- low 13 top-level sections: this looks like several domains in one skill
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
- -2localhost URLs: will not work for another user
- +2Single-language instructions
- +3Description length 247: enough signal without eating the budget
- +4Structure: 38 headings
- +3Step-by-step instructions: 32 items
- +4Has examples (14 code blocks)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 62.