run-history-skill-upgrader
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
Install / Use
npx skills add dongshuyan/compass-skills --skill run-history-skill-upgraderInstalls into whichever agent you are using.
SKILL.md
Installable skill definition
Quality Score
Category
AutomationSupported Platforms
Tags
Our assessment of run-history-skill-upgrader
run-history-skill-upgrader scores 87/100 on our quality scale, 1707th of 2,769 Automation skills we index.
Its SKILL.md is 6.6 KB long, well organised into 12 sections with 1 code example: a thorough specification that gives an agent plenty to work with.
It has 739 GitHub stars, a meaningful sign that others use it.
Maintenance, license and trust
- The repository was last updated about 3 months ago, so run-history-skill-upgrader is actively maintained.
- Our last check on 2026-11-02 found the source still online.
- It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
- Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.
Safety scan
No issues foundOur scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.
AI review by kimi-k2.7-code on 2026-10-04. Automated pattern scan on 2026-10-04. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.
run-history-skill-upgrader compared with similar skills
All 4 of these similar skills score higher than run-history-skill-upgrader; compare them before choosing.
| Skill | Score | Stars | Updated | Format |
|---|---|---|---|---|
| run-history-skill-upgrader (this skill)by dongshuyan | 87 | 739 | 3mo ago | SKILL.md |
| Agent-Reachby Panniantong | 100 | 112.7k | 9d ago | CLAUDE.md |
| rufloby ruvnet | 100 | 82.0k | today | CLAUDE.md |
| Claude-Code-Game-Studiosby Donchitos | 100 | 39.9k | 8d ago | CLAUDE.md |
| Scraplingby D4Vinci | 100 | 103.9k | today | MCP Server |
Frequently asked questions
- How do I install run-history-skill-upgrader?
- Run
npx skills add dongshuyan/compass-skills --skill run-history-skill-upgrader. The install tabs above show the steps for each supported agent. - Which AI agents does run-history-skill-upgrader work with?
- It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
- Is run-history-skill-upgrader safe to use?
- Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It is MIT-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
- Is run-history-skill-upgrader still maintained?
- The repository was last updated about 3 months ago, so run-history-skill-upgrader is actively maintained.
Skill content
View source on GitHubname: run-history-skill-upgrader description: 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".
Workflow
- Lock the target skill name and path.
- Lock
plan_onlyunless explicit post-plan approval already exists in the current conversation. - Lock the evidence scope: conversation, logs, screenshots, artifacts, diffs, tests, source docs, or user feedback.
- Read the current target skill before proposing changes.
- Classify the signals: process gap, validation gap, source drift, platform drift, user preference, candidate idea, incident, routing gap, or content bloat.
- Design the case set: incident, candidate rule, regression case, boundary case, and optional holdout challenge.
- Pass the generalization gate. A one-off incident does not automatically deserve a lasting rule.
- Map route impact. Remove weak routes and move machine-checkable facts to tools, tests, schema checks, diffs, validators, or files.
- Choose the net-improvement shape:
no_change,maintenance_note_only,prune_or_consolidate,local_refactor,cross_reference_refactor,major_refactor, ordeprecate_or_replace_source. - Produce the concrete plan and stop.
- Apply only after explicit approval.
- Validate, report what changed, and record follow-up risks.
Evidence Rules
Strong evidence:
- user feedback or corrections;
- real run outputs, logs, screenshots, tests, or diffs;
- actual target-skill files;
- official docs or first-party repositories that explain source or platform drift.
Weak evidence unless corroborated:
- one-off timeouts;
- one failed page load;
- a search snippet without opening the source;
- a model-generated idea with no supporting run evidence;
- a private path or one temporary filename presented as if it were a universal rule.
Upgrade Rules
- Prefer deleting or merging stale guidance over stacking new reminders on top.
- Keep examples only when they preserve complex behavior or important failure recovery.
- Temporary user preferences stay task-local unless the user clearly wants them kept as durable behavior.
- Holdout challenges are for post-apply validation, not for plan design.
- Do not ship an internal maintenance log with this released skill package. If the target skill already has one, update it only after approval and only if the user wants durable maintenance history there.
File-Editing Discipline
Before applying changes:
- read the target skill's
SKILL.md, relevantreferences/,scripts/,evals/, and optional agent metadata; - preserve unrelated user changes;
- capture a diff or snapshot reference when practical;
- edit only files that belong to the current approved plan.
Do not write credentials, browser sessions, private account data, unrelated personal paths, or hidden prompts into the target skill.
Validation
Run the bundled validator for this upgrader skill:
<python> <skill-dir>/scripts/validate_upgrade_artifacts.py --skill <skill-dir>
This bundled validator checks package structure, the portable Agent Skills frontmatter field set, referenced paths, JSON shape, Python syntax, common private-path leaks, and the upgrader's required approval terms. Its dependency-free frontmatter preflight accepts scalar fields, block text, and one-level string metadata; it rejects other YAML forms instead of guessing. A specific host may accept different syntax or a narrower field set, so its canonical validator remains authoritative for installation there. Neither structural check runs the eval cases or proves that an upgrade improves behavior.
Then run the target skill's own validator and the smallest relevant technical checks:
python -m py_compilefor modified Python scripts;python -m json.toolfor edited JSON files;- trigger regression if the frontmatter
descriptionchanged; - route and boundary regression if the workflow changed;
- comparison against the original failure, at least one similar positive case, and at least one near-negative case for high-risk upgrades.
Do not claim that the upgrade is complete if validation was skipped or failed.
Final Response
Report:
- the target skill and path;
- whether the result is plan-only or applied;
- evidence sources actually used;
- files actually changed;
- validation commands actually run and their results;
- deleted or rejected ideas and why;
- remaining risks or follow-up checks.
References
references/evidence-and-scope.mdreferences/upgrade-decision-protocol.mdreferences/validation-and-regression.mdreferences/examples.mdscripts/validate_upgrade_artifacts.pyevals/evals.json
Related Skills
Agent-Reach
112.7kGive your AI agent eyes to see the entire internet. Read & search Twitter, Reddit, YouTube, GitHub, Bilibili, XiaoHongShu — one CLI, zero API fees.
ruflo
82.0k🌊 The original agent harness. Deploy intelligent multi-player swarms, coordinate autonomous workflows, and build conversational AI systems. Features adaptive memory, self-learning intelligence, federation, vector RAG integration, and native Claude Code / Codex / Hermes and many more Integrated
Claude-Code-Game-Studios
39.9kTurn Claude Code into a full game dev studio — 49 AI agents, 75 workflow skills, and a complete coordination system mirroring real studio hierarchy.
Scrapling
103.9k🕷️ The BEST Web Scraping framework that handles everything from a single request to a full-scale crawl! Don't be shy, join here: https://discord.gg/EMgGbDceNQ and follow here for daily tips and tricks: https://x.com/Scrapling_dev
Languages
Trust signals
From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.
