Ext Ops Panel
Open dashboard
Comparison

requirement-elicitation vs dataverse

requirement-elicitation is a plugin bundle for AI coding tools published by Britt Crawford. 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-23. 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
Marketplacerequirement-elicitationdataverse
Community marketplace britt/agent-skills Listed
Version: 1.1.0
Forks (GitHub): 1
Stars (GitHub): 8
Not marked · First seen
Not listed
Copilot CLI: github/awesome-copilot Not listed Listed
Version: 1.16.1
Forks (GitHub): 64
Stars (GitHub): 247
Not marked · First seen
Copilot CLI: github/copilot-plugins Not listed Listed
Version: not stated
Forks (GitHub): 64
Stars (GitHub): 247
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

requirement-elicitation vs dataverse
Factrequirement-elicitationdataverse
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub) (differs)8 (worse)247 (better)
Forks (GitHub) (differs)1 (worse)64 (better)
Last release (differs)Not published2026-10-23
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
Licence (differs)Not statedMIT
Repository (differs)github.com/britt/agent-skillsgithub.com/microsoft/dataverse-skills
Changes in the last 7 days (differs)43
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

requirement-elicitation

In its own words, on Community GitHub marketplaces:

Adaptive conversational wizard for eliciting project requirements across functional, nonfunctional, and edge-case dimensions

dataverse

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

Microsoft Dataverse plugin for coding agents, covering record CRUD, bulk data operations, advanced queries, schema and metadata, administration, security, environment management, and solution lifecycle through MCP, CLI, and SDK workflows.

How to run each

requirement-elicitation As a Claude Code plugin

Claude Code
/plugin marketplace add britt/agent-skills
/plugin install requirement-elicitation@britt

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: requirement-elicitation · 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