SkillAnything Skill Generator
AgentSkillOS/SkillAnything
Generates a complete agent skill for a target tool, API, library or workflow through a seven-phase pipeline that ends with testing, tuning and packaging for several platforms.
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 Run History Skill Builder
$ npx skills add dongshuyan/compass-skills --skill run-history-skill-builder -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install dongshuyan/compass-skills run-history-skill-builder --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/dongshuyan/compass-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/run-history-skill-builder .claude/skills/run-history-skill-builder && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "run-history-skill-builder" agent skill from https://github.com/dongshuyan/compass-skills/tree/master/skills/run-history-skill-builder into .claude/skills/run-history-skill-builder/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "run-history-skill-builder", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/dongshuyan/compass-skills/tree/master/skills/run-history-skill-builderType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add dongshuyan/compass-skills --skill run-history-skill-builder -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install dongshuyan/compass-skills run-history-skill-builder --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/dongshuyan/compass-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/run-history-skill-builder .agents/skills/run-history-skill-builder && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "run-history-skill-builder" agent skill from https://github.com/dongshuyan/compass-skills/tree/master/skills/run-history-skill-builder into .agents/skills/run-history-skill-builder/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "run-history-skill-builder", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add dongshuyan/compass-skills --skill run-history-skill-builder -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install dongshuyan/compass-skills run-history-skill-builder --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/dongshuyan/compass-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/run-history-skill-builder .cursor/skills/run-history-skill-builder && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "run-history-skill-builder" agent skill from https://github.com/dongshuyan/compass-skills/tree/master/skills/run-history-skill-builder into .cursor/skills/run-history-skill-builder/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "run-history-skill-builder", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/dongshuyan/compass-skills.git --path skills/run-history-skill-builder--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add dongshuyan/compass-skills --skill run-history-skill-builder -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install dongshuyan/compass-skills run-history-skill-builder --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/dongshuyan/compass-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/run-history-skill-builder .gemini/skills/run-history-skill-builder && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "run-history-skill-builder" agent skill from https://github.com/dongshuyan/compass-skills/tree/master/skills/run-history-skill-builder into .gemini/skills/run-history-skill-builder/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "run-history-skill-builder", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install dongshuyan/compass-skills run-history-skill-builderInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add dongshuyan/compass-skills --skill run-history-skill-builder -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/dongshuyan/compass-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/run-history-skill-builder .github/skills/run-history-skill-builder && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "run-history-skill-builder" agent skill from https://github.com/dongshuyan/compass-skills/tree/master/skills/run-history-skill-builder into .github/skills/run-history-skill-builder/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "run-history-skill-builder", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add dongshuyan/compass-skills --skill run-history-skill-builder -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install dongshuyan/compass-skills run-history-skill-builder --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/dongshuyan/compass-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/run-history-skill-builder .opencode/skills/run-history-skill-builder && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "run-history-skill-builder" agent skill from https://github.com/dongshuyan/compass-skills/tree/master/skills/run-history-skill-builder into .opencode/skills/run-history-skill-builder/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "run-history-skill-builder", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
run-history-skill-builder- GitHub stars
- 753
- Token cost
- ~1.8k tokens
- SKILL.md length
- 906 words
- Files
- 10 (incl. scripts, references)
- Skills in repo
- 9
- Repo updated
- First seen
- Licence
- MIT
At a glance
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.
- Works in 10 steps: Lock intent: decide whether the request… → Lock evidence scope: confirm which… → Lock output location before writing files. → …
- The user asks to make a new skill from real run history
- SKILL.md covers Language Policy, Role, Portability and Workflow, plus 6 more sections
- Runs Python scripts from its folder; calls python
What it does
Run History Skill Builder is an agent skill from dongshuyan/compass-skills. 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.
Its SKILL.md is about 1.8k tokens, which your agent loads only when the skill is triggered. The skill folder holds 13 other files, including scripts and reference files (for example `agents/openai.yaml`, `evals/evals.json` and `references/examples.md`).
It sits in Agent Workflows, covering Skill authoring and CI/CD. It works with Python. The repository describes itself as: 司南：个性化 AI 任务总控 Skills 系统 /COMPASS: Personal Alignment Skills OS for AI Agents. The licence is MIT.
When your agent uses it
- 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
- Produce a plan before writing files
Example prompts
- “/run-history-skill-builder”
Requirements
- Python 3
Workflow steps
10 steps, taken from the first numbered list in SKILL.md.
- Lock intent: decide whether the request is plan_only, new_single_skill, router_skill, skill_suite, or existing_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…
- Abstract the workflow into state gates, validation gates, scripts, references, examples, and evals. Delete weak routes that depend on…
- 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.
What it can do on your machine
Read from SKILL.md and the folder at commit 1b2e556. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Ships 2 files in scripts/ (Python), which the agent can run.
Shell commands in SKILL.md call:
python
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Run History Skill Builder loads about 1.8k tokens when it runs, and up to ~5.2k if it reads all its reference files. Until then it costs about 122 tokens; SKILL.md has 906 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.
SKILL.md
The full file from dongshuyan/compass-skills at commit 1b2e556, republished under its MIT licence (© dongshuyan). 906 words, ~1,843 tokens.
Download SKILL.mdSave it as
.claude/skills/run-history-skill-builder/SKILL.md (or your agent's skills folder). This skill also uses 9 other files; get the full folder from GitHub.- name
- 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.
Show full SKILL.md (367 more words)Show less
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
© dongshuyan, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 9 other files (scripts, references) in skills/run-history-skill-builder of dongshuyan/compass-skills.
- SKILL.md
- agents/openai.yaml
- evals/evals.json
- references/examples.md
- references/history-mining.md
- references/open-source-pattern-mining.md
- references/self-repair-and-evals.md
- references/skill-design-protocol.md
- scripts/test_validate_skill_package.py
- scripts/validate_skill_package.py
Open the folder on GitHubat commit 1b2e556
Compare with similar skills
Run History Skill Builder next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Run History Skill Builder this skilldongshuyan/compass-skills | 753 | — | ~1.8k | Automated safety check: Pass | MIT | |
| SkillAnything Skill GeneratorAgentSkillOS/SkillAnything | 471 | — | ~1.9k | Automated safety check: Pass | MIT | |
| DBS Skill Makerdontbesilent2025/dbskill | 11k | — | ~1.2k | Automated safety check: Pass | Custom licence | |
| Skill Creatorluongnv89/asm | 955 | — | ~5.3k | Automated safety check: Pass | MIT | |
| Skill Contract Reviewerrohitg00/ai-engineering-from-scratch | 67k | 1 repos | ~450 | Automated safety check: Pass | MIT | |
| Skill CreatorTheSyart/emperor-agent | 195 | — | ~2k | Automated safety check: Pass | MIT |
Similar skills
DBS Skill Maker
dontbesilent2025/dbskill
Turns a problem you keep running into into a single installable, tested skill, and prepares a GitHub repository only when you ask to share it.
Skill Creator
luongnv89/asm
Create a skill or bring an existing one up to the same standard (validate + asm eval fix loop); run evals, tune triggering.
Skill Contract Reviewer
rohitg00/ai-engineering-from-scratch
Validates an Agent Skill package against a portable contract with a Python checker, then picks the smallest set of instruction, capability or lifecycle primitives for the task.
Skill Creator
TheSyart/emperor-agent
Create, update, import, or validate Emperor Skills (SKILL.md folders with optional scripts, references, and assets).
Skill Creator
xuzhougeng/wisp-science
Create, update, validate, and evaluate Wisp skills. An agent skill from xuzhougeng/wisp-science.
More from dongshuyan/compass-skills
All 9 skills in this repoTask Forest
dongshuyan/compass-skills
Maintains a repo-local task forest or task DAG for the current workspace.
Run History Skill Upgrader
dongshuyan/compass-skills
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.
Session Handoff Prompt
dongshuyan/compass-skills
Create a concise continuation prompt that a fresh agent session can paste in to resume a long or degraded session.
User Profile Keeper
dongshuyan/compass-skills
Local user-profile maintenance skill for Codex, Claude Code, OpenClaw, OpenCode, and other agent harnesses.
Assess Interview Candidate
dongshuyan/compass-skills
根据候选人简历与岗位要求生成可审计的后台评估、简明的候选人介绍、按岗位重要性排列的简历疑点、12–18 道可直接照读的面试题，以及支持重点标记和本机保存的离线 HTML。用于招聘方准备结构化面试、核验岗位能力和记录回答。不要用于求职者模拟面试、私人背景调查、心理或人格诊断、从敏感属性推断表现，或自动录用、淘汰、排序候选人。
Academic Humanizer
dongshuyan/compass-skills
Draft, audit, or minimally revise English- or Chinese-language academic prose to reduce formulaic, vacuous, mechanically repetitive, or process-leaking language while preserving claims, evidence…
Related
Works with
Categories
Questions about Run History Skill Builder
What does Run History Skill Builder do?
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. Run History Skill Builder is an agent skill from dongshuyan/compass-skills. 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.
When should I use Run History Skill Builder?
Run History Skill Builder fits situations like: 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; produce a plan before writing files.
How do I install Run History Skill Builder in Claude Code?
Run `npx skills add dongshuyan/compass-skills --skill run-history-skill-builder -a claude-code`. Or copy the skill folder (skills/run-history-skill-builder in dongshuyan/compass-skills) into .claude/skills/run-history-skill-builder in your project. Claude Code loads it when a task matches its description.
How do I install Run History Skill Builder in Codex?
Run `npx skills add dongshuyan/compass-skills --skill run-history-skill-builder -a codex`. Or copy the skill folder (skills/run-history-skill-builder in dongshuyan/compass-skills) into .agents/skills/run-history-skill-builder in your project. Codex loads it when a task matches its description.
Can I use Run History Skill Builder in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add dongshuyan/compass-skills --skill run-history-skill-builder -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/run-history-skill-builder, .gemini/skills/run-history-skill-builder, .github/skills/run-history-skill-builder and .opencode/skills/run-history-skill-builder in your project.
What does Run History Skill Builder need to run?
Going by SKILL.md and its folder, Run History Skill Builder needs Python for the scripts in its folder and the command-line tools its instructions call (python). Our summary lists: Python 3.
Does Run History Skill Builder access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Run History Skill Builder safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.
What licence does Run History Skill Builder use?
Run History Skill Builder is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Run History Skill Builder use?
About 1.8k tokens (SKILL.md is roughly 7.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 3.3k tokens, read only when the agent opens those files.
What are the alternatives to Run History Skill Builder?
Skills that share tags, products or a category with Run History Skill Builder: SkillAnything Skill Generator (AgentSkillOS/SkillAnything, 471 stars), DBS Skill Maker (dontbesilent2025/dbskill, 11k stars), Skill Creator (luongnv89/asm, 955 stars) and Skill Contract Reviewer (rohitg00/ai-engineering-from-scratch, 67k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Run History Skill Builder?
dongshuyan (a GitHub user) maintains it in dongshuyan/compass-skills, which has 753 GitHub stars. The repository holds 9 skills in this directory. The repository was last updated on August 26, 2026.
Source: dongshuyan/compass-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.