history-hygiene Skill
Record final outcomes to history.md, not intermediate requests or reversed decisions Published by microsoft in aitour26-BRK445-building-enterprise-ready-ai-agents-with-microsoft-foundry.
What is history-hygiene Skill?
Record final outcomes to history.md, not intermediate requests or reversed decisions Published by microsoft in aitour26-BRK445-building-enterprise-ready-ai-agents-with-microsoft-foundry. This profile combines repository metadata with install, compatibility, and usage signals so developers can quickly decide whether it fits their agent workflow before opening the source repository.
Automated repository signals based on public metadata such as recency, license, installation evidence, and adoption. These are not a security audit or endorsement.
Key capabilities
- Includes SKILL.md support
- Reusable instructions support
- Data analysis
- Writing
- Data analysis use cases
- Writing use cases
Technical details
- Install or run with Copy skill directory
When to use history-hygiene Skill
- Use it for data analysis.
- Use it for writing.
Built with
Editorial notes
Source
- Creator: microsoft
- Repository: microsoft/aitour26-BRK445-building-enterprise-ready-ai-agents-with-microsoft-foundry
- Skill file: .squad/templates/skills/history-hygiene/SKILL.md
What it does
Record final outcomes to history.md, not intermediate requests or reversed decisions
Skill instructions
Context History files (.md files tracking decisions, spawns, outcomes) are read cold by future agents. Stale or incorrect entries poison decision-making downstream. The Kobayashi incident proved this: history said "Brady decided v0.6.0" when Brady had reversed that to v0.8.17. Future spawns read the wrong truth and repeated the mistake. 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. - One read = one truth. A future agent should never need to cross-reference other files to understand what actually happened. Examples ✓ Correct: - "Migration target: v0.8.17 (initially discussed as v0.6.0, corrected by Brady)" - "Reverted to Node 18 per Brady's explicit request on 2024-01-15" ✗ Incorrect: - "Brady directed v0.6.0" (when later reversed) - Recording what was requested instead of what actually happened - Logging entr
Explore related resources
Frequently asked questions
What is history-hygiene?
history-hygiene is a open-source AI agent skill with Copy skill directory. Record final outcomes to history.md, not intermediate requests or reversed decisions
Who is history-hygiene best for?
history-hygiene is best for reusing agent instructions, scripts, and references, data analysis workflows, writing workflows.
How do I install history-hygiene?
Install or run history-hygiene using Copy skill directory. Check history-hygiene for the latest setup command.
Is history-hygiene actively maintained?
history-hygiene may need a closer maintenance check before production use.
Auto-fetched from GitHub.
