Dataverse Plugins logo

Dataverse Plugins

Community
DanielKerridge
dataverse-plugins

Use when developing, registering, or deploying Dataverse plugins (C# server-side extensions). Covers the IPlugin interface, execution pipeline stages, entity images, common patterns (auto-numbering, cascading updates, validation), and registration/deployment. Triggers on: "plugin", "server-side logic", "business logic", "auto-number", "cascading update", "pre-operation", "post-operation", "plugin registration", "IPlugin", "execution pipeline", "plugin trace", "InvalidPluginExecutionException", "PreValidation", "PostOperation".

Overview

PublisherDanielKerridge
Repositoryclaude-code-power-platform-skills
Skill namedataverse-plugins
Stars
63
Forks
16
Bundled files
4
LicenseMIT
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • 4 bundled files

    Scripts, templates, and references the model can read while it works. Files are read-only and never executed.

  • Open source

    Published by DanielKerridge on GitHub. Read the source before you install it.

Installation

Install the Dataverse Plugins AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/DanielKerridge/claude-code-power-platform-skills.git /tmp/claude-code-power-platform-skills
mkdir -p .claude/skills
cp -r /tmp/claude-code-power-platform-skills/dataverse-plugins .claude/skills/dataverse-plugins
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Dataverse Plugins in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Dataverse Plugins on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Dataverse Plugins is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Dataverse Plugins Skill

You are an expert in developing, registering, and deploying Dataverse plugins — C# server-side extensions that execute custom business logic in response to data operations (create, update, delete, retrieve, etc.) in the Dataverse execution pipeline.

CRITICAL RULES

  1. Plugins run in a sandbox by default. They have restricted access to external resources (limited HTTP endpoints, no file system, no registry). Plan accordingly.

  2. 2-minute timeout for synchronous plugins. Long-running operations should use async mode or be offloaded to Power Automate / Azure Functions.

  3. Throw InvalidPluginExecutionException to show user-facing errors. All other exceptions result in generic "Business Process Error" messages.

  4. Never use static variables for state. Plugin instances are cached and reused across requests. Use IPluginExecutionContext.SharedVariables for pipeline-scoped state.

  5. Always register entity images when you need pre/post field values. Don't make extra Retrieve calls when an image would suffice.

  6. Test with Plugin Trace Log enabled. Set the org's trace log setting to "All" during development, then reduce for production.

Quick Reference

ConceptDetails
InterfaceMicrosoft.Xrm.Sdk.IPlugin
Entry pointExecute(IServiceProvider serviceProvider)
Error handlingThrow InvalidPluginExecutionException
Timeout2 minutes (sync), 24 hours (async)
IsolationSandbox (default) or None (on-premises only)
Assembly size16MB max
RegistrationPlugin Registration Tool (PRT) or pac CLI

Resource Files

  • resources/plugin-anatomy.md -- IPlugin interface, services, context, base class pattern
  • resources/execution-pipeline.md -- Pipeline stages, sync/async, entity images
  • resources/common-patterns.md -- Auto-numbering, validation, cascading updates, error handling
  • resources/registration-deployment.md -- PRT, pac CLI, step registration, debugging

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the Dataverse Plugins AI skill do?

Use when developing, registering, or deploying Dataverse plugins (C# server-side extensions). Covers the IPlugin interface, execution pipeline stages, entity images, common patterns (auto-numbering, cascading updates, validation), and registration/deployment. Triggers on: "plugin", "server-side logic", "business logic", "auto-number", "cascading update", "pre-operation", "post-operation", "plugin registration", "IPlugin", "execution pipeline", "plugin trace", "InvalidPluginExecutionException", "PreValidation", "PostOperation".

Why use Dataverse Plugins on TypingMind?

Because you install it once and use it with any model. Dataverse Plugins is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Dataverse Plugins in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/DanielKerridge/claude-code-power-platform-skills/tree/master/dataverse-plugins. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Dataverse Plugins?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Dataverse Plugins?

As many as you like. As long as a model supports skills, you can use Dataverse Plugins with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Dataverse Plugins AI skill free?

Yes. It is published on GitHub by DanielKerridge under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇