form-cro
No security findings. Scanned 1 time, most recently 2026-02-06.
Second scanner: NVIDIA SkillSpector
Independent static run, no language model, over the same files as the Cisco scan above. How the two scanners compare across the whole corpus: Two scanners, one corpus.
What this skill does
When the user wants to optimize any form that is NOT signup/registration — including lead capture forms, contact forms, demo request forms, application forms, survey forms, or checkout forms. Also use when the user mentions "form optimization," "lead form conversions," "form friction," "form fields," "form completion rate," or "contact form." For signup/registration forms, see signup-flow-cro. For popups containing forms, see popup-cro.
- Package
- 1 file, 10 KB
- SKILL.md
- 1589 words, 12+ sections
- Code
- None. Instructions only.
- Version
- 1.0.0
SKILL.md covers: Form CRO · Initial Assessment · Core Principles · 1. Every Field Has a Cost · 2. Value Must Exceed Effort · 3. Reduce Cognitive Load · Field-by-Field Optimization · Email Field · Name Fields · Phone Number · Company/Organization · Job Title/Role
Findings
No findings. SAFE
What is in the package
| File | Kind | Size |
|---|---|---|
SKILL.md | doc | 10 KB |
Package contents recorded 2026-10-22 at commit a04cb61a577a. The scan above ran against the version current at scan time; the two can differ if the skill has since been updated.
What we checked
- Static analyzer. Pattern rules over SKILL.md and bundled files: known-bad commands, exfiltration URLs, secrets, obfuscation.
- Behavioral analyzer. Checks what the skill asks the agent to do against what its description claims it does.
- Llm analyzer. A language model reads the skill and reports intent-level issues the rules cannot express.
- Trigger analyzer. Looks for instructions that fire on conditions the user did not ask for.
- Meta analyzer. A second model pass that validates, deduplicates and re-scores the other analyzers' findings.
What we did not check
- Runtime behaviour. The skill was not executed; findings come from reading its files.
- Anything fetched at install or run time, including remote scripts, package dependencies, and URLs the skill tells the agent to open.
- Content the analyzers cannot read: images, binaries, and some non-English text.
- Known scanner bypass classes. See the methodology and limitations page.
Sources
- Repository: https://github.com/coreyhaines31/marketingskills
- Raw scan result: form-cro-scan.json
- Badge for your README:
- Request a re-scan