Skill: Query — Read and Analyze Dataverse Records

Bulk reads, multi-page iteration, and analytics over Dataverse data.

Context cost
8.9k tokensestimated from the bundle, loaded when it triggers
Bundle
5 files · 35.7 kBtext throughout, nothing executable
Licence
MITthe author’s own terms
Last change
—no release on file
Servers it uses
Noneruns standalone

What it does

Bulk reads, multi-page iteration, and analytics over Dataverse data. Use when the user wants to read, list, filter, aggregate, group, join, or analyze records — including pandas DataFrame workflows and notebook exploration. Also covers ERP (Finance and Operations / F&O) business-data reads and runtime entity, schema, or action discovery; load dv-overview first, then this skill.

What this skill changes about the agent has not been set out here as a list. Its SKILL.md, shown below, says it in the author’s own words.

analyticsdatabase
Filed under

Databases

The skill itself

A skill is instructions the model reads, so you can see what you are getting: below is the start of its SKILL.md. The front matter loads with every session, the body loads when the skill triggers, and the whole file comes with the install.

SKILL.md18.1 kB · preview
--- name: dv-query ---
6# Skill: Query — Read and Analyze Dataverse Records
7
8> **This skill uses Python and the Dataverse CLI.** Do not use Node.js, JavaScript, or any other language for Dataverse scripting. See the overview skill's Hard Rules.
9
10## Reads: prefer a managed surface, choose by shape
11
12**Fast path for simple reads:** If dataverse auth who shows an active profile, skip workspace setup and query directly with the CLI examples below. No .env, auth.py, pip install, or PAC needed for data reads.
13
14Pick **MCP, the Dataverse CLI, or the SDK by the shape of the read** — all three handle auth and retry (see the routing table below and the overview's **Tool Capabilities** / Hard Rule 2). MCP fits small, interactive reads; the CLI fits headless one-liners (OData, SQL, count); the SDK fits bulk iteration and analytics. For $apply aggregation and N:N $expand, prefer client.query.fetchxml() (aggregates + link-entity) or the managed dataverse api escape hatch; reach for hand-rolled urllib/get_token() **only** to stay in-process inside a tight Python loop (e.g. paging thousands of rows with client-side processing — see web-api-advanced.md).
15
16### Dataverse CLI gotchas (custom tables + Windows)
17
18When you drive the dataverse CLI directly (headless reads/CRUD; note the CLI needs .NET + a keyring, so it is blocked on ChatGPT web / Codex cloud — use the SDK there), two empirical traps:
19
20- **Custom-table SQL pluralization.** dataverse data query in SQL mode auto-pluralizes the table name, and irregular plurals resolve wrong: FROM im_category looks up entity set im_categorys and returns a **404** that reads like "table missing." It is not — switch to OData mode with the explicit entity set: dataverse data query --table im_categories --select im_name. Discover the real EntitySetName from EntityDefinitions when unsure; never conclude the table doesn't exist from this 404.
21- **Windows shell quoting.** Wrap the whole --path value in double quotes so cmd.exe/PowerShell don't treat & as a command separator. Keep & **literal** — it separates OData query options; encoding it to %26 merges them and breaks the query. Encode only $->%24 (in PowerShell a bare $select is read as a variable). If an unquoted & splits the command, the wrapper can exit nonzero *even when the API returned valid JSON* — quoting prevents it. (This is why the dataverse api request examples in other skills quote the path, use %24, and leave & literal.)
22
23### Dataverse CLI query examples (copy-paste ready)
24
This is a preview of SKILL.md. Download or install the skill to get the whole thing.
In the file
SKILL.md2,294 words
Files5
LicenceMIT
Why you can read it

Nothing in a skill executes. The client loads the text and the model follows it, so a skill can be audited the way a runbook is — by reading it.

What it costs in context

Skills are not billed by the call. They are paid for in context: every token the instructions occupy is a token your code, your diff and your conversation cannot use. Here is what this one takes and when it takes it.

≈100
always loaded
The name and description, so the model knows the skill exists and when to reach for it.
8,825
on trigger
The instruction body and 4 supporting files, read only when the skill fires.
4.5%
of a 200k window
Ten skills this size would take about 45% of the window before you open a file.
050k100k150k200k context window

8.9k tokens, estimated from the bundle at four bytes to the token, held for the rest of the session once it triggers. Heavy. Teams tend to install this one per project rather than globally, and load it only when the job comes up.

Servers bill, skills cost

A server charges by the month. A skill charges once per session, in context, and then keeps charging it for as long as the session lives.

Before and after

The same question, put to the same model twice: once as it comes, and once with these instructions loaded.

No worked example has been published for this skill yet.

The procedure it runs

The procedure has not been set out here step by step. It is in the body of its SKILL.md: the start of it is shown above, and the whole file comes with the install.

Prose, not code

These steps are written for a model to follow, not executed by a runtime. It can still be told to skip one, and it will say so when it does.

Servers it uses

None. This skill calls no MCP servers at all.

Everything it needs is in the instructions, so it works in a project with nothing connected — the model reads the file and changes how it works with what it can already reach.

Its SKILL.md does not declare which tools it asks the agent for, so what it touches is whatever the instructions themselves ask for — read them before you install it.

What it asks for
Writes filesnot declared
Network accessnot declared

This SKILL.md carries no allowed-tools line, so neither is declared. A skill grants no permissions of its own — it can only ask for tools your client already has.

What it will not do

Every skill is narrow, and the useful ones say where they stop. These are the jobs this one is the wrong tool for.

What this skill is not for has not been published here. Nothing is implied by that: it is a section the author has not filled in.

What is in the bundle

5 files, 35.7 kB on disk. A bundle is text throughout: the instructions the model reads, plus the templates it fills in.

  • SKILL.md18.1 kB
  • references/erp-reads.md4.2 kB
  • references/jupyter-setup.md2.0 kB
  • references/querybuilder.md5.1 kB
  • references/web-api-advanced.md6.3 kB
What is not in it

No dependencies and nothing executable: a skill is text the agent reads, so the bundle is 5 files you can review in full before installing. The MIT licence covers the templates and examples as well as the instructions.

Install

Installing copies the bundle into your project. Nothing runs at install time — the files sit on disk until the model reads them.

# Skill: Query — Read and Analyze Dataverse Records · 8.9k tokens when loaded · macOS, Linux mkdir -p .claude/skills && t=$(mktemp -d) && curl -fsSL -o "$t/bundle.tar.gz" https://mcprush.com/api/skills/skill-query-read-and-analyze-dataverse-records/bundle.tar.gz && tar -xzf "$t/bundle.tar.gz" -C "$t" && [ -d "$t/skill-query-read-and-analyze-dataverse-records" ] && { [ ! -e .claude/skills/skill-query-read-and-analyze-dataverse-records ] || { mv .claude/skills/skill-query-read-and-analyze-dataverse-records "$t/.previous" && echo "Previous copy moved to $t/.previous"; }; } && mv "$t/skill-query-read-and-analyze-dataverse-records" .claude/skills/ && echo "Installed .claude/skills/skill-query-read-and-analyze-dataverse-records"
On Windows, or any OS with Node 20+
npx mcprush@latest skill add microsoft/skill-query-read-and-analyze-dataverse-records

Windows PowerShell says 'running scripts is disabled on this system'? Run Set-ExecutionPolicy -Scope CurrentUser RemoteSigned once, or type npx.cmd instead of npx (codex.cmd, gemini.cmd, grok.cmd likewise). PowerShell 7 needs neither. Writes to .claude/skills/skill-query-read-and-analyze-dataverse-records/ in the current project. For every project instead, run mkdir -p ~/.claude/skills && t=$(mktemp -d) && curl -fsSL -o "$t/bundle.tar.gz" https://mcprush.com/api/skills/skill-query-read-and-analyze-dataverse-records/bundle.tar.gz && tar -xzf "$t/bundle.tar.gz" -C "$t" && [ -d "$t/skill-query-read-and-analyze-dataverse-records" ] && { [ ! -e ~/.claude/skills/skill-query-read-and-analyze-dataverse-records ] || { mv ~/.claude/skills/skill-query-read-and-analyze-dataverse-records "$t/.previous" && echo "Previous copy moved to $t/.previous"; }; } && mv "$t/skill-query-read-and-analyze-dataverse-records" ~/.claude/skills/ && echo "Installed ~/.claude/skills/skill-query-read-and-analyze-dataverse-records" (macOS, Linux) — or add --global to the npx line. The curl line replaces .claude/skills/skill-query-read-and-analyze-dataverse-records/ only after the download succeeds, so files left there by another skill of the same name, or by an older release, do not mix in. A copy already there is moved aside, not deleted, and the line prints where. It appears as dv-query in Gemini CLI, Codex, Copilot and Grok (its own name); Claude Code lists it by the folder name, skill-query-read-and-analyze-dataverse-records.

Which clients pick it up on their own

A skill is a folder of text. Most of these read a skills folder and pick it up without being told; the rest take the same folder another way — an upload in the app, a parameter on an API call — and then choose it by its description just the same.

Claude Code.claude/skills/
Claude DesktopCustomize › Skills
ChatGPTSkills › Create › Upload
Cursor.cursor/skills/
VS Code.github/skills/
Codex CLI.agents/skills/
Gemini CLI.gemini/skills/
Grok Build.grok/skills/
Microsoft CopilotSkills › Upload a skill
PerplexityComputer › Skills › Upload a skill
DeepSeek Harness.dsh/skills/
Zed.agents/skills/
Devin Desktop.devin/skills/
Windsurf (legacy).windsurf/skills/
OpenAI Agents SDKInstructions or sandbox Skills
HTTP / APIa request parameter
This release
Versionnot versioned
Publishedno release date on file
PriceFree
Referencemicrosoft/skill-query-read-and-analyze-dataverse-records

Versions

Its author publishes no version number, so there is nothing here to pin to: what you install is the folder as it stands today. Instructions change more often than APIs do — a skill can be rewritten entirely without anything it depends on moving.

Pinning

Nothing to pin to: this skill carries no version number of its own. What you install is what the folder holds on the day you install it.

Reviews

—no reviews yet

Nobody has reviewed this skill yet. The rating is the mean of the reviews written here, so there is none until somebody writes the first.

Sign in to review it

A review is tied to an account so it can be answered, edited and taken down by the person who wrote it.

Sign in
Who can post

Anybody with an account, one review each. It carries the version that was current when you wrote it, and the publisher may reply once.

Publisher
Servers9
Claim this skill