suyask-msft 8bfc9f3c4b Source dataverse plugin externally from microsoft/Dataverse-skills (#1010) ...

* Source dataverse plugin from microsoft/Dataverse-skills

The Dataverse plugin was previously bundled locally with a single
mcp-configure skill. It is now sourced externally from
microsoft/Dataverse-skills, which provides the full skill set:
init, setup, metadata, python-sdk, solution, mcp-configure, and overview.

- marketplace.json: update dataverse entry to external source format
- external.json: add Dataverse entry alongside Azure
- plugins/dataverse/: remove local plugin directory (now external)
- skills/mcp-configure/: remove top-level copy (now in external plugin)
- docs/README.plugins.md: update dataverse row with external link
- docs/README.skills.md: note mcp-configure moved to external plugin

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

* Make dataverse plugin docs generic to avoid stale counts

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

* Remove mcp-configure from skills index — now in external plugin

External plugins don't list their skills in README.skills.md
(consistent with azure-skills).

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

* Revert manual edits to generated files

marketplace.json, README.plugins.md, and README.skills.md are
auto-generated. External plugins are discovered via external.json
and merged into marketplace.json by generate-marketplace.mjs.
Matches the Azure external plugin pattern — no manual doc entries.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

* Regenerate marketplace.json and docs after external plugin change

Run npm run build to pick up the new external dataverse entry and
remove the old local one from generated files.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

---------

Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>

2026-03-17 08:32:26 +11:00

19 KiB

Raw Blame History

View Raw