Ghost Memory taps the collective memory of thousands of developers — the fixes, the shortcuts, the traps they learned the hard way — and feeds the right one into your agent as you code. Ranked by what actually works. Measured, not upvoted.
then ghost init — see your candidates in 90 seconds
Prefer pip? pip install git+https://github.com/mathischarlesgauthier/ghost-memory
Runs on your existing history. Nothing leaves your machine.
670,000 skills out there, ranked by download count. A number you can buy. It tells you nothing.
Ghost Memory ranks by lift — how much a skill actually improves a real task, measured by rerunning it.
We don't count. We measure.
Your agent stops rediscovering what you already taught it.
Ghost Memory only learns from your sessions, your repo, your conventions.
No files to write. No skills to hunt for. No config.
Every correction you make becomes capital. The knowledge isn't in the docs — it's in the 7 times it broke before it worked.
Runs on your existing history, on your machine. Nothing is published without you seeing the diff first.
One command. Zero config. And it runs on the history you already have — you see the result in 90 seconds.
read your past sessions
distill them into skills
wire them into your agent
That's it. Then you just work.
You explain that migrations on your ledger table have to go through batch_alter_table. It gets it. It works.
New session. It doesn't know. Seven attempts. Forty minutes.
Your new hire hits the same wall.
You've paid for that lesson three times.
What Claude gets right on the first try.
It's in the model. Everyone has it. Any prompt regenerates it.
The 7 times it broke before it worked.
The 12 times you said "no, not like that."
That doesn't exist anywhere except in your history. By definition, no model can guess it — if it could, you wouldn't have had to correct it.
Ghost Memory reads your scars.
Your own history only gives you back what you already learned the hard way. Useful — you never pay for it twice. But you already took the hit.
The wall you'll hit next Thursday, someone already hit it. Their scar is distilled, measured, and waiting.
You cannot build that alone. No matter how good you are.
We never charge for retrieving your own skills, distilling on your own key, or validating. You pay only for access to the collective memory — measured in unlocks.
An unlock is a distinct community skill added to your library. Yours to reuse as much as you want, as long as your plan is active.
We never charge for your own work. Only for the collective memory you draw from.
Beyond your quota, pay as you go — like your API bill, but for skills that actually work.
How much a skill actually improves a task — measured by rerunning it, not guessed from a download count.
670,000 skills out there, ranked by download count — a number you can buy.
We rank by what a skill does to real code.
We don't count. We measure.
Every real number on this site comes from replaying your own past tasks. Until yours are measured, the examples above are just that — examples.
Turns your coding history into skills your agent actually uses.
You already wrote your best skill. You just don't know it yet.
Your coding agent has goldfish memory.
Monday you teach it something. Thursday it makes the same mistake.
I built Ghost Memory: it reads your session history, pulls out what you already taught it, and feeds it back automatically.
uv tool install git+https://github.com/mathischarlesgauthier/ghost-memory — runs on your existing history.
I pointed it at my own 412 Claude Code sessions.
47 skill candidates. 312 failure loops. 89 times I had to correct it by hand.
Six months of scars, sitting there, unused.
Nobody writes agent skills because writing one is 2 hours of unpaid work.
That's why 80% of the 670k public skills are slop.
So we stopped asking people to write them. We extract them from what you already did.