AI tool comparison
Karpathy Skills vs SMF (Semantic Memory Filesystem)
Which one should you ship with? Here is the side-by-side panel verdict, pricing read, reviewer split, and community vote comparison.
Developer Productivity
Karpathy Skills
Andrej Karpathy's LLM coding wisdom packed into a single CLAUDE.md plugin
75%
Panel ship
—
Community
Free
Entry
Karpathy Skills is a CLAUDE.md plugin distilled from Andrej Karpathy's public observations on LLM coding pitfalls. Drop the single file into your project root (or install it as a Claude Code skill) and every Claude Code session starts pre-loaded with the four principles Karpathy identified as most commonly violated: think before writing, prefer simplicity, make only targeted changes, and close loops with explicit verification. The project has accumulated 1,450+ GitHub stars in under two weeks. The implementation is intentionally minimal — it's a structured system prompt, not a framework. Each principle is spelled out with concrete anti-patterns to avoid: no premature generation, no over-engineering simple tasks, no cascading refactors when a surgical fix suffices, no ending a session without verifying the goal was actually met. It's Karpathy's "Software 2.0" thinking applied to the agent workflow meta-layer. What makes this compelling isn't the technology — it's the curation. Karpathy has spent more time thinking about LLM behavior patterns than almost anyone outside the major labs. Packaging that into something installable in 30 seconds lowers the floor for teams who want more reliable agent outputs without extensive prompt engineering work.
Developer Tools
SMF (Semantic Memory Filesystem)
Your filesystem IS the vector database for AI agents
75%
Panel ship
—
Community
Paid
Entry
SMF (Semantic Memory Filesystem) is an open-source Python library that treats the POSIX filesystem as the native memory infrastructure for AI agents. The core bet: instead of standing up a vector database, embedding service, and retrieval pipeline, you model your agent's memory as ordinary directories, files, and symlinks — then use the OS's own tools for retrieval. Entities are directories, relationships are symlinks, metadata is file attributes, and search is built on grep and find. The appeal is radical simplicity. Every developer already understands the filesystem. Memory built on top of it is inspectable with any editor, versionable with git, and portable across machines with rsync. There's no new query language to learn, no vector index to maintain, and no external service to keep running. Dynamis-Labs argues that for many agent memory use cases, semantic similarity search is overkill — you need entity graphs and efficient lookup, which the filesystem already provides. With only 7 stars and created yesterday (April 14), SMF is in very early stages. But the approach has attracted immediate discussion from developers frustrated with the operational overhead of vector databases for relatively structured memory tasks. It's a contrarian bet that's worth watching.
Reviewer scorecard
“I've noticed a measurable improvement in Claude Code session quality after installing this. The 'verify before ending' principle alone has saved me from shipping broken refactors. It's a one-file install that acts like pair programming guardrails from someone who has thought deeply about LLM failure modes.”
“I've been burned too many times by embedding pipelines that drift when models update and vector indexes that mysteriously degrade. Filesystem-native memory is zero-dependency, trivially inspectable, and you can version it with git. For structured agent memory this is genuinely compelling.”
“This is four bullet points in a markdown file. The signal-to-hype ratio here is completely off — 1,400 stars for something you could write yourself in ten minutes. The underlying principles are sound, but attributing them to Karpathy as a canonical plugin feels like name-dropping disguised as engineering.”
“The filesystem approach breaks down the moment you need fuzzy semantic matching — 'find memories related to customer churn' doesn't map to a grep. For anything beyond exact lookup, you're going to bolt on a vector DB anyway and now you have two systems. This is clever for toy agents, not production.”
“The interesting meta-signal here is that the AI community is converging on a shared vocabulary for agent behavior principles. CLAUDE.md-as-skill-format is becoming a de facto standard for distributable agent instructions. This project is early evidence that the best agent tooling might be curated wisdom, not code.”
“The insight that the filesystem is a perfectly good entity-relationship store is underappreciated. As agents move toward local-first architectures, having memory that's portable, inspectable, and git-versionable becomes a serious advantage over cloud-hosted vector DBs.”
“For non-engineers using Claude Code to build things, having these guardrails prevents the most frustrating failure modes — the model that goes off and rewrites everything when you wanted one small change. Lowering that friction makes AI coding tools actually usable for creative people who aren't professional developers.”
“I love tools that demystify AI plumbing. The idea that agent memory could just be files I can open in a text editor makes the whole system feel less like a black box. This is the kind of transparency that builds trust.”
Weekly AI Tool Verdicts
Get the next comparison in your inbox
New AI tools ship daily. We compare them before you waste an afternoon.