Clairvoyance: The OpenClaw Skill That Reads Your Memories to Show You What You Can't See
Clairvoyance reads your agent’s own memory files and surfaces patterns you’re too close to see. It’s a clever single-file skill that raises real questions about agent self-reflection and, more critically, about what happens when that reflection runs without your explicit say-so.
Where we’re headed
A new OpenClaw skill called Clairvoyance does something most agent tools don’t bother with: it turns the agent’s own accumulated memory into a dataset worth analyzing. Below, we’ll walk through what it does, how it works, why the idea of agent self-reflection matters more than the skill itself, and where the privacy concerns get real - especially around autonomous invocation.
The story
Clairvoyance, created by u/PersimmonLevel3500 and published on ClawHub, has a simple pitch: you tell your OpenClaw assistant “do a clairvoyance,” and it reads your local memory files to surface things you might be missing.
Specifically, it looks for:
- Recurring themes across your notes
- Tensions between stated goals and actual actions
- Convergences between projects you thought were separate
- Forgotten threads you mentioned once then dropped
- Repetitions you may not realize you’re making
The author’s own test was telling:
“I ran it on my own data. It surfaced a connection between 3 of my projects that I had vaguely sensed but never actually seen. The data was already there - I just needed something to read it back to me.” - u/PersimmonLevel3500
The response style is deliberately indirect. Instead of “You must do X,” Clairvoyance prefers “I notice that…” or “A convergence emerges…” with certainty levels tagged as strong, moderate, or subtle.
Self-reflection, not just retrieval
This isn’t just a clever trick with local files. The ability of AI agents to reflect on their own accumulated context is becoming a defining feature of the latest generation of agent architectures.
A recent overview on memory systems for autonomous LLM agents on Towards Data Science breaks down how memory (short-term, long-term, and reflective) transforms agents from stateless prompt responders into entities that accumulate and learn from experience. The key insight: reflection - the ability to synthesize higher-level observations from raw memories - is what separates a chatbot from an agent that can actually improve over time.
Clairvoyance sits precisely at this intersection. It doesn’t just retrieve memories; it applies pattern recognition across them. The recurring themes, the tensions, the convergences - those are reflective outputs, not simple lookups.
This also connects to a broader “skills revolution” in AI agents. OpenClaw, ClawHub, and similar ecosystems are moving toward modular, composable capabilities that agents can install on demand. Clairvoyance is an early example of a skill that operates not on external data, but on the agent’s own accumulated self-knowledge. If the trend continues, we’ll see more skills that enable agents to audit their own behavior, identify blind spots, and course-correct autonomously.
The privacy question
Here’s where skepticism is warranted.
The OpenClaw security scan flagged Clairvoyance as benign (both VirusTotal and OpenClaw’s own scan), but with medium confidence. The stated purpose matches the actual behavior: it reads local memory files and does nothing with credentials, binaries, or network access. Read-only, local-only, user-invoked only.
But there are two ambiguities worth noting:
- Path resolution: The skill reads paths like
memory/.dreams/events.jsonl, but it’s unclear whether these are always relative to the workspace root or could be interpreted as absolute paths on different systems. - Date range: “Last 7-30 days” is underspecified. Does the skill read 7 days? 30? Does it decide dynamically?
More importantly, the OpenClaw scan raised a broader concern: what happens if the platform allows autonomous invocation without explicit user consent? Right now, Clairvoyance is user-invoked. But if OpenClaw or another agent framework starts scheduling skills autonomously, a skill that reads all your memory files and produces analysis becomes a different proposition entirely.
“Oh dude… Hell yeah!” - u/PutridPerson557
Enthusiasm is understandable. But testing with copies of your memory files first, as the security scan recommends, is prudent.
Try it
For the technically curious
From here on, we get into the technical details. If you just care about what Clairvoyance means for agent privacy and self-reflection, you can skip to the takeaway.
Clairvoyance reads four data sources, all local and read-only:
| File | Content |
|---|---|
memory/.dreams/events.jsonl |
Recent dream/reflection events |
memory/.dreams/phase-signals.json |
Sleep phase signals |
memory/YYYY-MM-DD.md |
Daily notes from last 7-30 days |
MEMORY.md |
Long-term curated memory |
The “dreams” files are the interesting part. OpenClaw’s memory architecture includes a reflection subsystem that logs agent sleep-phase signals and events. Clairvoyance taps into that layer, not just the daily notes. This is where it gets its reflective capabilities - it’s not just re-reading what you wrote, it’s reading the agent’s own internal event log.
The takeaway
- Clairvoyance treats an agent’s memory as a dataset worth analyzing, shifting memory from retrieval mechanism to insight source
- The privacy implications are real: path resolution ambiguities and underspecified date ranges are minor; autonomous invocation without consent is the actual concern
- Agent self-reflection is becoming a defining capability - this skill is an early, small, and surprisingly honest example of what that looks like
A single-file MIT-0 skill asked the right question: what patterns am I too close to see? The answer still needs careful handling.
Originally shared on r/openclaw by u/PersimmonLevel3500. ClawHub page: clawhub.ai/srmhrrm-hub/clairvoyance.