More screenshots

    Works with the AI tools you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+22 more

    Causal Timeline Sleuth

    1

    Reconstruct causal chains, decision timelines, and counterfactual histories from months or years of organizational events.

    $15

    Secure checkout via Stripe

    30-day refund guarantee

    Converts to your local currency at checkout

    Security scanned
    Causal Timeline Sleuth

    Causal Timeline Sleuth

    Example session with this skill installed

    What decisions led us to adopt OAuth2 for authentication?

    • Read your context and instructions
    • Compiled the causal timeline sleuth
    • Generated the document

    Causal Chain: OAuth2 Adoption (auth-service)

    Critical Path

    1. 2025-03-14 — Credential breach via legacy token endpoint

      • Actors: Security team, Platform lead
      • Rationale: Legacy tokens had no expiry or rotation
      • Evidence: INC-2847 postmortem, security review ticket
      • Confidence: high

    2. 2025-03-21 — Security review mandates token endpoint deprecation within 90 days

      • Actors: CISO, Platform lead
      • Caused by: 2025-03-14 breach
      • Rationale: Compliance + customer trust requirements
      • Evidence: SEC-Review-031
      • Confidence: high

    3. 2025-05-08 — OAuth2 selected over SAML after vendor evaluation

      • Actors: Platform eng, Security, External consultant
      • Caused by: 2025-03-21 mandate
      • Rationale: Better library support, existing API gateway already spoke OAuth2, lower migration cost than SAML
      • Evidence: ADR-042, evaluation matrix
      • Confidence: high

    4. 2025-06-01 — OAuth2 migration completed, legacy endpoint retired

      • Actors: Auth team
      • Caused by: 2025-05-08 decision
      • Evidence: PR #1842, release notes v2.14
      • Confidence: high

    Key Branch Points

    SAML vs OAuth2 (May 2025): SAML stronger on enterprise SSO features but required heavier gateway changes. OAuth2 won on implementation velocity and existing library maturity.

    Why This Path Was Taken

    The breach created non-negotiable timeline pressure. Once the 90-day clock started, the team optimized for the solution that could ship inside the window with the least new infrastructure.

    Gaps & Confidence Notes

    • Exact cost comparison numbers from the May evaluation are not in the current ADR.
    • No formal record of the rejected “stay on sessions + add rotation” proposal beyond a single Slack thread.

    Sources used: ADR-042, INC-2847, SEC-Review-031, git history of auth-service.

    causal-timeline-sleuth.pdf

    PDF · document

    Generated

    Example file from a real run - the skill writes it into your workspace.

    Connects securely to your tools. The creator never sees your data.

    What you get

    Trace the sequence of decisions leading to current technical debt.Generate post-incident causal chains for engineering retrospectives.Model counterfactual scenarios for past strategic pivots.Audit the rationale behind legacy architecture choices using ADRs.incident-analysisadrdecision-history

    About this skill

    AI agents fail on temporal-causal questions — not because they lack intelligence, but because they receive the wrong kind of context.

    This skill gives your agent the exact architecture patterns, event-graph schema, and query-routing logic needed to answer:

    • What decisions led to X?
    • How did this situation evolve?
    • Why does this system state exist?
    • What if we had chosen differently?

    What you get

    • Clear classification of Sequence / Causal / Counterfactual queries
    • A practical Event Graph schema (timestamp, actors, caused_by, confidence, sources)
    • Rules for extracting only the causal path from noisy history (ADRs, incidents, git, tickets, meetings)
    • Windowed context synthesis so critical intermediate decisions survive context compression
    • Structured output formats that are scannable in under 30 seconds
    • Explicit confidence scoring and gap reporting — no invented rationales

    Ideal for

    • Post-incident analysis and root-cause reconstruction
    • Architecture Decision Record (ADR) querying across months
    • Product retrospectives and strategy evolution
    • Compliance / audit “why does this policy exist?” questions
    • Organizational memory and institutional knowledge agents

    Works with any agent that supports the open SKILL.md standard (Claude Code, Cursor, Codex, Copilot, Gemini CLI, Grok, and 15+ more).

    How to install

    Works the same in every agent - Claude, Cursor, Codex, Copilot and 20+ more.

    ~30 seconds
    1. 1

      Download the ZIP

      Free skills download straight away. Paid skills unlock right after purchase.

    2. 2

      Unzip into your skills folder

      Every agent reads skills from one folder on your machine. Drop the unzipped folder in there.

    3. 3

      Ask your agent to use it

      Restart the agent if it was already running. It picks the skill up automatically - no config needed.

    Skills folder by agent

    Click the path to copy it. Create the folder if it does not exist yet.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill passes our trust checks below.

    Security scanned

    Passed our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    30-day refund

    Not a fit? Get your money back

    Trust & safety

    Security scanned

    Verified clean 25 days ago

    • Passed all security checks, Safe to install

    Listed25 days ago

    What's inside

    Frequently Asked Questions