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

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

70%

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, highly actionable 6-phase workflow with concrete commands and validation checkpoints, but it is slightly redundant in its notes sections and critically references several bundle files and scripts that are not present in the bundle, breaking progressive disclosure.

Suggestions

Add the missing referenced files to the bundle (references/dataverse-prerequisites.md, references/datamodel-manifest-schema.md, references/skill-tracking-reference.md) and scripts (check-version.js, dataverse-request.js, verify-dataverse-access.js), or remove the references and inline the essential content.

Reduce redundancy: the 'Core Principles' and 'Important Notes / Throughout All Phases' sections repeat 'Respect insertion order', 'Fail gracefully', and token-refresh guidance already stated in the phases — consolidate into one location.

Verify the 'Refresh tokens every 20 records' note in Important Notes against the Phase 5.6 guidance (which defers token refresh to the script's internal 401 handling) to avoid conflicting instructions.

Dimension	Reasoning	Score
Conciseness	Quotes concrete commands and preview examples that assume competence, but the 'Important Notes / Throughout All Phases' and 'Core Principles' sections restate phase content already conveyed (e.g. 'Respect insertion order', 'Fail gracefully', 'Refresh tokens every 20 records'), so it is mostly efficient with some repetition that could be tightened; not level 3 due to this redundancy, not level 1 because it avoids explaining concepts Claude already knows.	2 / 3
Actionability	Quotes executable commands like 'node "${PLUGIN_ROOT}/scripts/dataverse-request.js" <envUrl> POST ... --include-headers' with real request bodies and @odata.bind syntax plus a preview markdown table — copy-paste ready and fully executable, matching the level-3 anchor; not level 2 because guidance is complete and concrete rather than pseudocode.	3 / 3
Workflow Clarity	Quotes a 6-phase sequenced workflow with explicit validation checkpoints (Phase 6 'query the record count', Phase 4 preview/approval gate before insert) and a fail-gracefully error loop for the batch insert — clear sequence with explicit validation and error recovery, matching the level-3 anchor; not level 2 because checkpoints and feedback handling are explicit.	3 / 3
Progressive Disclosure	The body references ${PLUGIN_ROOT}/references/dataverse-prerequisites.md, datamodel-manifest-schema.md, skill-tracking-reference.md and scripts/check-version.js, dataverse-request.js, verify-dataverse-access.js, but these files are MISSING from the bundle (only references/odata-record-patterns.md exists), so navigation is broken and references do not resolve; matching the level-1 'poor organization / broken references' anchor rather than level 2 where references at least exist.	1 / 3
	Total	9 / 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 specific, uses third person, and explicitly answers both what the skill does and when to use it with natural trigger terms. It is a strong, concise description with no fluff or over-claims.

Dimension	Reasoning	Score
Specificity	Quotes 'Populates Dataverse tables with sample records for testing and demoing a Power Pages site' — lists multiple concrete actions (populate, sample records, test, demo) tied to a specific domain, matching the level-3 anchor; not level 2 because it names more than just a domain and partial actions.	3 / 3
Completeness	Quotes both 'Populates Dataverse tables with sample records...' (what) and 'Use when the user wants to add sample data, seed data...' (when) — explicitly answers what AND when, matching the level-3 anchor; not level 2 because the when clause is explicit, not merely implied.	3 / 3
Trigger Term Quality	Quotes 'add sample data, seed data, generate test records, or insert demo data' — natural phrasings a user would actually say, matching the level-3 'good coverage of natural terms' anchor; not level 2 because common variations are well represented rather than partially covered.	3 / 3
Distinctiveness Conflict Risk	Quotes 'Dataverse tables... Power Pages site' with distinct seed/demo-data triggers — clear niche unlikely to conflict with other skills, matching the level-3 anchor; not level 2 because the domain and triggers are specific enough to avoid overlap.	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.