What problem does it solve? After a deployment runs on Rainbond, it is hard to know whether the application truly converged and whether end users can actually reach it. This Skill performs the final delivery acceptance step: it inspects component runtime state, distinguishes delivered from partially-delivered or blocked rollouts, and reports the real access URL. ## Core Features & Use Cases - Delivery Acceptance Classification: Classifies each deployment as delivered, delivered-but-needs-manual-validation, partially-delivered, or blocked based on component convergence and access-path evidence. - Access URL Verification: Resolves the preferred user-facing URL and, for reverse-proxy full-stack apps, checks both the root page and the same-host API path before declaring success. - Stateful Persistence Checks: Inspects storage summaries for databases and middleware to confirm durable mounts before reporting a clean delivery. - Use Case: After deploying a frontend plus backend project to Rainbond, ask the agent to confirm delivery; it verifies component health, tests the page and /api paths, and returns the final access address or a precise blocker. ## Quick Start Ask the agent to confirm whether the current Rainbond application has been delivered successfully and to give you the access address.
