run-history-skill-upgrader

# Run History Skill Upgrader ## Language Policy Write all user-facing output in the user's language. Default to Chinese when the language is unknown. ## Role Turn real run feedback into structural net improvement for an existing skill. Upgrades may add, modify, merge, delete, deprecate, or decide not to change anything. ## Portability This skill is agent-agnostic. It should work in Codex, Claude Code, OpenCode, OpenClaw, Hermes, and similar local agent hosts that can read `SKILL.md` plus optional `references/`, `scripts/`, `evals/`, and `agents/`. - Resolve `<skill-dir>` from the directory that contains this `SKILL.md`. - Let `<python>` mean the host's available Python launcher: `python3`, `python`, or `py -3`. - Do not assume a fixed skill root, shell, home-directory layout, or path separator. - Placeholder paths such as `<skill-dir>/scripts/...` describe path segments, not a required separator style. On Windows, use the separator style that your shell or harness accepts. - Treat platform-specific helper tooling as optional. Use it only when it is actually available. ## Mandatory Two-Stage Approval This skill always starts in `plan_only`. 1. `plan_only`: read the target skill and the agreed evidence scope, then produce a concrete upgrade plan and stop. 2. `apply_after_approval`: modify files only after the user explicitly approves that specific plan. The following are **not** approval by themselves: - "upgrade it"; - "directly edit it"; - "don't ask me"; - "go ah...