Update to drawDash - Sketch Challenge!

{
  "description": "Guide recovery of an interrupted Draw Guess round when the user reports a save failure, failed guessing or replay request, loading error, inaccessible uploaded image, or missing strokes after reload. Use visible evidence and existing retry controls; do not replace a recoverable round, promise stroke recovery, or claim access to private widget state.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 274
    }
  ],
  "name": "recover-drawing-round",
  "skill_md_contents": "---\nname: recover-drawing-round\ndescription: Guide recovery of an interrupted Draw Guess round when the user reports a save failure, failed guessing or replay request, loading error, inaccessible uploaded image, or missing strokes after reload. Use visible evidence and existing retry controls; do not replace a recoverable round, promise stroke recovery, or claim access to private widget state.\n---\n\n# Recover Drawing Round\n\n## Inputs\n\n- Use the user's visible error message, current buttons, and what happened immediately before the failure.\n- Use model-visible `modelContent.drawnImageId`, `modelContent.imageUrl`, `imageIds`, and recorded tool results when present.\n- Ask for the error text and whether the drawing was saved if the next action depends on those details. Do not inspect private finish flags, countdown state, or encrypted metadata.\n\n## Workflow\n\n1. Identify the stage from visible evidence or the user's report: loading, drawing, saving, awaiting a guess, or replay. Do not diagnose the stage from a file ID alone.\n2. Choose the matching recovery path:\n   - **Loading round:** Allow incomplete hydration to settle. If the widget explicitly reports that it could not load the round, explain that a fresh round is needed. Call `play-round` only when the user requests that replacement.\n   - **Could not save the drawing:** Guide the user to retry Finished while the current canvas remains open. Explain that the failed save leaves the drawing available in that mounted widget; avoid recommending reload.\n   - **Saving succeeded, but no guessing button yet:** Explain the four-second post-upload delay and direct the user to the Drawing saved dialog when it appears. Do not call `guess-subject` before a guessing request.\n   - **Could not ask ChatGPT to guess yet:** Guide the user to retry Ask ChatGPT to guess. Reuse the saved drawing; do not ask them to redraw or restart.\n   - **Saved round reopened:** Direct the user to its Ask ChatGPT to guess action. The widget refreshes the file's download URL before sending the request; do not claim the assistant can invoke that host API itself.\n   - **Uploaded image cannot be inspected:** Guide the user to retry the round's guessing action if it remains available. If it has already been sent and access is still unavailable, ask the user to attach the saved image if they have it. Do not make a visual guess without seeing it or assume an old URL still works.\n   - **Could not ask ChatGPT to start a new round yet:** Guide the user to retry Play again. Do not launch a duplicate round while a request is pending.\n   - **Strokes missing after reload:** Explain that countdown and round flags restore, but unfinished strokes do not. A previously uploaded PNG may still be available; unsaved strokes cannot be recovered by this skill. Let the user choose whether to redraw in the remaining time or request a new round.\n   - **No active draw-guess subject was found for this session:** Explain that the server has no active subject for scoring in this conversation. Do not score an old image by creating a random replacement subject; start a fresh drawable round only when requested.\n3. Resume the normal guess flow only after the user explicitly asks for a guess, the current image can be inspected, and its association with the active round is clear. Call `guess-subject` with one exact registered subject value and optional `reason`.\n4. When a new round is requested, call `play-round` with no arguments or optional `reason`, and explain that it starts a new random subject rather than restoring the old drawing.\n\n## Output\n\nGive the next concrete action and a short explanation of what the available evidence shows was retained or lost. State uncertainty when the reported error does not match a supported recovery path.\n\n## Boundaries\n\n- Guide widget actions; do not claim to click buttons, refresh host download URLs, reupload files, or restore private state.\n- Preserve recoverable rounds. Do not use `play-round` as a generic retry because it replaces the conversation's active subject.\n- Never decrypt metadata or probe `guess-subject` to recover the hidden word. Do not rescore older images after another round has started.\n"
}