add-sample-data
This skill should be used when the user asks to "add sample data", "populate tables", "seed data", "add test records", "generate sample records", "insert demo data", "fill tables with data", "create test data", or wants to populate their Dataverse tables with sample records so they can test and demo their Power Pages site.
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.
The description excels at trigger term coverage and distinctiveness, with an extensive list of natural phrases users would say and a clear technology niche (Dataverse/Power Pages). Its main weakness is that the 'what' portion is somewhat thin—it describes the general goal (populate tables with sample data) but doesn't enumerate specific capabilities like data types supported, number of records, or related actions. The description also uses passive/imperative voice rather than third person, though this is a minor issue.
Suggestions
Add more specific concrete actions beyond 'populate tables', such as 'Generates realistic sample records across related Dataverse tables, handles lookups and relationships, and creates configurable volumes of test data.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description mentions populating Dataverse tables with sample records for testing/demoing Power Pages sites, which names the domain and a general action, but doesn't list multiple specific concrete actions beyond 'populate tables with sample data'. | 2 / 3 |
Completeness | Clearly answers both 'what' (populate Dataverse tables with sample records for testing/demoing Power Pages sites) and 'when' (explicit list of trigger phrases and use cases). The 'Use when' guidance is effectively provided through the opening clause. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms: 'add sample data', 'populate tables', 'seed data', 'add test records', 'generate sample records', 'insert demo data', 'fill tables with data', 'create test data'. These are phrases users would naturally say. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive due to the specific technology stack (Dataverse tables, Power Pages) and the narrow use case (sample/test data population). Unlikely to conflict with generic data generation or other database skills. | 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. The 6-phase structure with explicit validation, error handling, and user decision points makes it highly deterministic. The main weakness is moderate verbosity — some content is repeated between core principles and the 'Important Notes' section, and the progress tracking table could be more concise.
Suggestions
Consolidate the 'Core Principles' and 'Important Notes / Throughout All Phases' sections to eliminate redundancy (insertion order, fail gracefully, and task tracking are stated twice).
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is fairly well-structured but includes some redundancy — core principles are restated in 'Important Notes', the progress tracking table is somewhat duplicative, and some explanations could be tighter. However, it mostly avoids explaining concepts Claude already knows. | 2 / 3 |
Actionability | Every phase includes concrete, executable commands with specific scripts, flags, and API patterns. The OData queries, PowerShell commands, and JSON body examples are copy-paste ready with clear placeholders for dynamic values. | 3 / 3 |
Workflow Clarity | The 6-phase workflow is clearly sequenced with explicit outputs per phase, validation steps (Phase 6 verification), error handling guidance (fail gracefully, continue on failure), token refresh checkpoints, and clear decision points where user confirmation is required. | 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 self-contained. References are one level deep and clearly signaled. | 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
66a61c6
- 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.