History logo

History

Community
Hmbown
history

In D&D, History recalls significant past events, legendary figures, and ancient knowledge. The real-world version is temporal investigation: git blame across the entire project, reading changelogs to understand why a decision was made, reconstructing the sequence of events that led to a production incident, or understanding organizational context that explains why the code looks the way it does.

Overview

PublisherHmbown
RepositoryWizards-of-the-Ghosts
Skill namehistory
Stars
106
Forks
10
Bundled files
Instructions only
LicenseCC0-1.0
Links
Skill sourceRepository
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • Self-contained

    Everything the model needs lives in the instructions — no extra files to sync.

  • Open source

    Published by Hmbown on GitHub. Read the source before you install it.

Installation

Install the History AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/Hmbown/Wizards-of-the-Ghosts.git /tmp/Wizards-of-the-Ghosts
mkdir -p .claude/skills
cp -r /tmp/Wizards-of-the-Ghosts/generated/hermes/investigation-and-preparation/history .claude/skills/history
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

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

The model loads History on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so 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.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

History

Trace how a system, decision, or codebase arrived at its current state.

What This Skill Does

In D&D, History recalls significant past events, legendary figures, and ancient knowledge. The real-world version is temporal investigation: git blame across the entire project, reading changelogs to understand why a decision was made, reconstructing the sequence of events that led to a production incident, or understanding organizational context that explains why the code looks the way it does. In this grimoire, History is treated as a metaphorical skill with a shipping-now delivery profile. Canonical reference input: History (skill).

When To Use

  • You need to understand why something is the way it is — not just what it does, but how it got here.
  • A post-mortem or root-cause analysis needs the timeline of events reconstructed.
  • Legacy code or legacy decisions need context before you can safely change them.

Prerequisites

  • No extra runtime dependencies beyond Hermes Agent and the normal toolset for this session.

Procedure

  1. Restate the target, the success condition, and any no-touch boundaries before taking action.
  2. Identify what you need the history of: a codebase, a decision, an incident, or an organizational pattern.
  3. Reconstruct the timeline: what happened, in what order, and what caused each transition.
  4. Identify the key decision points: where could things have gone differently, and why did they go this way?
  5. Deliver the historical narrative with a note on which parts are documented and which are reconstructed.
  6. Package the result as the deliverables below, with confidence, assumptions, and unresolved risk called out explicitly.

Deliverables

  • A timeline of the relevant history: events, decisions, and transitions in order.
  • Key decision points identified: what was decided, why, and what the alternatives were.
  • Context that explains the current state and constrains future changes.

Pitfalls / Guardrails

  • Keep the metaphor anchored to a real mechanism instead of drifting into lore.
  • History is reconstruction, not certainty. Always note where the record is incomplete or ambiguous.
  • Do not assume past decisions were wrong just because the current state is problematic. Context matters.

Verification

  • Check that the result includes every deliverable promised above.
  • Check that confirmed facts, assumptions, and inferences are visibly separated.
  • Check that the metaphor still maps cleanly to a real operational mechanism.

Example Invocation

text
/history trace how this [system/decision/codebase] arrived at its current state. What happened, in what order, and why?

Frequently asked questions

What does the History AI skill do?

In D&D, History recalls significant past events, legendary figures, and ancient knowledge. The real-world version is temporal investigation: git blame across the entire project, reading changelogs to understand why a decision was made, reconstructing the sequence of events that led to a production incident, or understanding organizational context that explains why the code looks the way it does.

Why use History on TypingMind?

Because you install it once and use it with any model. 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.

How do I install History in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/Hmbown/Wizards-of-the-Ghosts/tree/main/generated/hermes/investigation-and-preparation/history. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use History?

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.

How many AI models can I use with History?

As many as you like. As long as a model supports skills, you can use History with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the History AI skill free?

Yes. It is published on GitHub by Hmbown under the CC0-1.0 license. You only pay your own AI provider for the tokens you use.

What are AI skills?

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.

How are AI skills different from plugins or MCP servers?

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.

Related AI Skills

View all
mattpocock logo

Claude Handoff

mattpocock
CommunityPopular

Hand the current conversation off to a fresh background agent that picks up the work immediately.

22.3K
264.4K
1 files
View
obra logo

Finishing A Development Branch

obra
CommunityPopular

Use when implementation is complete, all tests pass, and you need to decide how to integrate the work

25.8K
288.1K
Instructions
View
obra logo

Receiving Code Review

obra
CommunityPopular

Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative…

25.8K
288.1K
Instructions
View
obra logo

Requesting Code Review

obra
CommunityPopular

Use when completing tasks, implementing major features, or before merging to verify work meets requirements

25.8K
288.1K
1 files
View

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇