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.
88
87%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Quality
Discovery
89%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a well-crafted skill description that clearly identifies its niche (Dataverse/Power Pages sample data generation) and includes an explicit 'Use when' clause with strong trigger term coverage. The main weakness is that the capability description is somewhat narrow—it describes one core action rather than listing multiple specific sub-actions, though this may accurately reflect the skill's scope.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description names the domain (Dataverse tables, Power Pages) and the core action (populates with sample records), but it doesn't list multiple specific concrete actions—it's essentially one action (populating/seeding data) described in slightly different ways. | 2 / 3 |
Completeness | Clearly answers both 'what' (populates Dataverse tables with sample records for testing/demoing a Power Pages site) and 'when' (explicit 'Use when' clause listing multiple trigger scenarios). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms: 'sample data', 'seed data', 'test records', 'demo data', 'insert', 'Dataverse tables', 'Power Pages'. These are terms users would naturally use when requesting this functionality. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive—targets a very specific niche (Dataverse tables + Power Pages + sample data generation). Unlikely to conflict with other skills due to the specific technology stack mentioned. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
85%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-crafted skill with excellent actionability and workflow clarity — it provides a clear 6-phase process with concrete commands, proper dependency ordering, validation steps, and error handling. The progressive disclosure is strong with appropriate references to supporting files. The main weakness is moderate redundancy between the core principles, phase descriptions, and the 'Important Notes' section at the end, which repeats several guidelines already stated earlier.
Suggestions
Remove the 'Important Notes' section or consolidate it with the 'Core Principles' section at the top to eliminate redundancy — the insertion order, fail gracefully, and task tracking guidance are already stated in the phases themselves.
The picklist option querying appears in both Phase 4.1 (as a note) and Phase 5.2 (as a full command) — consolidate to Phase 5.2 only and just reference it from Phase 4.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is fairly well-structured but includes some redundancy — core principles are restated in the 'Important Notes' section at the bottom, and the progress tracking table duplicates what's already described in each phase. Some sections like the picklist query appear in both Phase 4 and Phase 5. However, it mostly avoids explaining concepts Claude already knows. | 2 / 3 |
Actionability | Every phase includes concrete, executable commands with the exact script paths and query parameters. OData queries, POST body formats, lookup syntax (`@odata.bind`), and response parsing instructions are all specific and copy-paste ready. The data generation guidance includes concrete examples for each column type. | 3 / 3 |
Workflow Clarity | The 6-phase workflow is clearly sequenced with explicit dependencies (parent before child insertion), validation checkpoints (Phase 6 verification queries), error handling strategy (log and continue, no rollback), token refresh guidance, and clearly marked decision points where user confirmation is required. The feedback loop for failures is well-defined. | 3 / 3 |
Progressive Disclosure | The skill appropriately references external files for detailed patterns (odata-record-patterns.md, dataverse-prerequisites.md, datamodel-manifest-schema.md, skill-tracking-reference.md) while keeping the main workflow and key commands inline. References are one level deep and clearly signaled with their purpose. | 3 / 3 |
Total | 11 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 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 | 9 / 11 Passed | |
- Repository
- microsoft/power-platform-skills
- Commit
48e49c4
- Reviewed
Table of Contents
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.