Security audit
Security checks for vulnerabilities and agentic risk
This is a plain guidance skill for improving non-signup forms, with no executable code, install hooks, persistence, or hidden data handling.
Installers should expect this skill to read form-related business context files if they exist and then give CRO recommendations. It appears low risk, but users should still review suggested form changes before applying them to production, especially when collecting personal, payment, or regulated data.
Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.
## Field-by-Field Optimization
### Email Field
- Single field, no confirmation
- Inline validation
- Typo detection (did you mean gmail.com?)
- Proper mobile keyboard
This JSON eval file is a manifest-type file, so vague-trigger checks apply. The expected output says the skill 'Should trigger on casual phrasing,' which defines activation in an overly broad way without listing specific trigger phrases, constraints, or exclusion conditions, increasing the risk of unintended invocation from ordinary language.
No suspicious patterns detected.