setup-datamodel

Creates Dataverse tables, columns, and relationships for a Power Pages site based on a data model proposal. Use when the user wants to set up the data model, create database tables, or build the Dataverse schema for their site.

Quality

83%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Quality

Content

73%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is a well-sequenced, actionable 8-phase workflow with strong validation and feedback loops for a destructive batch operation, scoring high on workflow clarity and actionability. It loses points on conciseness due to repeated restatements of the phases/principles and on progressive disclosure due to referenced files missing from the bundle.

Suggestions

Consolidate the redundancy between Core Principles, Important Notes, and the Progress Tracking table — keep one authoritative phase/principle list and have the other sections reference it rather than restate it.

Verify or restore the referenced bundle files (dataverse-prerequisites.md, datamodel-manifest-schema.md, skill-tracking-reference.md, and the dataverse-request.js / verify-dataverse-access.js scripts) so the signaled one-level-deep references actually resolve.

Trim the gate blocks' 'Why we ask' and 'Cancel leaves' prose to a single line each to reduce token overhead while preserving the routing intent.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient procedural content, but Core Principles, Important Notes, and the Progress Tracking table all restate the same 8 phases and principles, and the gate blocks add verbose 'Why we ask'/'Cancel leaves' prose that could be tightened, placing it at mostly-efficient-with-some-redundancy rather than lean.	3 / 5
Actionability	Concrete executable commands ('node "${PLUGIN_ROOT}/scripts/dataverse-request.js" <envUrl> POST "api/data/v9.2/EntityDefinitions" ...') with defined placeholders and a fully concrete manifest example cover the common cases, but the JSON request bodies are deferred to references via placeholders, leaving a minor gap versus copy-paste-ready.	4 / 5
Workflow Clarity	Eight phases are clearly sequenced with explicit validation checkpoints (5.2 existence 404/200 checks, 8.2 post-creation verification), feedback loops (4.2 Request changes re-present, 404→create / 200→skip handling), and an upfront 8-task checklist, satisfying the validation-required bar for batch database creation.	5 / 5
Progressive Disclosure	The overview appropriately offloads bulk JSON templates to references/odata-api-patterns.md with clearly signaled one-level-deep paths, but several referenced files (dataverse-prerequisites.md, datamodel-manifest-schema.md, skill-tracking-reference.md, dataverse-request.js, verify-dataverse-access.js) are absent from the provided bundle and some inline content duplicates referenceable material, so structure is good but not pristine.	4 / 5
	Total	16 / 20 Passed

Description

92%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is concise, uses third person, and cleanly states both the capability and the use-when triggers for a well-scoped Power Pages/Dataverse skill. It is comprehensive on actions and triggers with only minor synonym coverage gaps.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'Creates Dataverse tables, columns, and relationships' — comprehensively covering the domain's core object types, matching the comprehensive-coverage anchor.	5 / 5
Completeness	Explicitly answers both what ('Creates Dataverse tables, columns, and relationships...') and when via a 'Use when the user wants to...' clause with concrete trigger phrases, matching the top anchor.	5 / 5
Trigger Term Quality	Natural phrases like 'set up the data model', 'create database tables', and 'build the Dataverse schema' give good coverage, but synonyms are limited and there are no file-extension or format triggers, so it sits just below comprehensive.	4 / 5
Distinctiveness Conflict Risk	Targets a clear niche — Power Pages Dataverse schema/data-model setup — with distinct triggers, making conflict with unrelated skills unlikely.	5 / 5
	Total	19 / 20 Passed

Validation

87%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
allowed_tools_field	'allowed-tools' contains unusual tool name(s)	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	14 / 16 Passed

Repository: microsoft/power-platform-skills
Path: plugins/power-pages/skills/setup-datamodel/SKILL.md
Commit: 4c284ab

Reviewed: 2 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.