How do I install the Ivx Cf Hindsight Memory skill?

Run npx skillmds@latest add intelli-verse-x/ivx-cf-hindsight-memory in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Ivx Cf Hindsight Memory safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Ivx Cf Hindsight Memory?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Ivx Cf Hindsight Memory free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Ivx Cf Hindsight Memory?

intelli-verse-x (@intelli-verse-x) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Ivx Cf Hindsight Memory by intelli-verse-x

Name: Ivx Cf Hindsight Memory
Rating: 4.666666666666667 (3 reviews)
Author: intelli-verse-x

Ivx Cf Hindsight Memory

Shared IntelliVerse-X long-term memory via Hindsight MCP. Recall before deep repo exploration; sync_retain after non-obvious fixes, decisions, and process rules. Use for content-factory, kube-infra, QuizVerse, Nakama. Triggers: hindsight, team memory, retain, recall, root cause, gotcha, continuous memory save, "we've hit this before".

intelli-verse-x Updated Sep 8, 2026 0 repo stars

File contents

Hindsight Memory (Content Factory)

Shared team brain. MCP server: hindsight (or user-hindsight).

Quick Start

Before non-trivial work (silent — fold results in, don't announce tools):

recall(query="<plain-language restatement of the task/problem>")

After resolving something durable:

sync_retain(
  content="<self-contained fact: what / why / when>",
  context="content-factory <area>",
  tags=["project:content-factory"]
)

Use retain only for fire-and-forget; prefer sync_retain.

Project Tags

Tag	When
`project:content-factory`	CF pipelines, MCP, LiteLLM, prompts, accounts
`project:kube-infra`	EKS, aicart, Helm, deployments
`project:quizverse-unity`	QuizVerse Unity
`project:quizverse-frontend`	QuizVerse web
`project:backend-ai`	NestJS / AI API
`project:nakama`	Nakama

Omit tags only for true org-wide facts.

What to Retain

Root causes (especially non-obvious)
Gotchas / footguns
Architecture or process decisions + rationale
Workarounds for flaky providers
New CF conventions (prompt registry, LiteLLM, character_identity, task store)

Never retain: secrets, credentials, tokens, raw logs with PII, chat noise.

Continuous Save Cadence

Start — recall before exploring from scratch
Dedupe — recall the candidate fact; if present, update_memory instead of duplicate retain
Milestone / end — sync_retain one distilled outcome per resolved issue

Other Tools

Tool	When
`reflect(query=...)`	Synthesized judgment across memories
`list_memories(q=...)`	Browse/audit
`update_memory` / `invalidate_memory`	Correct or retire stale facts

Failure Mode

If Hindsight MCP is disconnected or auth fails: note once, continue the task. Memory is an accelerator, not a blocker. Do not retry auth in a loop.

---name: ivx-cf-hindsight-memorydescription: Shared IntelliVerse-X long-term memory via Hindsight MCP. Recall before deep repo exploration; sync_retain after non-obvious fixes, decisions, and process rules. Use for content-factory, kube-infra, QuizVerse, Nakama. Triggers: hindsight, team memory, retain, recall, root cause, gotcha, continuous memory save, "we've hit this before".---# Hindsight Memory (Content Factory)Shared team brain. MCP server: `hindsight` (or `user-hindsight`).## Quick Start**Before non-trivial work** (silent — fold results in, don't announce tools):```recall(query="<plain-language restatement of the task/problem>")```**After resolving something durable:**```sync_retain( content="<self-contained fact: what / why / when>", context="content-factory <area>", tags=["project:content-factory"])```Use `retain` only for fire-and-forget; prefer `sync_retain`.## Project Tags| Tag | When ||-----|------|| `project:content-factory` | CF pipelines, MCP, LiteLLM, prompts, accounts || `project:kube-infra` | EKS, aicart, Helm, deployments || `project:quizverse-unity` | QuizVerse Unity || `project:quizverse-frontend` | QuizVerse web || `project:backend-ai` | NestJS / AI API || `project:nakama` | Nakama |Omit tags only for true org-wide facts.## What to Retain- Root causes (especially non-obvious)- Gotchas / footguns- Architecture or process decisions + rationale- Workarounds for flaky providers- New CF conventions (prompt registry, LiteLLM, character_identity, task store)**Never retain:** secrets, credentials, tokens, raw logs with PII, chat noise.## Continuous Save Cadence1. **Start** — `recall` before exploring from scratch2. **Dedupe** — `recall` the candidate fact; if present, `update_memory` instead of duplicate retain3. **Milestone / end** — `sync_retain` one distilled outcome per resolved issue## Other Tools| Tool | When ||------|------|| `reflect(query=...)` | Synthesized judgment across memories || `list_memories(q=...)` | Browse/audit || `update_memory` / `invalidate_memory` | Correct or retire stale facts |## Failure ModeIf Hindsight MCP is disconnected or auth fails: note once, continue the task. Memory is an accelerator, not a blocker. Do not retry auth in a loop.

Frequently asked questions