History Hygiene

CommunityPopular

bradygaster

history-hygiene

Record reconciled final outcomes to history.md, not intermediate requests or obsolete claims

Overview

Publisher	bradygaster
Repository	`squad`
Skill name	`history-hygiene`
Stars	3.3K
Forks	506
Bundled files	Instructions only
License	MIT
Links	Skill source Repository Homepage

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 bradygaster on GitHub. Read the source before you install it.

Installation

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

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.

Open the app and go to Plugins → Skills.
Choose "Install from GitHub".
Paste the skill folder URL below and confirm.
https://github.com/bradygaster/squad/tree/dev/packages/squad-cli/templates/skills/history-hygiene
Enable the skill in any chat where you want it available.

Store

Installed

Skills

Add skills

Import one or more skills from a public GitHub folder or a local .skill or .zip archive, or SKILL.md file.

From GitHub URLFrom .skill, .zip, or SKILL.md

GitHub repo or folder

https://github.com/bradygaster/squad/tree/dev/packages/squad-cli/templates/skills/history-hygiene

Points to a single skill folder, or any folder that contains multiple skills. Public repos only.

CancelContinue

Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.

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/bradygaster/squad.git /tmp/squad
mkdir -p .claude/skills
cp -r /tmp/squad/packages/squad-cli/templates/skills/history-hygiene .claude/skills/history-hygiene

Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

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

Context

History files are cold-start context, not the source of truth for live behavior. Stale or incorrect entries poison decision-making downstream. A stale-history incident proved that an old history claim can cause future spawns to repeat a reversed decision. Reconcile an operational claim with current implementation, workflows, tests, documentation, skills, and applicable decisions before acting on it.

Scope

Activate when recording, correcting, or promoting finalized operational history.
Allowed targets: the explicitly selected history file and a focused reusable skill when the rule applies beyond one role.
Exclusions: intermediate requests, stale assignments, roster metadata, and unrelated cleanup.

Patterns

Record the final outcome, not the initial request.
Wait for confirmation before writing to history — don't log intermediate states.
If a decision reverses, update the entry immediately — don't leave stale data.
Link authority for operational facts. Name the current source or workflow when a lesson depends on live behavior.
Promote reusable rules. Move procedures and incident lessons that future roles need into a focused skill; history should retain only the evidence and outcome.
Record shipped guidance changes. A change to a shipped skill or template requires a changeset/changelog entry, unless the repository's documented skip label or equivalent release exception is present.

Examples

✓ Correct:

"Migration target: v0.8.17 (initial target was later corrected before execution)"
"Node runtime: follow the current package.json engines.node requirement"

✗ Incorrect:

"Migration target: v0.6.0" (when that request was later reversed)
Recording what was requested instead of what actually happened
Logging entries before outcome is confirmed

Stop conditions

Stop if the outcome is not confirmed or current authority disagrees with the proposed entry.
Stop if the target history file or promoted skill is outside the explicit scope.
Stop if a shipped skill/template change has no changeset or documented release exception.

Anti-Patterns

Writing intermediate or "for now" states to disk
Attributing decisions without confirming final direction
Treating history as authoritative over live source or workflow behavior
Copying dated assignments, status reports, or retired workarounds into a reusable skill

Frequently asked questions

What does the History Hygiene AI skill do?

Record reconciled final outcomes to history.md, not intermediate requests or obsolete claims

Why use History Hygiene on TypingMind?

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

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/bradygaster/squad/tree/dev/packages/squad-cli/templates/skills/history-hygiene. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use History Hygiene?

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

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

Is the History Hygiene AI skill free?

Yes. It is published on GitHub by bradygaster 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

Claude Opus 4 5 Migration

anthropics

OrganizationPopular

Migrate prompts and code from Claude Sonnet 4.0, Sonnet 4.5, or Opus 4.1 to Opus 4.5. Use when the user wants to update their codebase, prompts, or API calls to use Opus 4.5. Handles model string…

Deploy Release Test

Validate a commit-specific Next.js preview package and manually trigger the entire Next.js deployment test suite through the test_e2e_deploy_release.yml GitHub Actions workflow. Use only when asked to…

Insight Error Page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new `errors/<slug>.mdx` page, auditing an existing one, or checking that a page matches the framework fix…

Mcp Apps Builder

**MANDATORY for ALL MCP server work** - mcp-use framework best practices and patterns. **READ THIS FIRST** before any MCP server work, including: - Creating new MCP servers - Modifying existing MCP…

Overview

Installation

Install in TypingMind

Install in another agent

Use it in TypingMind

Works with any AI model

Skill instructions

Context

Scope

Patterns

Examples

Stop conditions

Anti-Patterns

Frequently asked questions

Related AI Skills

Set up your own AI workspace now