
from wizards-of-the-ghosts91
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.
History is a purely instructional skill for temporal investigation — reconstructing how a system or codebase arrived at its current state. No scripts are bundled; it's effectively a structured prompt template with D&D-themed framing. The procedure steps and deliverables are clear but lack concrete tooling or output schemas. Guardrails are present but the metaphor risks misalignment if an agent treats lore as operational guidance.
Clean from a security perspective — no scripts, no network calls, no credentials. Limited practical value as it adds little beyond what a well-prompted agent would already do. The D&D theming is a niche framing that may not resonate with most users.
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.
Hypnotic Pattern
Design short-lived attention-capture patterns (progress indicators, micro-rewards, visual anchors) to hold focus during bounded flows without creating addictive
Fear (Pre-mortem & Risk Amplifier)
Structured pre-mortem generator that amplifies plausible worst-case scenarios, ranks failure modes, and produces concrete mitigation recommendations.
Greater Invisibility
Plan and execute live changes with minimal user-visible noise using feature flags, shadow writes, progressive rollout, and operator-visible signals.
Power Word Kill
Emergency containment skill: guidance and guarded procedure for immediate hard termination of processes, services, or accounts when graceful options are unavail
Disguise Self
Adapt voice, tone, and presentation of existing content for a target audience without changing facts or meaning.
Locate Animals or Plants
Discover live services, background jobs, data stores, and hidden dependencies in an environment and return a prioritized map with confidence notes.