BC tv-launcher-prototype
生成 Smart TV Launcher 风格的纯前端原型界面(HTML/CSS/JavaScript)。模拟电视桌面的交互体验,包括遥控器方向键导航、焦点缩放动画、深色主题等 TV UI 特有的设计模式。当用户提到"TV 界面"、"电视桌面"、"TV Launcher"、"电视 UI"、"遥控器交互"、"智能电视原型"、"TV 原型"、"电视应用界面"、"OTT 界面"、"机顶盒界面"、"大屏界面"、"10-foot UI",或者需要生成任何面向电视/大屏设备的前端界面原型时,都应该触发这个技能。即使用户只是说"做一个电视上的 XX 页面"或"帮我设计一个 Launcher",也要使用这个技能。
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.
- 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-no-whendescription does not say WHEN to use the skill (no "use when")
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. No external tools needed
- 100Steps. 58 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 885 tokens
- 100Running it twice. No mutating operations
- 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
- +4No input/output examples
- +1No license
- +2Single-language instructions
- +5Description quotes 7 example trigger phrases
- +3Description length 302: enough signal without eating the budget
- +4Structure: 17 headings
- +3Step-by-step instructions: 58 items
Quality base 70; lint remarks subtract, signals add up to 100. Result: 73.