S4h Historical logo

S4h Historical

Organization
human-avatar
s4h-historical

Entry point for the historical reasoning toolkit. Routes to the right historical skill based on your situation. Use when you say 'historical', 'has this happened before', 'what does history say', 'what cycle is this', 'what usually goes wrong', 'what's the lesson', or want historical reasoning applied without knowing which specific tool fits.

Overview

Publisherhuman-avatar
Repositoryskills-for-humanity
Skill names4h-historical
Stars
234
Forks
24
Bundled files
Instructions only
LicenseMIT
Links
  • 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 human-avatar on GitHub. Read the source before you install it.

Installation

Install the S4h Historical 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.
    https://github.com/human-avatar/skills-for-humanity/tree/main/skills/s4h-historical
  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/human-avatar/skills-for-humanity.git /tmp/skills-for-humanity
mkdir -p .claude/skills
cp -r /tmp/skills-for-humanity/skills/s4h-historical .claude/skills/s4h-historical
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

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

Historical

Applies historical reasoning to current situations. Diagnoses what kind of historical analysis is needed and applies the right tool.

Which tool fits

You need to...Tool
Identify what recurring cycle this is and where you are in itcycle-detection
Find recurring failure modes from similar past situationsfailure-analysis
Extract the transferable principle from a specific historical caselesson-extraction
Find genuinely similar historical situations to inform a decisionprecedent-analysis

Routing Decision

  • Situation feels like it has been seen before, want to know where in the pattern you are → cycle-detection
  • About to do something and want to know how it typically fails → failure-analysis
  • Have a specific historical case and want to know what it actually teaches → lesson-extraction
  • Making a decision and want to know what history says → precedent-analysis
  • Unclear → precedent-analysis; finding the analogous situation usually reveals cycles, lessons, and failure modes together

Framing check: Confirm the specific historical situation before routing. State what you've identified — the actual situation being examined, what time pressure or decision is attached, and the historical angle being sought — in one sentence, then use AskUserQuestion:

  • Question: "I'm reading this as: [your one-sentence framing of the situation and what historical lens fits]. Is that right?"
  • Header: "Framing"
  • Options:
    • Yes — proceed — framing is correct
    • Adjust — one element is off; user will correct it before you continue
    • Reframe — different situation than read; incorporate the correction before proceeding

Confirm Direction

After diagnosing which tool fits, use the AskUserQuestion tool to confirm direction. Construct the question dynamically to include your diagnosis:

  • Question: "My read: [diagnosed tool] — [one sentence on why it fits]. How would you like to proceed?"
  • Header: "Direction"
  • Options:
    • Yes, run that tool — Execute the diagnosed skill immediately using the context already provided
    • Show all options — List every skill in this category with one-line descriptions
    • Quick version — Run a lighter-weight alternative if one exists for this situation
    • Re-diagnose — Revisit the situation description for a different read

Proceed based on their selection.


Cycle Detection

Identifies what recurring cycle this is and where in it you currently are.

Most situations are instances of known cycles: hype cycles, market cycles, innovation S-curves, boom-bust patterns, political pendulum swings. Name the cycle candidates. Test each: does the current situation match the structural characteristics of that cycle? If so: what phase are you in (early, peak, correction, trough, recovery)? What does the cycle predict comes next?

Output: Cycle identification with evidence, current phase assessment, and what the cycle predicts comes next.


Failure Analysis

Extracts recurring failure modes from similar past situations.

Most failures have happened before in recognizable patterns. Identify 3-5 historical situations that are structurally similar to the current one. For each: what went wrong? Was the failure caused by overconfidence, resource depletion, misreading the environment, internal conflict, timing, or something else? Look for the failure mode that appears across multiple cases — that's the one most worth preparing for.

Output: Historical failure case inventory, recurring failure modes ranked by frequency and severity, and the specific early warning signs to watch for.


Lesson Extraction

Extracts the transferable principle from a specific historical case.

Historical cases carry both contingent details (specific to their time and place) and transferable principles (valid across contexts). The challenge is separating them. Take the case and ask: what actually caused the outcome — the surface events or the underlying dynamics? If you removed all the period-specific details, what structural principle remains? Test that principle against at least one other historical case.

Output: The contingent surface details set aside. The underlying structural principle. Cross-case validation. How the principle applies to the current situation.


Precedent Analysis

Finds and applies genuinely similar historical situations.

Distinguish true precedents from superficial analogies. A true precedent shares the underlying causal structure, not just surface similarity. Find 2-3 candidate precedents. For each: what makes it genuinely similar? What makes it different in ways that matter? What did decision-makers do, and what happened? What would they have done differently in hindsight?

Output: Precedent inventory with genuine vs. superficial similarity assessment, decision-outcome analysis for each, and the lessons that most directly apply.

Frequently asked questions

What does the S4h Historical AI skill do?

Entry point for the historical reasoning toolkit. Routes to the right historical skill based on your situation. Use when you say 'historical', 'has this happened before', 'what does history say', 'what cycle is this', 'what usually goes wrong', 'what's the lesson', or want historical reasoning applied without knowing which specific tool fits.

Why use S4h Historical on TypingMind?

Because you install it once and use it with any model. S4h Historical 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 S4h Historical in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/human-avatar/skills-for-humanity/tree/main/skills/s4h-historical. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use S4h Historical?

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 S4h Historical?

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

Is the S4h Historical AI skill free?

Yes. It is published on GitHub by human-avatar under the MIT 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.

View all

Set up your own AI workspace now

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