from wizards-of-the-ghosts67
Performs structured reconstruction of how a system, decision, or codebase arrived at its current state: timelines, key decision points, and contextual analysis
History is a procedural investigative skill that helps an agent reconstruct timelines and explain why a system, decision, or codebase looks the way it does. It formalises steps for gathering evidence, sequencing events, identifying key decision points, and producing a clear narrative with confidence levels and unresolved uncertainties.
Use during post-mortems, root-cause analyses, onboarding into legacy projects, or before making invasive refactors where historical context and prior trade-offs matter. Also useful when translating organizational or product decisions into engineering constraints.
has_scripts=false).Designed for Hermes-style or general-purpose assistants that can access git history, changelogs, and repo metadata. Works best when the agent has tools for git blame, commit inspection, and reading project docs.
This skill has not been reviewed by our automated audit pipeline yet.
Symbol — Policy Tagging / Semantic Marker
Define and apply named policy 'symbols' (machine-readable tags) that trigger enforcement actions like audit logging, throttling or compliance gates when conditi
Arcana (Technical Mechanism Analysis)
Explain how systems, protocols, or architectures actually work under the hood and surface non-obvious implications and failure modes.
