Run any Skill in Manus with one click

build-recovery

Stars333

Forks48

UpdatedJuly 14, 2026 at 05:17

Owns the build wait and build failure. Narrates the generation honestly while it runs, and when it errors, names the failure plainly with a real recovery path instead of a generic "oops". Loads when generation is long or returns an error. The single highest-risk moment for the "it's actually building" belief.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

QuantumByteOSS

QuantumByteOSS/quantumbyte

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

SKILL.md

readonly

name	build-recovery
description	Owns the build wait and build failure. Narrates the generation honestly while it runs, and when it errors, names the failure plainly with a real recovery path instead of a generic "oops". Loads when generation is long or returns an error. The single highest-risk moment for the "it's actually building" belief.

Build-recovery — wait management + failure

The build is the moment the user shifts from evaluating to delighted-or-disappointed. A silent wait or a generic error is where the "it's actually building" belief dies.

While it runs (wait management)

Narrate the next concrete piece coming online — short, present-tense, plural: "wiring the booking calendar… setting up reminders… deploying." Never show "no active activity" or an opaque spinner during the most exciting moment. Tie the narration to their app's real pieces, not generic build steps.

When it fails

A generic "something went wrong, try again" is a belief-erosion event. An honest, specific narration is a belief-reinforcement event — a system that sees its own failure and fixes it is the strongest trust signal there is.

Name it with the cause if you have it: "the database setup hit a configuration edge case." If you don't: "the build stopped partway — I'm not sure why yet, here's what I can try." Never blame the user.
Offer the real paths, matched to the cause:
- transient → simple retry: rebuild directly.
- scope/spec issue → retry with refined inputs (back to naming/scope, then rebuild).
- structural mismatch revealed → this may actually be a disqualification; route there.
Keep the user's momentum: one short honest line, one clear next move, no doc-length apology.

More from this repository

same repository

business-requirements

QuantumByteOSS/quantumbyte

Read and hand-edit the app's business requirements — the checklist the harness verifies the built app against. MUST be loaded whenever the user asks to add, change, remove, reword, re-prioritise, or reclassify a business requirement (e.g. "add a requirement that…", "that rule is wrong, fix it", "drop the requirement about X", "make the closed-outlet rule critical"). The requirements are a plain JSON file in the app repo; edit it directly with the file tools, then create the lock marker so the change survives.

2026-07-14333

chat-formatting-widgets

QuantumByteOSS/quantumbyte

Governs the custom markdown widgets rendered in the QuantumByte chat interface. This includes the inline highlight-mark span (use on every question the user must answer). You must check this skill on every reply to format highlights.

2026-07-14333

disqualification

QuantumByteOSS/quantumbyte

The honest exit. Loads when qualification signals sustained-low or a realism failure (the ask is genuinely outside QB's wheelhouse). Acknowledges the mismatch plainly, suggests a realistic alternative, preserves dignity, and does not chase. A legitimate designed outcome, not a framework failure.

2026-07-14333

first-run-open

QuantumByteOSS/quantumbyte

Owns the opening move of first-run when the user has NOT handed you a substantive prompt (cold start), and sets the voice-vs-text opening posture for any open. Shows a provisional dream and a guess about who the user is, then learns from their correction (show-to-learn) and re-aims. Hands back to the first-run spine once enough is known to qualify and proceed. Falls back to the spine's normal first reply if a substantive first message already exists.

2026-07-14333

qualification

QuantumByteOSS/quantumbyte

Reads qualification signals from the user's input and passive context, sets the archetype and effort mode, and decides whether to proceed up the convince ladder or route to the disqualification skill. Runs alongside the first-run spine from the first substantive message onward. Falls back to "proceed at normal effort" if signals are unavailable.

2026-07-14333

name	build-recovery
description	Owns the build wait and build failure. Narrates the generation honestly while it runs, and when it errors, names the failure plainly with a real recovery path instead of a generic "oops". Loads when generation is long or returns an error. The single highest-risk moment for the "it's actually building" belief.

Build-recovery — wait management + failure

The build is the moment the user shifts from evaluating to delighted-or-disappointed. A silent wait or a generic error is where the "it's actually building" belief dies.

While it runs (wait management)

When it fails

Name it with the cause if you have it: "the database setup hit a configuration edge case." If you don't: "the build stopped partway — I'm not sure why yet, here's what I can try." Never blame the user.
Offer the real paths, matched to the cause:
- transient → simple retry: rebuild directly.
- scope/spec issue → retry with refined inputs (back to naming/scope, then rebuild).
- structural mismatch revealed → this may actually be a disqualification; route there.
Keep the user's momentum: one short honest line, one clear next move, no doc-length apology.