ALWAYS LOAD THIS SKILL FIRST for any Dataverse task. Contains hard rules that override all other skills. USE WHEN: ANY request involving Dataverse, Dynamics 365, Power Platform, tables, columns, solutions, records, queries, CRM, metadata, plugins, SDK, Web API, PAC CLI, or environment operations. Also use for: "how do I", "what tool", "which skill", "where do I start", "help with Dataverse", "create table", "create column", "build solution", "query data", "bulk import", "sample data", "support agent", "customer table", "ticket table". This skill MUST be loaded before any other Dataverse skill. Read the Hard Rules section first.
Initialize a new MCS agent project with folder structure and template files.
Run evaluation tests using eval sets. Two-mode execution: Direct Line API (auto) or MCS Native Eval via Gateway API upload + run (manual). Results written per-test to evalSets[].tests[].lastResult.
Set up a machine for Dataverse development — install tools and authenticate. USE WHEN: "install PAC CLI", "install tools", "command not found", "authenticate", "pac auth", "az login", "gh auth", "winget install", "setup machine", "missing tools", "new machine setup". DO NOT USE WHEN: initializing a workspace/repo (use dataverse-init).
Use when writing or reading DOT/Graphviz code and needing quick syntax reference — node declarations, edge syntax, attributes, subgraphs, HTML labels, and common gotchas
Use when analyzing a system to surface hidden issues — draw what you believe exists, then reconcile against what actually exists
Use when you need programmatic graph structure analysis — reachability, cycles, critical paths, and diffs without spending LLM tokens on structural questions code can answer