Agent skill

Forgiveness Undo And Soft Delete

by hashgraph-online in hashgraph-online/awesome-codex-plugins

A skill your agent uses when designing reversibility — undo systems, soft delete, archive-with-recovery, version history, "Undo Send" patterns, and any mechanism that lets a user step back from an…

Apache-2.0Auto-check passed

Install Forgiveness Undo And Soft Delete

skills CLI
$ npx skills add hashgraph-online/awesome-codex-plugins --skill forgiveness-undo-and-soft-delete -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install hashgraph-online/awesome-codex-plugins forgiveness-undo-and-soft-delete --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/hashgraph-online/awesome-codex-plugins.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/HDeibler/universal-design-principles/plugins/interaction-and-control-principles/skills/forgiveness-undo-and-soft-delete .claude/skills/forgiveness-undo-and-soft-delete && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
forgiveness-undo-and-soft-delete
GitHub stars
1.3k
Token cost
~2.2k tokens
SKILL.md length
993 words
Files
2 (incl. references)
Skills in repo
716
Repo updated
First seen
Licence
Apache-2.0

At a glance

A skill your agent uses when designing reversibility — undo systems, soft delete, archive-with-recovery, version history, "Undo Send" patterns, and any mechanism that lets a user step back from an…

  • Works in 3 steps: The "did they recover?" check. Look at… → The toast-button audit. For every… → The trash audit. Is there a Trash /…
  • Designing reversibility — undo systems
  • SKILL.md covers The reversibility ladder, Choosing the right…, When reversibility isn't… and Recovery window length, plus 4 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Forgiveness Undo And Soft Delete is an agent skill from hashgraph-online/awesome-codex-plugins. Use this skill when designing reversibility — undo systems, soft delete, archive-with-recovery, version history, "Undo Send" patterns, and any mechanism that lets a user step back from an action they regret. Trigger when designing destructive actions you want to be safe rather than friction-heavy, when picking between confirmation dialogs and undo toasts, when defining recovery windows, or when planning version-history features. Sub-aspect of forgiveness; read that first.

Its SKILL.md is about 2.2k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including reference files (for example `references/undo-pattern-history.md`).

The repository describes itself as: A curated list of awesome OpenAI Codex / ChatGPT plugins, skills, and resources. The 1 Codex Marketplace. See live plugins at: https://hol.org/plugins/best-codex-plugins. The licence is Apache-2.0.

When your agent uses it

  • Designing reversibility — undo systems
  • Archive-with-recovery
  • Version history
  • Undo Send patterns

Example prompts

  • “Undo Send”
  • “/forgiveness-undo-and-soft-delete”

Workflow steps

3 steps, taken from the first numbered list in SKILL.md.

  1. The "did they recover?" check. Look at support tickets for data loss. Each one is a reversibility failure.
  2. The toast-button audit. For every destructive action, is there a toast with Undo? If not, why not?
  3. The trash audit. Is there a Trash / Archive / Recycle Bin in your app? If items can be deleted but there's no recovery view, you're…

What it can do on your machine

Read from SKILL.md and the folder at commit 3e1456a. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are javascript).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Forgiveness Undo And Soft Delete loads about 2.2k tokens when it runs, and up to ~3.3k if it reads all its reference files. Until then it costs about 128 tokens; SKILL.md has 993 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~128
When it runs · the whole SKILL.md, loaded when a task matches
~2.2k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~3.3k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from hashgraph-online/awesome-codex-plugins at commit 3e1456a, republished under its Apache-2.0 licence (© hashgraph-online). 993 words, ~2,200 tokens.

Download SKILL.mdSave it as .claude/skills/forgiveness-undo-and-soft-delete/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
forgiveness-undo-and-soft-delete
description
Use this skill when designing reversibility — undo systems, soft delete, archive-with-recovery, version history, "Undo Send" patterns, and any mechanism that lets a user step back from an action they regret. Trigger when designing destructive actions you want to be safe rather than friction-heavy, when picking between confirmation dialogs and undo toasts, when defining recovery windows, or when planning version-history features. Sub-aspect of `forgiveness`; read that first.

Forgiveness through reversibility

Reversibility is the highest-leverage form of forgiveness short of structural prevention. It makes destructive actions safe by allowing recovery — users keep speed (no friction up front) and safety (the action is undoable). Whenever an action can be made reversible, that's almost always preferable to confirming it.

The reversibility ladder

Different actions need different reversibility approaches:

Synchronous undo (Cmd-Z)

The classic. The user takes an action; pressing Cmd-Z (or Ctrl-Z) reverses it. Multi-level undo lets the user back out through a sequence of actions.

When it applies: editing operations on a single object — text editing, image manipulation, design tool actions, code edits.

Implementation pattern:

  • Maintain an undo stack of inverse operations.
  • On each action, push the inverse onto the stack.
  • On Cmd-Z, pop and apply the inverse.
  • On any new action after undo, optionally clear the redo stack (or maintain redo separately).
js
const undoStack = [];
const redoStack = [];

function executeAction(action) {
  action.do();
  undoStack.push(action);
  redoStack.length = 0;
}

function undo() {
  const action = undoStack.pop();
  if (!action) return;
  action.undo();
  redoStack.push(action);
}

function redo() {
  const action = redoStack.pop();
  if (!action) return;
  action.do();
  undoStack.push(action);
}
Toast-with-undo (the modern default for one-off destructive actions)

The user takes an action that destroys or moves data; a toast appears with an "Undo" button for several seconds.

When it applies: archive, delete, move-to-folder, mark-read, and similar one-shot list actions.

Implementation pattern:

  • Optimistically update the UI (item disappears).
  • Send the destructive request to the server (or defer it for the undo window).
  • Show a toast with an Undo affordance for 5–10 seconds.
  • On Undo: reverse the optimistic update, cancel/reverse the server action.
  • On timeout: commit the action permanently.
js
async function archive(item) {
  const previous = items.slice();
  items = items.filter(i => i.id !== item.id);
  render();

  let undone = false;
  showToast(`"${item.name}" archived`, {
    action: { label: 'Undo', onClick: () => { undone = true; items = previous; render(); } },
    duration: 7000,
    onDismiss: () => { if (!undone) api.commitArchive(item.id); }
  });
}

The user gets the speed of "click and it happens" plus the safety of "you have 7 seconds to undo."

Soft delete with explicit recovery

A delete that doesn't actually remove the data — instead moves it to a recoverable state for some window (30 days, indefinitely, until storage cleanup).

When it applies: account-level data the user might want back later; emails, documents, files. Common in B2B SaaS.

Implementation pattern:

  • Mark the item as deleted with a timestamp.
  • Hide it from default views.
  • Provide a "Trash" or "Archive" view where deleted items can be restored.
  • After the recovery window, hard-delete via background job.
js
// Soft delete
async function softDelete(item) {
  await api.update(item.id, { deletedAt: new Date(), deletedBy: currentUser.id });
}

// In default queries
const visibleItems = items.filter(i => !i.deletedAt);

// Recovery view
const trashedItems = items.filter(i => i.deletedAt && daysAgo(i.deletedAt) < 30);

async function restore(item) {
  await api.update(item.id, { deletedAt: null, deletedBy: null });
}
Version history

The strongest reversibility: every state of the object is preserved; the user can return to any prior state.

When it applies: documents, code, designs, configurations — anything users edit over time and might want to revert.

Implementation pattern:

  • Snapshot the object on each meaningful change (or at intervals, or on explicit save).
  • Provide a "Version history" UI listing past states.
  • Allow viewing, restoring, or branching from any prior version.

Google Docs, Notion, Figma, GitHub all implement this. The user never fears editing because they can always restore.

The "Undo send" pattern

Gmail's pattern: an action that appears committed actually defers for a few seconds, allowing cancellation in that window.

When it applies: actions that the user often regrets immediately after triggering — sending an email, posting publicly, sending a message.

Implementation pattern:

  • On "Send," show "Sending..." with an Undo affordance for N seconds.
  • Don't actually transmit until N seconds elapse with no Undo.
  • On Undo, return to draft state.

The user feels they sent it; the system just defers commitment briefly. The defer window is short (5–30 seconds) — long enough to catch reflexive "wait!" moments, short enough not to delay genuine sends.

Choosing the right reversibility approach

Action typeRecommended reversibility
Text/edit/format changeSynchronous undo (Cmd-Z)
Archive / soft delete one itemToast-with-undo
Hard delete / account changesSoft delete + recovery view
Document editsVersion history + Cmd-Z
Send / publish / postUndo-send window
Bulk destructiveSoft delete + bulk-restore in trash
Show full SKILL.md (422 more words)Show less

When reversibility isn't possible

Some actions genuinely can't be reversed at the data layer:

  • External communications (sent emails, sent SMS, public tweets) — the recipient already saw it.
  • Financial transfers — money has moved.
  • Compliance / legal commits — once signed, signed.
  • Hardware operations — once a physical command goes to a robot or printer, it's done.

For these, lean on the next-strongest forgiveness levels: structural prevention (good affordances), confirmation (deliberate intent), and warnings.

The "Undo send" pattern bridges this for some communications: the external action is still irreversible, but the system delays it long enough for the user to catch second thoughts.

Recovery window length

For toast-with-undo: 5–10 seconds is the typical range.

  • < 5 seconds: too short for users who realized after a moment of reflection.
  • 5–7 seconds: covers most reflexive corrections.
  • 10+ seconds: lingers; some users dismiss the toast before reading it.

For soft delete: 7–30 days is typical.

  • 7 days: balances storage cost with user recovery needs.
  • 30 days: standard for most SaaS; forgiving enough for vacations and weekends.
  • Indefinite: storage cost grows but maximum forgiveness.

Discoverability of recovery

A reversibility mechanism that users don't know exists doesn't help. Patterns:

  • Toast affordance is its own discovery — users see the Undo button and learn the pattern.
  • "Trash" or "Archive" navigation entry signals that deleted items can be recovered.
  • Onboarding mention for version history ("All changes saved. View history at any time.").

If users are filing tickets to recover data they could have restored themselves, the recovery affordance isn't visible enough.

Anti-patterns

  • Toast that vanishes too fast. A 2-second toast with an Undo button most users never see.
  • Soft delete with no recovery UI. Items go to a "trash" the user can't access.
  • Version history that's hidden. Buried under three menu levels; users don't know it exists.
  • Cmd-Z that doesn't undo destructive actions. Some apps undo formatting but not deletion. Inconsistent.
  • Undo that fails silently. Click Undo; nothing happens; no error; user is confused. If undo fails, say so.

Heuristics

  1. The "did they recover?" check. Look at support tickets for data loss. Each one is a reversibility failure.
  2. The toast-button audit. For every destructive action, is there a toast with Undo? If not, why not?
  3. The trash audit. Is there a Trash / Archive / Recycle Bin in your app? If items can be deleted but there's no recovery view, you're missing soft delete.
  • forgiveness (parent).
  • forgiveness-confirmation-and-prevention — the alternative when reversibility isn't possible.
  • feedback-loop — toast-with-undo is feedback that doubles as reversibility.
  • factor-of-safety (process) — engineering analog of "design with margin so errors are recoverable."

© hashgraph-online, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 1 other file (references) in plugins/HDeibler/universal-design-principles/plugins/interaction-and-control-principles/skills/forgiveness-undo-and-soft-delete of hashgraph-online/awesome-codex-plugins.

  • SKILL.md
  • references/undo-pattern-history.md

Open the folder on GitHubat commit 3e1456a

Compare with similar skills

Forgiveness Undo And Soft Delete next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Forgiveness Undo And Soft Delete compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Forgiveness Undo And Soft Delete this skillhashgraph-online/awesome-codex-plugins1.3k—~2.2kAutomated safety check: PassApache-2.0
Design Systemaffaan-m/ECC276k—~698Automated safety check: PassMIT
Design Guidepaperclipai/paperclip99k1 repos~3.1kAutomated safety check: PassMIT
Design Audit Against Rams' Principlesthedotmack/claude-mem99k—~4.6kAutomated safety check: PassApache-2.0
Figma Design to Codewarpdotdev/warp65k4 repos~2.9kAutomated safety check: PassAGPL-3.0
Design Consultationgarrytan/gstack136k—~15kAutomated safety check: NotesMIT

Similar skills

  • Design System

    affaan-m/ECC

    Generate a design system from an existing codebase or audit one for visual consistency: extract tokens (colors, typography, spacing, shadows) into design-tokens.json and CSS custom properties with…

    276k GitHub stars~698 tokensUpdated today
    Frontend & DesignAuto-check passed
  • Design Guide

    paperclipai/paperclip

    Paperclip UI design system guide for building consistent, reusable frontend components.

    99k GitHub starsUsed in 1 repo~3.1k tokens
    Frontend & DesignAuto-check passed
  • Audits a design against Dieter Rams' ten principles of good design, scores each with evidence, and hands off a make-plan prompt for a new, refined or redesigned outcome.

    99k GitHub stars~4.6k tokensUpdated yesterday
    Frontend & DesignAuto-check passed
  • Figma Design to Code

    warpdotdev/warp

    Turns a Figma frame or component into production code that matches the design, using the Figma MCP server and the project's own design system.

    65k GitHub starsUsed in 4 repos~2.9k tokens
    Frontend & DesignAuto-check passed
  • Design Consultation

    garrytan/gstack

    Learns about your product, studies the landscape and writes a DESIGN.md with a full design system covering type, color, layout, spacing and motion.

    136k GitHub stars~15k tokensUpdated yesterday
    Frontend & DesignAuto-check: notes
  • Product Design Workflow Bundle

    XiaomiMiMo/MiMo-Code

    Entry point to a bundle of product design workflows covering context, research, audits, ideation, URL or image to code, design QA and sharing a prototype.

    14k GitHub stars~721 tokensUpdated yesterday
    Frontend & DesignAuto-check passed

More from hashgraph-online/awesome-codex-plugins

All 716 skills in this repo
  • Anime Reaction Gif

    hashgraph-online/awesome-codex-plugins

    Create original anime-style reaction stickers as looping GIFs and MP4 previews, using generated character pose sheets and timed key poses.

    1.3k GitHub stars~922 tokensUpdated today
    Auto-check passed
  • Calibredb

    hashgraph-online/awesome-codex-plugins

    Manage and query Calibre libraries with the calibredb CLI (local paths or Calibre Content server URLs).

    1.3k GitHub stars~1k tokensUpdated today
    Auto-check passed
  • Rust API Test Harness

    hashgraph-online/awesome-codex-plugins

    A skill your agent uses when adding, changing, testing, or debugging Rust HTTP APIs and services, especially when Codex needs black-box integration tests, random-port app startup, real database test…

    1.3k GitHub stars~1.7k tokensUpdated today
    Auto-check passed
  • Art

    hashgraph-online/awesome-codex-plugins

    Make a studio's game look like something at build time — a cover from a real frame of the game (free), painted covers, backdrops, textures and character plates from image models through the…

    1.3k GitHub stars~2.4k tokensUpdated today
    Auto-check passed
  • Calle

    hashgraph-online/awesome-codex-plugins

    Use CALL-E from Codex through the calle CLI. An agent skill from hashgraph-online/awesome-codex-plugins.

    1.3k GitHub stars~2.9k tokensUpdated today
    Auto-check passed
  • Game Balance Economy

    hashgraph-online/awesome-codex-plugins

    Balance game difficulty, resources, rewards, probability, progression, economies, and dominant strategies.

    1.3k GitHub stars~618 tokensUpdated today
    Auto-check passed

Questions about Forgiveness Undo And Soft Delete

What does Forgiveness Undo And Soft Delete do?

A skill your agent uses when designing reversibility — undo systems, soft delete, archive-with-recovery, version history, "Undo Send" patterns, and any mechanism that lets a user step back from an…. Forgiveness Undo And Soft Delete is an agent skill from hashgraph-online/awesome-codex-plugins. Use this skill when designing reversibility — undo systems, soft delete, archive-with-recovery, version history, "Undo Send" patterns, and any mechanism that lets a user step back from an action they regret.

When should I use Forgiveness Undo And Soft Delete?

Forgiveness Undo And Soft Delete fits situations like: designing reversibility — undo systems; archive-with-recovery; version history; undo Send patterns.

How do I install Forgiveness Undo And Soft Delete in Claude Code?

Run `npx skills add hashgraph-online/awesome-codex-plugins --skill forgiveness-undo-and-soft-delete -a claude-code`. Or copy the skill folder (plugins/HDeibler/universal-design-principles/plugins/interaction-and-control-principles/skills/forgiveness-undo-and-soft-delete in hashgraph-online/awesome-codex-plugins) into .claude/skills/forgiveness-undo-and-soft-delete in your project. Claude Code loads it when a task matches its description.

How do I install Forgiveness Undo And Soft Delete in Codex?

Run `npx skills add hashgraph-online/awesome-codex-plugins --skill forgiveness-undo-and-soft-delete -a codex`. Or copy the skill folder (plugins/HDeibler/universal-design-principles/plugins/interaction-and-control-principles/skills/forgiveness-undo-and-soft-delete in hashgraph-online/awesome-codex-plugins) into .agents/skills/forgiveness-undo-and-soft-delete in your project. Codex loads it when a task matches its description.

Can I use Forgiveness Undo And Soft Delete in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add hashgraph-online/awesome-codex-plugins --skill forgiveness-undo-and-soft-delete -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/forgiveness-undo-and-soft-delete, .gemini/skills/forgiveness-undo-and-soft-delete, .github/skills/forgiveness-undo-and-soft-delete and .opencode/skills/forgiveness-undo-and-soft-delete in your project.

What does Forgiveness Undo And Soft Delete need to run?

SKILL.md names no scripts, command-line tools or credentials: Forgiveness Undo And Soft Delete is instructions for the agent only.

Does Forgiveness Undo And Soft Delete access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Forgiveness Undo And Soft Delete safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Forgiveness Undo And Soft Delete use?

Forgiveness Undo And Soft Delete is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Forgiveness Undo And Soft Delete use?

About 2.2k tokens (SKILL.md is roughly 8.8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 1.1k tokens, read only when the agent opens those files.

What are the alternatives to Forgiveness Undo And Soft Delete?

Skills that share tags, products or a category with Forgiveness Undo And Soft Delete: Design System (affaan-m/ECC, 276k stars), Design Guide (paperclipai/paperclip, 99k stars), Design Audit Against Rams' Principles (thedotmack/claude-mem, 99k stars) and Figma Design to Code (warpdotdev/warp, 65k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Forgiveness Undo And Soft Delete?

hashgraph-online (a GitHub organization) maintains it in hashgraph-online/awesome-codex-plugins, which has 1,267 GitHub stars. The repository holds 716 skills in this directory. The repository was last updated on October 10, 2026.

Source: hashgraph-online/awesome-codex-plugins on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.