Verified State Changes
Makes scoped state changes with target checks, minimal edits and read-back verification.
Install
npx skills add odysseus-dev/odysseus --skill verified-state-change -g -a claude-code -y- Repository
- odysseus-dev/odysseus94.9k
- Category
- AI and agents
- Updated
- 3d ago
- License
- AGPL-3.0
- Context cost
- Lightabout 354 tokens
- Runs scripts
- No, instructions only
What it does
Make scoped state changes with target confirmation, minimal mutation, and read-back verification
When to Use
Use when creating, editing, deleting, moving, sending, scheduling, or otherwise changing persistent state through an application, API, filesystem, or service.
Procedure
- Read the current state and identify the target using stable identifiers plus enough content to disambiguate it.
- Preserve fields the user did not ask to change and choose the narrowest supported mutation.
- For destructive or externally visible actions, confirm that the user's instruction authorizes the exact target and effect.
- Perform the mutation once and capture the returned identifier, status, or revision.
- Read the target again through an independent list, fetch, status, or content operation.
- Compare the observed state with the requested outcome and repair only the specific mismatch.
Pitfalls
- Do not infer the target from a stale active item when a stable identifier can be fetched.
- Do not report success from an accepted request alone; asynchronous or partial operations may not have completed.
- Do not replace an entire object when a field-level update is supported and safer.
- Do not silently broaden a mutation to adjacent files, records, accounts, or services.
Verification
- The target identity was confirmed before mutation.
- A read-back shows the intended values and preserves unrelated state.
- Any external effect has a concrete status, identifier, or observable result.
