BC formora-survey
Create, edit, publish, and distribute Formora AI surveys, polls, and forms. Supports organic channels (Telegram, Email, QR code, X) and live paid ads (Google Ads + Meta Ads with paused-by-default creation and shared daily/weekly budget caps). Always previews questions and requires explicit user confirmation before publishing. Requires FORMORA_API_KEY. / 使用 Formora AI 创建、编辑、发布并分发问卷/表单/投票。支持有机渠道（Telegram、Email、二维码、X）及付费广告投放（Google Ads、Meta Ads，默认暂停创建，合计每日/每周预算上限保护）。需要 FORMORA_API_KEY。
As a process C 56/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.
- 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 · 2
✓ No critical or high findings
Medium and low: 2
-
low Exfiltration
exfil-webhook-urlscripts/formora.py:352Webhook / callback URL commonly used for exfiltration (verify the destination) (the skill's own vendor host; quoted — discussed, not commanded)f"https://api.telegram.org/bot{token}/sendPhoto",vendor-hostquoted -
low Exfiltration
exfil-webhook-urlscripts/formora.py:362Webhook / callback URL commonly used for exfiltration (verify the destination) (the skill's own vendor host; quoted — discussed, not commanded)f"https://api.telegram.org/bot{token}/sendMessage",vendor-hostquoted
Files scanned: 3. 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 56/100
- 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
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 5 mutating operations with no state check
- 50Failures and branches. 0 branches, has a failure section
- 100Tools and files. No external tools needed
- 100Steps. 20 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1752 tokens
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
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
- +1No license
- +2Single-language instructions
- +3Description length 487: enough signal without eating the budget
- +4Structure: 15 headings
- +3Step-by-step instructions: 20 items
- +4Has examples (11 code blocks)
- +3All 1 scripts are documented
Quality base 70; lint remarks subtract, signals add up to 100. Result: 75.