investigation-memory

Capture and manage investigative insights and hunches in a case-specific directory.

2|Updated Jun 26, 2026
One-click install
npx skills add https://github.com/sxd007/investigation-ontology --skill investigation-memory
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: investigation-memory
Source: https://github.com/sxd007/investigation-ontology/tree/main/skills/investigation-memory
Command: npx skills add https://github.com/sxd007/investigation-ontology --skill investigation-memory

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill solves the problem of losing valuable investigative intuition, hunches, and temporary decision-making rationales that do not yet qualify as formal evidence but are critical for future case retrospectives.

Core Features & Use Cases

  • Non-Intrusive Capture: Records investigative branches, hunches, and observations in the background without interrupting the user's workflow or polluting the formal evidence chain.
  • Structured Indexing: Automatically maintains an index of all memory entries, allowing for easy retrieval and cross-referencing during case reviews.
  • Use Case: When an investigator feels a specific supplier payment pattern is suspicious but lacks sufficient data to prove it, they can use this skill to log the observation for future verification without prematurely flagging it as evidence.

Quick Start

Use the investigation-memory skill to record a new observation about the interviewee's body language during the recent session.

Frequently Asked Questions about investigation-memory

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I track investigation hunches without polluting the formal evidence chain?

To track investigation hunches without polluting formal evidence, use a dedicated case-specific directory to capture non-evidentiary insights. This ensures strict separation from formal evidence registries, maintaining investigation integrity while logging observations for future verification.

What is the best way to record non-evidentiary observations during an audit?

The best way to record non-evidentiary audit observations is using a searchable, low-noise repository that automatically maintains an index of memory entries. This allows structured indexing for easy retrieval and cross-referencing during case reviews without interrupting your workflow.

Can I use a retrospective memory tool to log suspicious patterns before having enough proof?

Yes, you can use a retrospective memory tool to log suspicious patterns before having enough proof. It captures investigative branches and observations in the background, allowing you to record temporary decision-making rationales that require future verification without prematurely flagging them as evidence.

Does investigation memory support cross-referencing insights during case management reviews?

Investigation memory supports cross-referencing insights during case management reviews by providing structured indexing. It automatically maintains an index of all memory entries, allowing easy retrieval of decision rationales and observations for case retrospectives.

When should I not use a non-evidentiary insight tracker for case management?

You should not use a non-evidentiary insight tracker for storing formal evidence or working papers. It is designed strictly for non-evidentiary investigative insights and hunches to ensure strict separation and maintain the integrity of the formal investigation process.

How does a searchable memory repository handle investigative intuition for future verification?

A searchable memory repository handles investigative intuition by capturing and managing hunches and decision rationales in a dedicated case-specific directory. It supports the investigation lifecycle by providing a low-noise repository for information requiring future reflection and verification.