Rp User Action Recovery

Regenerates a stale durable human request without accepting an outdated answer.

1 minute · 300 words · 1 sections

Install

$ npx skills add wix/skills --skill rp-user-action-recovery

$ npx skills add wix/skills

» /plugin marketplace add wix/skills

The first command installs just this skill, by the name in its SKILL.md; the second installs the whole repository.

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, run node 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.

Colophon for this issue

Colophon

How this issue was made

Source

github.com/wix/skills, branch main, last pushed 8 November 2026.

Licence

MIT — the text of every skill is reproduced unmodified, frontmatter included, under the upstream licence.

Discovery

67 skills found by walking the repository tree for SKILL.md, not by matching a directory convention. 5 distinct layouts observed: skills/*/SKILL.md, skills/wix-headless-replatform/resources/*/SKILL.md, skills/wix-replatform/resources/*/SKILL.md, */SKILL.md, wix-replatform/resources/*/SKILL.md.

Duplicates collapsed

5 mirror copies folded into their canonical skill — republished for Alternate. Copies match on content hash and on position once a leading per-agent prefix is stripped, because the same skill is routinely shipped under a dozen agent directories with a dozen different hashes.

Issue colours

Resolved from a curated brand profile — hue 261°, chroma 0.190. Two accent tones are generated per issue and each is proven against its own ground before it ships: a single accent that passes AA on both light and dark paper is arithmetically impossible.

Heading repairs

1 repair applied to this skill so the document has one h1 and no skipped levels:

Removed “rp-user-action-recovery”, a leading h1 that duplicated the skill title.

Spec compliance

1 editorial note across 1 of 67 skills. They are printed in the margin of each skill rather than as errors here.

Wix Headless Kit — 1 note

Images

Images inside a skill come from the upstream repository. Where the author gave no alternative text we mark the image decorative rather than inventing a description — a plausible caption we made up is worse than none for the reader who depends on it.

Marketplace

A plugin manifest is published at .claude-plugin/marketplace.json by Wix, declaring 1 plugin. It is read for editorial metadata only — never as the skill index, which is always the repository tree.

Signal

Install counts come from skills.sh. They measure downloads, not quality, and an unranked repository is not an unread one.

Agent surfaces

The whole issue is available as one markdown document at /wix/skills.md, and each skill at its own .md URL.

Publication

Set by Skills Docs from the source repository. Body text is Literata at the reader’s chosen size and measure; code is Geist Mono. Nothing on this page was written by us except this paragraph.

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, run node 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.