Skill History
Show version evolution timeline for a specific skill.
Usage
bashnode ${CLAUDE_PLUGIN_ROOT}/scripts/history.mjs $ARGUMENTS
Display the output exactly as returned. Do not modify or summarize.
Show version timeline for a skill with metrics per version. Tracks SKILL.md changes over time with satisfaction rates and line count deltas.
| Publisher | haidang1810 |
| Repository | skill-evolver |
| Skill name | skill-history |
| Stars | 55 |
| Forks | 12 |
| Bundled files | Instructions only |
| Links |
A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.
AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.
Everything the model needs lives in the instructions — no extra files to sync.
Published by haidang1810 on GitHub. Read the source before you install it.
Install the Skill History AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.
TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.
https://github.com/haidang1810/skill-evolver/tree/master/plugins/skill-evolver/skills/skill-historyAny agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.
git clone --depth 1 https://github.com/haidang1810/skill-evolver.git /tmp/skill-evolver
mkdir -p .claude/skills
cp -r /tmp/skill-evolver/plugins/skill-evolver/skills/skill-history .claude/skills/skill-historyEnable Skill History in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.
AI skills are plain Markdown instructions rather than provider-specific code, so Skill History is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.
The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.
Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.
This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.
Show version evolution timeline for a specific skill.
bashnode ${CLAUDE_PLUGIN_ROOT}/scripts/history.mjs $ARGUMENTS
Display the output exactly as returned. Do not modify or summarize.
Show version timeline for a skill with metrics per version. Tracks SKILL.md changes over time with satisfaction rates and line count deltas.
Because you install it once and use it with any model. Skill History is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.
Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/haidang1810/skill-evolver/tree/master/plugins/skill-evolver/skills/skill-history. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.
Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.
As many as you like. As long as a model supports skills, you can use Skill History with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.
It is published on GitHub by haidang1810. Check the repository for licensing terms. You only pay your own AI provider for the tokens you use.
An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.
A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.
Pytorch Lightning
Clean training loops with built-in distributed support.
Troubleshoot
Investigate unexpected behavior in the current Copilot agent session by analyzing its event log. Use when the user asks why something happened, why a request was slow, why a tool was or was not used,…
Use this skill whenever the user wants to do anything with PDF files. This includes reading or extracting text/tables from PDFs, combining or merging multiple PDFs into one, splitting PDFs apart,…
Ui Styling
Create beautiful, accessible user interfaces with shadcn/ui components (built on Radix UI + Tailwind), Tailwind CSS utility-first styling, and canvas-based visual designs. Use when building user…
Get notified about new features and future giveaways by subscribing to our newsletter 👇
