run-history-skill-builder

# Run History Skill Builder ## Language Policy Write all user-facing output in the user's language. Default to Chinese when the language is unknown. ## Role Turn real run history into a new skill package, a plan-only skill design, or an upgrade handoff when the request is actually about an existing skill. ## 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. - Before writing files, lock the output directory. If the user does not provide one, propose a neutral local target such as the current repository's `skills/` directory or the host agent's documented local skills directory, then wait for confirmation. ## Workflow 1. Lock intent: decide whether the request is `plan_only`, `new_single_skill`, `router_skill`, `skill_suite`, or `existing_skill_upgrade_handoff`. 2. Lock evidence scope: confirm which conversation turns, files, logs, artifacts, diffs, browser flows, or ...