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.
70
87%
Does it follow best practices?
Impact
—
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 communicates its purpose and includes strong trigger terms. The 'Use when' clause provides excellent coverage of natural language variations users might employ. The only minor weakness is that the 'what' portion could list more specific concrete actions beyond the general 'populates tables with sample records.'
Suggestions
Consider adding more specific actions to the capability description, e.g., 'Populates Dataverse tables with sample records, configures record relationships, and generates realistic field values for testing and demoing a Power Pages site.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | It names the domain (Dataverse tables, Power Pages) and the core action (populates with sample records), but doesn't list multiple specific concrete actions beyond 'populates tables with sample records.' It could be more specific about what kinds of records, how many, or what configuration options exist. | 2 / 3 |
Completeness | Clearly answers both 'what' (populates Dataverse tables with sample records for testing and demoing a Power Pages site) and 'when' (explicit 'Use when' clause listing multiple trigger scenarios: add sample data, seed data, generate test records, insert demo data). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms: 'sample data', 'seed data', 'test records', 'demo data', 'insert', 'add', plus domain-specific terms like 'Dataverse tables' and 'Power Pages site'. These are terms users would naturally use when requesting this functionality. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with a clear niche: Dataverse tables + Power Pages + sample/test data population. The combination of platform-specific terms (Dataverse, Power Pages) and the specific action (seeding test data) makes it very unlikely to conflict with other 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-structured, highly actionable skill that clearly orchestrates a complex multi-phase data seeding workflow with proper dependency ordering, concrete OData commands, and explicit validation steps. Its main weakness is moderate redundancy between the core principles, important notes, and key decision points sections, which repeat the same guidance. Overall it's a strong skill that effectively balances comprehensiveness with navigability.
Suggestions
Consolidate the 'Core Principles', 'Important Notes / Throughout All Phases', and 'Key Decision Points' sections into a single reference block to eliminate repeated guidance about insertion order, fail-gracefully policy, and task tracking.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably efficient for its complexity but includes some redundancy — core principles are restated in the 'Important Notes' section, and the progress tracking table duplicates phase descriptions already covered in the body. Some sections could be tightened. | 2 / 3 |
Actionability | Every phase includes concrete, executable commands with actual script paths and OData query patterns. The insertion examples show exact JSON body syntax including @odata.bind for lookups, and the verification step uses specific query parameters. Fully copy-paste ready. | 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 policy (log and continue, no rollback), token refresh guidance, and clearly marked user decision points. The feedback loop for failures is well-defined. | 3 / 3 |
Progressive Disclosure | The skill references external files appropriately — dataverse-prerequisites.md, odata-record-patterns.md, datamodel-manifest-schema.md, skill-tracking-reference.md — keeping the main skill focused on workflow orchestration. References are one level deep and clearly signaled with context about what each contains. | 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
b4c46e9
- 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.