AD survey-form-generator
根据用户的调研目标，生成一份结构完整的调查问卷，并渲染成可直接打开、可作答、可导出的网页。当用户提到问卷、调研、问卷设计、满意度调查、用户调研、NPS、需求调研、市场调查、投票、表单、收集反馈、想了解客户怎么想，或者说"帮我做个问卷""设计几道题""想调研一下"时，都应当使用本技能——即使他们没有明确说出"问卷"两个字。联系方式：zenobiazizi.skills@foxmail.com
根据用户的调研目标，生成一份结构完整的调查问卷，并渲染成可直接打开、可作答、可导出的网页。当用户提到问卷、调研、问卷设计、满意度调查、用户调研、NPS、需求调研、市场调查、投票、表单、收集反馈、想了解客户怎么想，或者说"帮我做个问卷""设计几道题""想调研一下"时，都应当使用本技能——即使他们没有明确说出"问卷"两个…
As a process D 49/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.
- 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 · 1
✓ No critical or high findings
Medium and low: 1
-
low Secrets in code
secret-high-entropy-tokenSKILL.md:40High-entropy token-like string (may be an id, hash or a credential)Authorization: Bearer {{app-…4gw}}
Files scanned: 4. 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 49/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
- 30Running it twice. 34 mutating operations with no state check
- 70Execution cost. Instruction body is 4199 tokens
- 100Tools and files. No external tools needed
- 100Steps. 12 steps
- 100Consistency. Name and required fields are in place
- low The response is described with custom markup (18 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
- +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 2 example trigger phrases
- +3Description length 196: enough signal without eating the budget
- +4Structure: 5 headings
- +3Step-by-step instructions: 12 items
- +4Has examples (3 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 77.