From dataverse-xml-lsp
Use when editing, reviewing, or validating Dataverse / model-driven-app customization XML — RibbonDiff.xml, Customizations.xml, SiteMap, FormXml (forms), charts (visualization / datadefinition), FetchXML, viewers, or configuration-migration parameter XML — especially in headless / subagent / CI contexts or before `pac solution pack` / `pac solution import`. Runs the schema validator (Validate-DataverseXml.ps1) and explains how to read its output.
How this skill is triggered — by the user, by Claude, or both
Slash command
/dataverse-xml-lsp:dataverse-xml-validateThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Run the schema validator after editing Dataverse customization XML, and always in contexts where the
Run the schema validator after editing Dataverse customization XML, and always in contexts where the live LSP does not push diagnostics (subagents, headless, CI):
pwsh "${CLAUDE_PLUGIN_ROOT}/scripts/Validate-DataverseXml.ps1" <file-or-dir> [more paths / globs]
Non-zero exit = validation failed. It picks the schema by the file's root element and fails loud on unknown roots.
pac solution pack / import — a final gate so bad edits fail here, not at import.Whole-form FormXml and whole-file Customizations.xml validation is indicative, not
authoritative: the bundled 9.0.0.2090 schema lags modern attributes, so it reports false "not
declared" errors on out-of-the-box content. Confirm YOUR edit is clean by checking that no error
references your own element/attribute names (grep the output for them); treat pre-existing OOB noise
as expected. The ribbon fragment (RibbonCore.xsd) is authoritative.
Full root→schema table, the ribbon-button recipe, and gotchas: docs/guide.md.
npx claudepluginhub cordedmink2/dataverse-agent-plugins --plugin dataverse-xml-lspGuides completion of development work by verifying tests, detecting environment, and presenting structured options for merge, PR, or cleanup.
Guides creation and editing of skills using test-driven development with pressure scenarios and subagents to verify agent compliance.
Dispatches multiple subagents concurrently for independent tasks without shared state. Use when facing 2+ unrelated failures or subsystems that can be investigated in parallel.