rainbond-app-assistant

Orchestrates Rainbond deployment, troubleshooting, delivery verification, and dev-to-test promotion for source projects.

7|1|Updated May 13, 2026
One-click install
npx skills add https://github.com/goodrain/rainskills --skill rainbond-app-assistant-goodrain
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: rainbond-app-assistant
Source: https://github.com/goodrain/rainskills/tree/main/rainbond-app-assistant
Command: npx skills add https://github.com/goodrain/rainskills --skill rainbond-app-assistant-goodrain

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Deploying a source project to Rainbond involves many stages—project initialization, topology bootstrap, build troubleshooting, delivery verification, and version promotion—and it is easy to pick the wrong step or silently fall back to the wrong delivery mode. This Skill acts as the top-level router that inspects the current project state and drives the right lower-level Rainbond Skill at the right time. ## Core Features & Use Cases - State-aware orchestration: Classifies the project as unlinked, topology-missing, building, healthy, capacity-blocked, or needing code/build handoff, then routes to init, bootstrap, troubleshooter, or delivery verifier accordingly. - Delivery path protection: Locks source-backed projects to the source path and never silently switches to package, image, or template fallback after a build failure. - Dev-to-test promotion: On explicit request, creates a snapshot version, provisions a testing app, and verifies its delivery before stopping. - Use Case: Tell the agent "帮我部署当前项目,并验证页面和 API" and it resolves the workspace, builds the app on Rainbond, verifies the access URL, and reports a concise Chinese deployment result. ## Quick Start Ask the agent to deploy the current project with Rainbond and verify the page and API endpoints.

Frequently Asked Questions about rainbond-app-assistant

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I deploy my current project to Rainbond?

Tell the agent to deploy the current project and verify the page and API. The assistant resolves the workspace context, runs project init if unlinked, bootstraps the topology, troubleshoots build issues, and verifies the final access URL.

How does the assistant decide which Rainbond skill to run?

It classifies the project state first: unlinked projects go to project init, missing topology goes to bootstrap, building or unhealthy topology goes to the troubleshooter, and healthy runtime goes to the delivery verifier. Routing rules are defined in its routing reference.

What happens when a source build fails on Rainbond?

The run enters the source_build_failed phase and routes to the troubleshooter on the same source path. It never silently falls back to package upload, image creation, or template install without explicit user confirmation.

Can it promote an app from development to testing?

Yes, but only on explicit request. After the source app reaches strict delivered status, it creates a snapshot version, provisions a testing app, and verifies the testing app delivery before stopping.

When does the assistant stop instead of continuing deployment?

It stops for ambiguous team/app identity, cluster capacity shortages, missing secrets, invalid source refs, complex suites lacking a descriptor, code/build handoff needs, or when the retry budget is exhausted, always reporting one next step.

Does it support third-party Compose or Helm applications?

No. Supplied third-party Compose, Helm, or image-set descriptors and named open-source suites are routed to rainbond-opensource-app-deploy, and confirmed market templates go to rainbond-template-installer.