sensei vs skillmem
sensei is a plugin bundle for AI coding tools published by jreynolds-dev. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). skillmem is an MCP server published by liza-studio. Marketplaces we read that list it: 2 (Official MCP Registry, Community GitHub marketplaces). As of our marketplace pass on 2026-10-16. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.
Where each is published
| Marketplace |  sensei |  skillmem |
|---|---|---|
| Claude Code: claude-plugins-community | Listed Version: 1.0.0 Forks (GitHub): 0 Stars (GitHub): 1 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.12.1 Downloads/month (PyPI): 4 269 Downloads/week (PyPI): 112 Forks (GitHub): 4 Stars (GitHub): 9 Not marked · First seen |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | sensei | skillmem |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 2 (better) |
| Stars (GitHub) (differs) | 1 (worse) | 9 (better) |
| Forks (GitHub) (differs) | 0 (worse) | 4 (better) |
| Last release | Not published | Not published |
| Where it runs (differs) | Installs as a plugin bundle | On your machine (skillmem) |
| Transport (differs) | Not stated | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | Not published | 1, secrets among them: 0 |
| Hooks it runs (differs) | Not published | 8 |
| Parts of the bundle (differs) | 14 | 7 |
| Licence (differs) | MIT | Apache-2.0 |
| Repository (differs) | github.com/jreynolds-dev/sensei | github.com/liza-studio/skillmem |
| Changes in the last 7 days (differs) | 0 | 2 |
| First seen | 2026-10-11 | 2026-10-11 |
Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.
What each says it does
sensei
Sensei is a Claude Code plugin that turns any project into a guided learning environment. It installs a persistent AI mentor — selectable between Master Splinter and Gandalf — that teaches through the Socratic method rather than serving direct answers. Key behaviors: Code gate — refuses to give code unless the student uses a character-specific safeword or demo trigger - Session lifecycle — /dojo-open sets a micro-goal, /pizza-time closes the session and updates progress tracking - Spaced repetition — tracks concepts introduced, practiced, and mastered across sessions - Character integrity — hooks enforce voice and teaching stance across every message, preventing drift
skillmem
Skill memory for coding agents: learn, recall, reinforce, decay. Local SQLite, no API key.
How to run each
sensei As a Claude Code plugin
/plugin marketplace add anthropics/claude-plugins-community
/plugin install sensei@claude-communityskillmem As a local MCP server: PyPI package
claude mcp add --transport stdio skillmem -- uvx skillmem mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
The marketplaces of sensei publish no settings it asks for, so we do not compare settings.
What it can do: sensei · What it can do: skillmem · Compare two other plugins
Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Data comes from public marketplace files in GitHub repositories of their authors. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.