run-history-skill-builder
Turn a completed task, browser flow, artifact pipeline, failure-recovery trace, or repeatedly refined workflow into a new reusable skill package or a reviewed skill-design plan
Install / Use
npx skills add dongshuyan/compass-skills --skill run-history-skill-builderInstalls into whichever agent you are using.
SKILL.md
Installable skill definition
Quality Score
Category
AutomationSupported Platforms
Our assessment of run-history-skill-builder
run-history-skill-builder scores 87/100 on our quality scale, 1706th of 2,769 Automation skills we index.
Its SKILL.md is 7.2 KB long, well organised into 11 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-builder is actively maintained.
- Our last check on 2026-10-11 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-builder compared with similar skills
All 4 of these similar skills score higher than run-history-skill-builder; compare them before choosing.
| Skill | Score | Stars | Updated | Format |
|---|---|---|---|---|
| run-history-skill-builder (this skill)by dongshuyan | 87 | 739 | 3mo ago | SKILL.md |
| taste-skillby Leonxlnx | 100 | 117.6k | 9d ago | CLAUDE.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 |
Frequently asked questions
- How do I install run-history-skill-builder?
- Run
npx skills add dongshuyan/compass-skills --skill run-history-skill-builder. The install tabs above show the steps for each supported agent. - Which AI agents does run-history-skill-builder 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-builder 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-builder still maintained?
- The repository was last updated about 3 months ago, so run-history-skill-builder is actively maintained.
Skill content
View source on GitHubname: run-history-skill-builder description: Turn a completed task, browser flow, artifact pipeline, failure-recovery trace, or repeatedly refined workflow into a new reusable skill package or a reviewed skill-design plan. Use when the user asks to make a new skill from real run history, extract a reusable workflow from conversation/logs/files, summarize lessons into a new skill, or produce a plan before writing files. Do not use to upgrade an existing skill or to execute the business workflow itself.
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 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. - 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
- Lock intent: decide whether the request is
plan_only,new_single_skill,router_skill,skill_suite, orexisting_skill_upgrade_handoff. - Lock evidence scope: confirm which conversation turns, files, logs, artifacts, diffs, browser flows, or transcripts you may read.
- Lock output location before writing files.
- Reconstruct the workflow from authorized evidence: user goal, real steps, failures, fixes, success proofs, and approval gates.
- Mine local or open-source patterns only when they help package the workflow more reliably.
- Separate reusable invariants from local accidentals such as one-time paths, account names, one-day product quirks, or temporary user preferences.
- Abstract the workflow into state gates, validation gates, scripts, references, examples, and evals. Delete weak routes that depend on subjective guesses.
- Choose the smallest package that preserves correctness.
- Write the skill only after the previous gates are satisfied.
- Validate, report remaining assumptions, and hand the package back with paths and checks.
Do not jump directly from "I saw a successful run" to "I wrote a skill". The missing middle layer is where portability, privacy, and generalization are decided.
Architecture Choices
plan_only: the user wants a reviewed design or audit, not files.new_single_skill: one stable workflow or one tightly coupled workflow family.router_skill: one entry point that routes across several existing skills or phases.skill_suite: several independent workflows that should be released together but triggered separately.existing_skill_upgrade_handoff: the real task is to improve an existing skill. Produce a clean handoff for$run-history-skill-upgraderinstead of editing that skill here.
Prefer replacement, merging, and omission over package bloat.
Evidence And Scope
Allowed by default after intent is locked:
- current visible conversation;
- user-provided paths, artifacts, logs, screenshots, and transcripts;
- current workspace files, diffs, tests, and generated outputs;
- similar public skills or official docs read for packaging patterns.
Require explicit approval before reading:
- broad local session archives unrelated to the current task;
- browser cookies, local storage, session exports, or account caches;
- passwords, tokens, API keys, verification codes, MFA data, or other credentials;
- unrelated private folders or personal history outside the agreed scope.
Keep facts, inferences, and open assumptions separate. Never write secrets, hidden prompts, private account identifiers, or unrelated personal data into the released skill or its examples.
Design Rules
- Keep
SKILL.mdfocused on trigger boundary, role, workflow, safety gates, and reference navigation. - Put long branch-specific guidance in
references/. - Put deterministic and repeated checks in
scripts/. - Put trigger and regression samples in
evals/when the workflow is long-lived, high-risk, or easy to overfit. - Use examples only when they capture complex behavior, failure recovery, or boundary conditions. Every example must state the invariant and the non-goal.
- User-owned decisions stay user-owned. Machine-checkable facts move to scripts, tests, schema checks, diffs, file-existence checks, or validators.
- Do not create per-skill
README, installation scripts, changelogs, or decorative files unless the user or release target explicitly requires them. - Treat
agents/openai.yamlas an optional UI enhancement, not as the core logic.
Validation
Run the package validator bundled with this skill:
<python> <skill-dir>/scripts/validate_skill_package.py <target-skill-dir>
This bundled validator checks package structure, the portable Agent Skills frontmatter field set, referenced paths, JSON shape, Python syntax, and common private-path leaks. 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 the skill triggers correctly or improves behavior.
If the current host provides a canonical skill validator, run that too. On Codex-like hosts, this often means a quick_validate.py command from the platform's skill tooling.
Also run the smallest relevant technical checks:
python -m py_compilefor modified Python scripts;python -m json.toolfor edited JSON files;- trigger review with the smallest useful set that includes a should-trigger case, a nearby should-not-trigger case, and a boundary case; add more only when risk or instability warrants it;
- a leak scan for private absolute paths, credentials, hidden prompts, or environment-specific debris.
Do not claim completion if validation was skipped or failed. Report the gap and the remaining risk.
Final Response
Report:
- the chosen package type;
- the final skill path;
- files created or intentionally omitted;
- evidence sources actually used;
- validation commands actually run and their results;
- assumptions that still need user review;
- whether the result is
plan_only, a new skill package, or an upgrader handoff.
References
references/history-mining.mdreferences/open-source-pattern-mining.mdreferences/skill-design-protocol.mdreferences/self-repair-and-evals.mdreferences/examples.mdscripts/validate_skill_package.pyevals/evals.json
Related Skills
taste-skill
117.6kAgent skills that give coding agents taste: art direction, reference images and a browser check instead of generic AI pages
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.
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.
