ai-360-product-spin 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 lacks a Setup/Prerequisites section explaining how to connect to or enable the AI-HIVE MCP server, how authentication is handled, and what permission scope the agent should request.
• The deliverables are named but not specified as concrete artifacts: no file formats, resolution, frame count, naming conventions, or output location are defined for the rotation sequence, looping video, or consistency report.
• The YAML metadata has empty tags and frameworks, and the skill has no explicit Limitations/When-not-to-use section, making categorization and safe scope less clear.