Ext Ops Panel
Open dashboard
Comparison

ensue-auto-memory vs dataverse

ensue-auto-memory is a plugin bundle for AI coding tools published by christinetyip. Marketplaces we read that list it: 1 (Community GitHub marketplaces). dataverse is a plugin bundle for AI coding tools published by microsoft. Marketplaces we read that list it: 2 (Copilot CLI: github/awesome-copilot, Copilot CLI: github/copilot-plugins). As of our marketplace pass on 2026-10-15. 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

Where each is published
Marketplaceensue-auto-memorydataverse
Community marketplace christinetyip/ensue-auto-memory Listed
Version: not stated
Forks (GitHub): 0
Stars (GitHub): 7
Not marked · First seen
Not listed
Copilot CLI: github/awesome-copilot Not listed Listed
Version: 1.0.0
Forks (GitHub): 64
Stars (GitHub): 245
Not marked · First seen
Copilot CLI: github/copilot-plugins Not listed Listed
Version: not stated
Forks (GitHub): 64
Stars (GitHub): 245
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

ensue-auto-memory vs dataverse
Factensue-auto-memorydataverse
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub) (differs)7 (worse)245 (better)
Forks (GitHub) (differs)0 (worse)64 (better)
Last releaseNot publishedNot published
Where it runsInstalls as a plugin bundleInstalls as a plugin bundle
TransportNot statedNot stated
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Hooks it runs (differs)3Not published
Parts of the bundle (differs)4Not published
Licence (differs)Not statedMIT
Repository (differs)github.com/christinetyip/ensue-auto-memorygithub.com/microsoft/dataverse-skills
Changes in the last 7 days22
First seen (differs)2026-10-152026-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

ensue-auto-memory

In its own words, on Community GitHub marketplaces:

Automatic persistent memory that saves preferences, corrections, and project context. Works invisibly in the background.

dataverse

In its own words, on Copilot CLI: github/awesome-copilot:

Build and manage Microsoft Dataverse solutions using natural language. Includes table/column creation, solution lifecycle, data operations, and MCP server configuration.

How to run each

ensue-auto-memory As a Claude Code plugin

Claude Code
/plugin marketplace add christinetyip/ensue-auto-memory
/plugin install ensue-auto-memory@ensue-auto-memory

dataverse

No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.

Commands 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

Neither one's marketplaces publish the settings it asks for.

What it can do: ensue-auto-memory · What it can do: dataverse · Compare two other plugins

Data comes from public marketplace files in GitHub repositories of their authors. Data comes from the public marketplace file https://github.com/github/awesome-copilot/blob/HEAD/.github/plugin/marketplace.json. Data comes from the public marketplace file https://github.com/github/copilot-plugins/blob/HEAD/.github/plugin/marketplace.json. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.

Where the data comes from: how the catalog is built