
Deleting Thoughts
Use when asked to delete, remove, purge, wipe, or "get rid of" an Open Brain thought...
Install
npx skills add NateBJones-Projects/OB1 --skill deleting-thoughts -g -a claude-code -y- Repository
- NateBJones-Projects/OB14.8k
- Category
- Engineering
- Updated
- 3d ago
- License
- See repository
- Context cost
- Lightabout 887 tokens
- Runs scripts
- No, instructions only
What it does
Use when asked to delete, remove, purge, wipe, or "get rid of" an Open Brain thought, or before calling delete_thought (the open-brain-delete-thought connector), which HARD-deletes with no undo. Also use when tempted to delete a thought that is merely outdated or wrong. To edit or deprecate instead of removing, see updating-thoughts.
Deleting Thoughts
Overview
delete_thought (the open-brain-delete-thought connector) performs a hard
delete, the row is gone the moment it returns, with no tombstone, no
soft-delete, and no restore. Recovery depends entirely on database backups. The
Open Brain maintainer's stance is "deprecate and version rather than
delete." So deletion is a last resort, and every delete must target an id you
verified this session.
Violating the letter of these rules is violating their spirit.
When to Use
Delete only when both hold:
- The thought is genuinely disposable, a test/throwaway, an exact duplicate, or an accidental capture, and
- Editing or tagging it is not good enough.
If the thought is merely outdated, wrong, or superseded, update it or tag it
superseded instead, see the updating-thoughts skill.
Process
- Resolve the id via
search_thoughts/list_thoughts.delete_thoughttakes a UUID; never delete an id you typed from memory. - Show the target and confirm. Surface the thought's content to the user
and get explicit confirmation that this specific thought should be removed.
- Check for derivatives first. Before deleting, run
find_derivatives(and/orrelated_thoughts) on the thought. If other thoughts were derived from it, deleting orphans their provenance chain, those derivatives lose the source they point back to. Prefer deprecating over deleting in that case. Tool names may carry a connector prefix; use whatever the environment exposes.
- Check for derivatives first. Before deleting, run
- Delete only after confirmation. Call
delete_thought(id). It pre-checks existence (a clean "not found" if already gone) and returns the prior content length as a receipt. Report that receipt to the user.
