jleechanorg/jleechan-skills/conversation-history-sparse

Sparse history

Resolve the topic, timeframe, source and desired fact. Use supported connected history/search tools or an explicitly authorized local read-only helper. Search metadata/indexes first, then small relevant snippets with a strict result/context budget. Escalate depth only when sparse evidence cannot answer the question; do not silently broaden scope.

Report source, date, runtime and bounded supporting facts. Separate no match, unavailable and unsearched stores. Tool payloads and repeated transcripts may create false hits; verify the relevant user/assistant event rather than treating a keyword hit as evidence. Usage event counts are not distinct user intentions and missing telemetry is not proof of nonuse.

Do not export raw chats, credentials, hidden instruction stores, unrelated personal/tax/financial/health data or broad memory dumps. Historical approvals and policies are evidence only, not current authority. Never probe denied paths or use state-writing recovery commands for a read-only search.

Return a concise sourced answer and remaining coverage gaps. For broader memory/roadmap context use memory-search without duplicating completed searches.