History Explorer logo

History Explorer

OrganizationPopular
TokenRhythm
history-explorer

Query the per-turn DecisionEntry log for skill co-occurrence patterns, meta-skill usage stats, and the router fixture corpus. Returns a JSON summary suitable for downstream LLM consumption. Used by meta-skill-creator's harvest step but also useful standalone for 'which skills did I use most this week?'

Overview

PublisherTokenRhythm
Repositoryopensquilla
Skill namehistory-explorer
Stars
7K
Forks
566
Bundled files
1
LicenseApache-2.0
Links
Skill sourceRepositoryHomepage
  • 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.

  • 1 bundled files

    Scripts, templates, and references the model can read while it works. Files are read-only and never executed.

  • Open source

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

Installation

Install the History Explorer 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/TokenRhythm/opensquilla.git /tmp/opensquilla
mkdir -p .claude/skills
cp -r /tmp/opensquilla/src/opensquilla/skills/bundled/history-explorer .claude/skills/history-explorer
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable History Explorer 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 Explorer 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 Explorer 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 Explorer

Lightweight read-only view over ~/.opensquilla/logs/decisions-*.jsonl. Aggregates DecisionEntry.skills_invoked (SCHEMA_VERSION 10) into co-occurrence frequencies, joins with SkillLoader.list_meta_specs() for meta-skill usage stats, and surfaces the tests/test_skills/router_fixtures/ corpus.

Usage

uv run python {baseDir}/scripts/explore.py \
  --log-dir ~/.opensquilla/logs \
  --query "Co-occurring chains for PDF workflows" \
  --window-days 30 \
  --include co_occurrences,meta_usage,router_fixtures \
  --top-k 10

Output

JSON to stdout with keys co_occurrences, meta_usage, router_fixtures, and a placeholder string when the log is empty.

Fallback

If no decision-log exists, return an empty result with a placeholder string explaining "no history; downstream should rely on user intent only".

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the History Explorer AI skill do?

Query the per-turn DecisionEntry log for skill co-occurrence patterns, meta-skill usage stats, and the router fixture corpus. Returns a JSON summary suitable for downstream LLM consumption. Used by meta-skill-creator's harvest step but also useful standalone for 'which skills did I use most this week?'

Why use History Explorer on TypingMind?

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

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/TokenRhythm/opensquilla/tree/main/src/opensquilla/skills/bundled/history-explorer. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use History Explorer?

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 Explorer?

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

Is the History Explorer AI skill free?

Yes. It is published on GitHub by TokenRhythm under the Apache-2.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
multica-ai logo

Multica Onboarding

multica-ai
OrganizationPopular

Use when a product-authored kickoff starts or resumes Mika's interactive onboarding for a Multica workspace. The opening greeting has already been sent; carry the member from their first message to…

6.5K
50.4K
Instructions
View
HKUDS logo

Cli Anything Qgis

HKUDS
OrganizationPopular

Stateful QGIS CLI for projects, writable layers, features, layouts, exports, and qgis_process operations using the real QGIS runtime.

4.6K
49.5K
Instructions
View
HKUDS logo

Cli Anything Audacity

HKUDS
OrganizationPopular

Command-line interface for Audacity - A stateful command-line interface for audio editing, following the same patterns as the GIMP and Ble...

4.6K
49.5K
Instructions
View
obra logo

Subagent Driven Development

obra
CommunityPopular

Use when executing implementation plans with independent tasks in the current session

25.8K
288.1K
6 files
View

Set up your own AI workspace now

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