# Run History Skill Builder

Turn a completed task, browser flow, artifact pipeline, failure-recovery trace, or...

- Repository: https://github.com/dongshuyan/compass-skills (764 stars)
- Category: Design
- License: MIT
- Last updated: 2026-10-30
- Runs scripts: yes, review before use

## Install

Claude Code: `npx skills add dongshuyan/compass-skills --skill run-history-skill-builder -g -a claude-code -y`
Codex: `npx skills add dongshuyan/compass-skills --skill run-history-skill-builder -g -a codex -y`
Cursor: `npx skills add dongshuyan/compass-skills --skill run-history-skill-builder -g -a cursor -y`
Gemini CLI: `npx skills add dongshuyan/compass-skills --skill run-history-skill-builder -g -a gemini-cli -y`

## 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.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# 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

The rest: https://github.com/dongshuyan/compass-skills/blob/HEAD/skills/run-history-skill-builder/SKILL.md