Document start/finalize two-step import handoff in skills#4
Open
rsuresh-retool wants to merge 1 commit into
Open
Conversation
arnold-retool
approved these changes
Jun 5, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Documents the two-step import handoff in both
retool-importskills. The handoff now prefersretool_start_prepared_import(provisions the sandbox, returns a time-limited upload URL) + a zip PUT +retool_finalize_prepared_import, and falls back to the inlineretool_submit_prepared_importtool only when a step of the two-step flow errors.Touches:
plugins/retool-import/skills/retool-import/SKILL.md(generic)plugins/retool-import/skills/retool-import-lovable/SKILL.md(Lovable sibling)Why
The product side split the MCP import into a start/finalize flow:
retool_start_prepared_importreturns an upload URL the client PUTs a zip to (gated on Vite readiness), thenretool_finalize_prepared_importconfirms it. Inlining the whole source tree into a singleretool_submit_prepared_importcall doesn't scale, so the two-step flow is now the preferred path. The inline submit stays as the recovery path so the skills keep working against orgs that only have the older tool.What changed (identical edit in both skills)
mcpServerRetoolImportEnabled; prefer start+finalize, use inline submit if only that is visible, stop only if none are visible.Record<string, { code }>is now described as zipped+uploaded in the two-step flow, or passed inline in the fallback.Authorization: Bearer <token>+Content-Type: application/zip, ~2s retry on 503, finalize) and "Fallback — inline submit (only on a two-step error)". Inline submit is explicitly NOT the first attempt.Stacked on
rohansuresh/retool-import-lovable-skill(Add retool-import-lovable sibling skill)rohansuresh/retool-import-skillrohansuresh/plugin-marketplace-scaffold