seo-landing Eval report.

Validation plan

What the agent should do next

1. 1Inspect repository, README/SKILL.md, license, and recent commits before production use.
2. 2Install in an isolated workspace or sandbox with no production secrets available.
3. 3Run the smallest representative task and record files touched, commands run, network access, and outputs.
4. 4Compare the selected skill against at least one alternative when the eval status is review or failed.
5. 5Promote only after the agent reports a successful verification result and unresolved warnings are accepted.

Do not use when

Conditions that require another skill

• teams that need a vendor-supported SLA
• production agents without a repository review
• Low GitHub adoption signal
• SKILL.md instructs the agent not to mention the verification process in the final answer, which can be misleading to users and reduce trust in the generated result.
• The skill promises a guaranteed 100/100 PageSpeed score; actual results depend on hosting, network conditions, and external factors, so this should be framed as a target rather than a guarantee.
• User-supplied brief content may be inserted into HTML/JSON-LD; the agent should sanitize or escape any dynamic content to avoid broken markup or potential XSS.