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.
Install with Tessl CLI
npx tessl i github:microsoft/power-platform-skills --skill add-sample-data88
Quality
87%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
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 description excels at trigger term coverage and completeness, providing extensive natural language phrases users would say and clearly specifying the Power Pages/Dataverse context. The main weakness is specificity - it describes the general purpose but doesn't detail the concrete actions performed (e.g., what types of sample data, how records are structured, which tables are supported).
Suggestions
Add specific concrete actions like 'Generates realistic contact records, account data, and custom entity samples' to improve specificity
Consider restructuring to lead with capabilities before the trigger terms for better readability (e.g., 'Populates Dataverse tables with sample records for testing Power Pages sites. Use when...')
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Dataverse tables, Power Pages) and the general action (populate with sample data), but doesn't list multiple specific concrete actions like what types of data, how many records, or specific table operations. | 2 / 3 |
Completeness | Explicitly answers both what (populate Dataverse tables with sample records for testing/demo) and when (lists extensive trigger phrases and use case of testing Power Pages sites). Has clear 'Use when' equivalent guidance. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms users would say: '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 all natural phrases users would actually use. | 3 / 3 |
Distinctiveness Conflict Risk | Very specific niche targeting Dataverse tables and Power Pages sites specifically. The combination of platform-specific terms (Dataverse, Power Pages) with the sample data context makes it unlikely to conflict with generic data or testing 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 and actionability. The 6-phase structure with explicit user confirmation points and validation checkpoints demonstrates strong process design. Minor improvements could be made by eliminating the duplicate progress tracking table and tightening some explanatory text, but overall the skill is production-ready.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is mostly efficient but includes some redundancy - the progress tracking table appears twice (in Phase 1 and Important Notes), and some explanations could be tightened. However, it appropriately assumes Claude's competence with PowerShell and OData concepts. | 2 / 3 |
Actionability | Provides fully executable PowerShell commands throughout, with specific OData endpoints, proper header syntax, and copy-paste ready code blocks. The @odata.bind syntax for lookups and token refresh patterns are concrete and immediately usable. | 3 / 3 |
Workflow Clarity | Excellent multi-step sequencing with 6 clearly defined phases, explicit validation checkpoints (verify prerequisites, user confirmation points), and proper error handling guidance (fail gracefully, log and continue). The insertion order logic with parent-before-child is well-articulated. | 3 / 3 |
Progressive Disclosure | Well-structured with clear phase organization and appropriate references to external files (dataverse-prerequisites.md, odata-record-patterns.md, datamodel-manifest-schema.md, skill-tracking-reference.md). References are one level deep and clearly signaled with full paths. | 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 | |
- 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.