Run History Skill Upgrader
Use real run evidence, validation failures, source drift, platform drift, and user...
Install
npx skills add dongshuyan/compass-skills --skill run-history-skill-upgrader -g -a claude-code -y- Repository
- dongshuyan/compass-skills764
- Category
- Marketing
- Updated
- 6d ago
- License
- MIT
- Context cost
- Mediumabout 1,554 tokens
- Runs scripts
- Yes, review before use
What it does
Use real run evidence, validation failures, source drift, platform drift, and user feedback to plan and, only after explicit approval, apply structural upgrades to an existing skill. Use when the user asks to improve an existing skill from recent runs, recurring failures, outdated sources, excessive bloat, changed platform behavior, or validated workflow feedback. Do not use to create a brand-new skill or to execute the business workflow itself.
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 thisSKILL.md. - Let
<python>mean the host's available Python launcher:python3,python, orpy -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.
plan_only: read the target skill and the agreed evidence scope, then produce a concrete upgrade plan and stop.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 ahead";
- the original request to improve a skill.
Valid approval must clearly point to the current plan, for example "approve plan A", "apply the plan above", or "yes, execute that upgrade plan".
