CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

verified-state-change

Make scoped state changes with target confirmation, minimal mutation, and read-back verification

Quality

76%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./resources/skills/agent/verified-state-change/SKILL.md
SKILL.md
Quality
Evals
Security

When to Use

Use when creating, editing, deleting, moving, sending, scheduling, or otherwise changing persistent state through an application, API, filesystem, or service.

Procedure

  1. Read the current state and identify the target using stable identifiers plus enough content to disambiguate it.
  2. Preserve fields the user did not ask to change and choose the narrowest supported mutation.
  3. For destructive or externally visible actions, confirm that the user's instruction authorizes the exact target and effect.
  4. Perform the mutation once and capture the returned identifier, status, or revision.
  5. Read the target again through an independent list, fetch, status, or content operation.
  6. 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.
Repository

odysseus-dev/odysseus

Path

resources/skills/agent/verified-state-change/SKILL.md

Last updated
First committed

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.