add-sample-data

Populates Dataverse tables with sample records for testing and demoing a Power Pages site. Use when the user wants to add sample data, seed data, generate test records, or insert demo data into their tables.

Quality

81%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

81%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.

A thorough, highly actionable multi-phase workflow with executable OData commands, explicit validation gates, and a clear progress checklist. The main weaknesses are redundant restatement of core principles across sections and a slightly nested reference chain.

Suggestions

Consolidate the Core Principles and Important Notes sections so "Respect insertion order", "Fail gracefully", and the TaskCreate guidance are stated once and referenced, rather than repeated across four locations.

Flatten the reference chain by inlining the essential auth/token-refresh notes from odata-common.md into odata-record-patterns.md, or have SKILL.md link directly to odata-common.md, to avoid the SKILL.md -> odata-record-patterns.md -> odata-common.md 2-level hop.

Render reference paths as markdown links (e.g. [dataverse-prerequisites.md](references/dataverse-prerequisites.md)) instead of bare code spans so navigation is explicit.

Dimension	Reasoning	Score
Conciseness	The body is action-oriented and avoids explaining concepts Claude already knows, but it repeats the same principles multiple times ("Respect insertion order" appears in Core Principles, Phase 3.3, Phase 5.3, and Important Notes; "Fail gracefully" and TaskCreate guidance are likewise restated), which is more than minor padding.	3 / 5
Actionability	Every phase gives copy-paste-ready `node "${PLUGIN_ROOT}/scripts/dataverse-request.js"` commands with concrete OData query strings, `--body` JSON payloads, and the `--include-headers` flag, covering the common cases (parent insert, child lookup binding, picklist options, count query).	5 / 5
Workflow Clarity	Six phases are explicitly sequenced with validation checkpoints (Phase 1 API-access verification, Phase 4.2 preview-approval gate, Phase 6 record-count verification), a defined fail-and-continue recovery behavior, and a Progress Tracking checklist table; validation is present so the batch-operation cap does not apply.	5 / 5
Progressive Disclosure	SKILL.md acts as a phased overview pointing to one-level-deep reference files with clearly signaled `${PLUGIN_ROOT}/references/` paths and the local `odata-record-patterns.md` exists; not a 5 because `odata-record-patterns.md` chains onward to `odata-common.md` (a 2-level reference chain) and most references are given as code paths rather than navigable links.	4 / 5
	Total	17 / 20 Passed

Description

82%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.

A well-formed description that clearly conveys purpose and trigger conditions in third person with strong natural-language triggers. Its only weakness is modest action specificity, since it describes one main activity rather than a list of distinct capabilities.

Dimension	Reasoning	Score
Specificity	Names the domain and one concrete action ("Populates Dataverse tables with sample records for testing and demoing a Power Pages site") but does not list multiple distinct actions, matching the 1-2 concrete-actions anchor rather than the comprehensive-coverage anchor.	3 / 5
Completeness	It clearly states what the skill does in the first sentence and gives an explicit "Use when the user wants to add sample data, seed data, generate test records, or insert demo data" trigger clause, satisfying both what and when with concrete triggers.	5 / 5
Trigger Term Quality	The "Use when" clause supplies several natural synonyms ("add sample data, seed data, generate test records, or insert demo data"), giving good keyword coverage; not a 5 because common variants like "dummy data", "mock data", or "fixtures" are absent.	4 / 5
Distinctiveness Conflict Risk	The Power Pages / Dataverse sample-data niche is specific with distinct triggers, making overlap with unrelated skills unlikely.	5 / 5
	Total	17 / 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/add-sample-data/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.