Rp User Action Recovery
WixOfficialPublished by Wix
- Skill
- Workflow
- Automation and integrations
- MIT
- No issues found
AutoGineer summary
Written by AutoGineer from the skill’s own files, not by the author
The rp-user-action-recovery skill provides a structured workflow for handling stale human action requests in an automated system. When a request becomes stale due to changes or loss of pinned evidence, this skill guides the user through the process of safely regenerating the request. It ensures that outdated answers are not accepted, maintains the integrity of the request lifecycle by superseding stale entries, and requires the creation of fresh, valid requests that reflect the current state of reviewed artifacts.
What it does
- Identifies and inspects stale user action requests reported by the system.
- Executes specific recovery commands for omission acknowledgments.
- Rebuilds missing review evidence based on the producing stage's contract.
- Creates new pending requests with updated evidence and artifact hashes.
- Supersedes stale requests with fresh replacements to ensure valid human input.
- Preserves audit trails by keeping superseded requests in the orchestration directory.
When to use it
- When the system router reports a user_action_stale error.
- When pinned evidence for a human request has changed or disappeared.
- When you need to ensure a human decision is based on current, accurate evidence.
- When you need to replace an invalid or outdated request without losing existing approval records.
Advantages
- Prevents the use of outdated or unsafe human decisions.
- Maintains a clear audit trail of superseded requests.
- Ensures that new requests are correctly linked to current artifact hashes.
- Provides a standardized recovery path for blocked human-in-the-loop processes.
Usage examples
- “The system reported a user_action_stale error for request ID 123. How do I recover it?”
- The agent will guide you to inspect the request, rebuild the evidence, create a new request, and supersede the stale ID 123 with the fresh request ID.
- “How do I handle a stale read-back-omission-ack request?”
- The agent will execute the recover-omission-ack command to rebuild evidence and route the new request for human approval.
Install
Download the skill as a ZIP:
https://mp-staging.autogineer.com/agent-skills/wix/rp-user-action-recovery/downloadUnzip it into the cross-client skills folder of your project:
mkdir -p .agents/skills && unzip rp-user-action-recovery.zip -d .agents/skills
Documentation by Wix
rp-user-action-recovery
Use when the router reports user_action_stale. The request's pinned evidence changed
or disappeared, so answering it is unsafe. Recover only the reported requestIds.
Read each request through
scripts/user-action.js show --project <projectDir> --request <id>. Identify its stage, effect and pinned artifacts. Do not read secret-bearing config into tool output. Preserve the existing request and all recorded answers.For effect
read-back-omission-ack, runnode scripts/user-action.js recover-omission-ack --project <projectDir> --request <stale-id>. Its producer rebuilds the evidence from approved omissions, checkpoints the new request and ledger bindings, then supersedes the old request. Retry the same command after an interruption. Changed mapping/import inputs require revalidation by their producing stage; do not refresh their hashes. Regenerate the completion report so its operator action uses the new request, then route again for the human answer. Skip the generic steps below.Use the producing stage's contract to rebuild any missing review evidence and prepare a fresh explanation and choices for the current evidence. Do not merely change the old digest, reuse outdated prose, answer on the user's behalf, or perform setup/import writes. If the evidence cannot be regenerated, report the specific repair needed and stop.
Create a new pending request with the same stage, kind and effect scope through
scripts/user-action.js create --project <projectDir> --request-file <json>. Pin the current reviewed artifacts. An evidence digest may change; the subject and permission being requested must remain the same. A materially different decision needs its own producer-owned recovery rather than silently changing this request's scope.Only after the replacement exists, run:
node scripts/user-action.js supersede --project <projectDir> --request <stale-id> --replacement <fresh-id>. This refuses a missing, answered, stale or differently scoped replacement. No approval effect is applied. Route again and present the fresh request for a human answer.
Output
The old request remains in orchestration/user-actions/ as superseded; a fresh pending
replacement carries the current review and artifact hashes. Approvals remain unchanged.
If recovery is blocked, preserve the old request and identify the required repair.
Files
- ATTRIBUTION.mdAdded by AutoGineer858 B
- LICENSELicence file added by AutoGineer1.0 KiB
- SKILL.md2.5 KiB
Requirements and compatibility
Works with: Claude Code, Claude apps, OpenAI Codex, GitHub Copilot, Cursor, Gemini CLI, Kiro, OpenCode, Goose, Amp, Roo Code, JetBrains Junie, Factory Droid, Devin (ex-Windsurf), Mistral Vibe, OpenHands, Letta
“Works with” means the tool reads the open Agent Skills format; a skill written for one tool may use features others lack.
Needs: Needs Node.js
Security
No issues found by our static scan· No issues found
A static scan is not a guarantee. Skills are third-party content: review a skill before you let an agent use it.
Attribution and licence
- Published by
- Wix
- Publisher
- Wix (Official)
- Source
- wix/skills · skills/wix-replatform/resources/rp-user-action-recovery · commit d168bc2
- Licence
- MIT License (redistribution allowed)
- LICENSE (added by AutoGineer from LICENSE)
- ATTRIBUTION.md (written by AutoGineer)
- Synced
AutoGineer is not affiliated with or endorsed by Wix.
Download ZIP
The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download rp-user-action-recovery.zip