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', e.g., 'Generates realistic sample records for Dataverse tables, supports multiple entity types, creates related records with proper lookups, and configures appropriate data volumes for Power Pages testing and demos.'
| 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 workflow clarity, strong actionability through concrete commands and patterns, and good progressive disclosure via external references. Its main weakness is moderate redundancy — the 'Important Notes' section largely restates principles and decision points already covered in the phase descriptions, and the progress tracking table duplicates phase summaries. Overall it's a high-quality, production-ready skill.
Suggestions
Remove or consolidate the 'Important Notes' section — the core principles, key decision points, and progress tracking table duplicate content already present in the phase descriptions and the top-level 'Core Principles' section.
| 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 phase descriptions already given. Some sections like 'Key Decision Points' repeat what's already stated in each phase's actions. However, it avoids explaining basic concepts Claude already knows. | 2 / 3 |
Actionability | The skill provides concrete, executable commands throughout — specific `node` script invocations with actual parameters, PowerShell commands, OData query patterns with proper syntax, and exact JSON body formats for POST requests. The `@odata.bind` lookup syntax and `--include-headers` flag for capturing GUIDs are specific, copy-paste-ready details. | 3 / 3 |
Workflow Clarity | The 6-phase workflow is clearly sequenced with explicit dependencies (parent before child insertion), validation checkpoints (Phase 6 verification of record counts), error handling strategy (log and continue, never rollback), and user confirmation gates at phases 2, 3, and 6. The insertion order determination in Phase 3.3 is a well-defined feedback loop for dependency resolution. | 3 / 3 |
Progressive Disclosure | The skill appropriately references external files for detailed content — `dataverse-prerequisites.md`, `datamodel-manifest-schema.md`, `odata-record-patterns.md`, and `skill-tracking-reference.md` — all one level deep with clear signals about what each reference contains. The main skill stays at the orchestration level while delegating implementation details to reference files. | 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
1132a35
- 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.