handoff-engineering vs Moxie Docs
handoff-engineering is a plugin bundle for AI coding tools published by Alireza Rezvani. Marketplaces we read that list it: 1 (Community GitHub marketplaces). Moxie Docs is an MCP server published by Jackalope-Dev. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-29. 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 |  Moxie Docs | |
|---|---|---|
| Community marketplace alirezarezvani/claude-skills | Listed Version: 2.14.2 Forks (GitHub): 4 016 Stars (GitHub): 28 939 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.3.0 Forks (GitHub): 0 Stars (GitHub): 2 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 | handoff-engineering | Moxie Docs |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 28 939 (better) | 2 (worse) |
| Forks (GitHub) (differs) | 4 016 (better) | 0 (worse) |
| Last release (differs) | 2026-10-26 | Not published |
| Where it runs (differs) | Installs as a plugin bundle | Remote server (moxiedocs.com/api/mcp) |
| Transport (differs) | Not stated | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Parts of the bundle (differs) | 3 | Not a bundle |
| Licence | MIT | MIT |
| Repository (differs) | github.com/alirezarezvani/claude-skills | github.com/jackalope-dev/moxie-docs-mcp |
| Changes in the last 7 days (differs) | 2 | 0 |
| First seen (differs) | 2026-10-14 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 21 h ago |
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
handoff-engineering
Conversation-handoff document generator. Compacts the current session into a markdown handoff for a fresh agent — references existing artifacts (PRDs, plans, ADRs, issues, commits) by path/URL instead of duplicating them. Derived from Matt Pocock's MIT-licensed handoff with: (1) 3 stdlib Python tools (template generator tailored to 5 next-session emphases, artifact deduplicator across 5 categories of duplication, skill recommender matching content to 14 skills in this repo), (2) 4 references citing 7-8 sources (handoff structure, deduplication discipline, next-session skill matching, companion tooling), (3) cs-handoff-author persona agent + /cs-handoff slash command. Matt's no-duplication discipline + mktemp convention preserved verbatim per MIT.
Moxie Docs
Living docs and MCP context for GitHub repos — conventions, gaps, and source-cited pages on merge.
How to run each
handoff-engineering As a Claude Code plugin
/plugin marketplace add alirezarezvani/claude-skills
/plugin install handoff-engineering@claude-code-skillsMoxie Docs As a remote MCP server
claude mcp add --transport http moxie-docs https://moxiedocs.com/api/mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only Moxie Docs has a remote endpoint we check. How we check endpoints
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
Neither one's marketplaces publish the settings it asks for.
What it can do: handoff-engineering · What it can do: Moxie Docs · Compare two other plugins
Data comes from public marketplace files in GitHub repositories of their authors. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.