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

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

77%

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

The content is a well-sequenced, highly actionable 8-phase workflow with strong validation checkpoints, though it carries some duplicated prose in the closing notes. Its main weakness is progressive disclosure: most referenced bundle files do not exist and the one reference that does chains into another missing file.

Suggestions

Add the missing referenced files (dataverse-prerequisites.md, datamodel-manifest-schema.md, skill-tracking-reference.md, scripts/check-version.js, scripts/dataverse-request.js, scripts/verify-dataverse-access.js) or remove the references so navigation is not broken.

Resolve the second-level reference: odata-api-patterns.md points to a missing odata-common.md — either provide it or inline the auth/retry content to keep references one level deep.

Trim the "Important Notes" section, which restates TaskCreate usage, no-rollback, and token-refresh already covered inline in the phases, to tighten conciseness.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient operational guidance, but the "Important Notes" section repeats inline content (TaskCreate/TaskUpdate, report-without-rollback, automatic token refresh) and the multi-line gate callouts could be tightened, matching level 2; it is not level 1 because it does not explain concepts Claude already knows.	2 / 3
Actionability	Every phase ships concrete, copy-paste-ready commands (e.g. `node "${PLUGIN_ROOT}/scripts/dataverse-request.js" <envUrl> POST "api/data/v9.2/EntityDefinitions"`) with exact endpoints and AskUserQuestion option tables, matching level 3; it is not level 2 because the guidance is executable rather than pseudocode or abstract.	3 / 3
Workflow Clarity	Eight phases are explicitly sequenced with Goal/Actions/Output, plus validation checkpoints (Phase 5 existence checks with 404/200 branching, Phase 8 verify-tables-exists, token refresh) and a progress-tracking checklist, matching level 3; it is not level 2 because validation and feedback loops are present rather than missing for these batch/database operations.	3 / 3
Progressive Disclosure	The body signals one-level-deep references per phase (e.g. "Refer to references/odata-api-patterns.md"), but of the seven referenced files only one exists, the lone existing reference itself points to a missing odata-common.md (2-level broken nesting), and the bundled scripts/validate-datamodel.js is unreferenced — so navigation is broken, matching level 2; it is not level 3 because references are not actually navigable, and not level 1 because the body itself is well-organized rather than a monolithic wall.	2 / 3
	Total	10 / 12 Passed

Description

100%

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 third-person, concise, and cleanly answers both what the skill does and when to invoke it with natural trigger terms. It carves a distinct niche (Power Pages Dataverse schema setup) with no over-claims. Strong across all dimensions.

Dimension	Reasoning	Score
Specificity	"Creates Dataverse tables, columns, and relationships" lists multiple specific concrete actions, matching the level-3 anchor; it is not level 2 because it goes beyond naming the domain to enumerate the concrete artifacts the skill produces.	3 / 3
Completeness	It states what ("Creates Dataverse tables, columns, and relationships...") and when ("Use when the user wants to set up the data model, create database tables, or build the Dataverse schema...") with an explicit trigger clause, matching level 3; level 2 lacks an explicit 'when'.	3 / 3
Trigger Term Quality	"set up the data model", "create database tables", and "build the Dataverse schema" are natural phrases a user would say, giving good coverage; it is not level 2 because several common user-facing variations are present rather than only one technical keyword.	3 / 3
Distinctiveness Conflict Risk	"Dataverse tables, columns, and relationships for a Power Pages site" carves a clear niche with distinct triggers unlikely to fire for other skills; it is not level 2 because the Power Pages + Dataverse schema scope is specific rather than broadly overlapping.	3 / 3
	Total	12 / 12 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
Commit: 55fa377

Reviewed: 5 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.