verified-state-change

Agent Skills › odysseus-dev/odysseus › verified-state-change

verified-state-change

GitHub

提供持久化状态变更的标准流程，涵盖读取、最小化修改、用户确认及读回验证，确保操作安全与数据一致性。

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

触发场景

创建、编辑或删除数据记录通过API或文件系统修改配置执行具有破坏性或外部可见性的状态变更

安装

npx skills add odysseus-dev/odysseus --skill verified-state-change -g -y

更多选项

非标准路径

npx skills add https://github.com/odysseus-dev/odysseus/tree/dev/resources/skills/agent/verified-state-change -g -y

不安装直接使用

npx skills use odysseus-dev/odysseus@verified-state-change

指定 Agent (Claude Code)

npx skills add odysseus-dev/odysseus --skill verified-state-change -a claude-code -g -y

安装 repo 全部 skill

npx skills add odysseus-dev/odysseus --all -g -y

预览 repo 内 skill

npx skills add odysseus-dev/odysseus --list

SKILL.md

Frontmatter

{
    "name": "verified-state-change",
    "tags": [
        "state",
        "mutation",
        "verification",
        "safety"
    ],
    "owner": "",
    "source": "builtin",
    "status": "published",
    "created": "2026-08-30T00:00:00Z",
    "version": "1.0.0",
    "category": "agent",
    "confidence": 1,
    "description": "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.