CtrlK
BlogDocsLog inGet started
Tessl Logo

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

Quality

87%

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

Quality

Content

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 for a complex multi-phase data seeding workflow. It provides concrete commands, clear sequencing with validation, and appropriate progressive disclosure to external references. The main weakness is moderate redundancy between the core principles, inline instructions, and the 'Important Notes' recap section at the bottom, which could be consolidated to save tokens.

Suggestions

Remove the 'Important Notes' section at the bottom or merge it into the core principles, as it largely repeats guidance already embedded in the phase instructions (insertion order, fail gracefully, task tracking).

DimensionReasoningScore

Conciseness

The skill is fairly long (~250 lines) but most content is necessary for a complex multi-phase workflow. Some redundancy exists — core principles are restated in 'Important Notes' at the bottom, and the 'Key Decision Points' section repeats what's already clear from the gate annotations. The gate comment blocks add verbosity but serve a structural purpose.

2 / 3

Actionability

Every phase includes concrete, executable commands with proper argument placeholders. OData query patterns, script invocations, JSON body syntax, and @odata.bind lookup syntax are all copy-paste ready. The data generation guidance includes specific examples for each column type (e.g., 'Email' -> 'jane.doe@example.com').

3 / 3

Workflow Clarity

The 6-phase workflow is clearly sequenced with explicit dependencies (parent before child insertion order), validation checkpoints (Phase 6 verification queries), user confirmation gates at key decision points, and graceful error handling (log and continue, never rollback). The progress tracking table provides a clear task list upfront. Token refresh is addressed for long-running operations.

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 with full paths. The main file serves as a clear orchestration overview.

3 / 3

Total

11

/

12

Passed

Description

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 provides strong trigger terms for skill selection. The 'Use when' clause is comprehensive with good synonym coverage. The only minor weakness is that the 'what' portion could list more specific actions beyond the general 'populates tables with sample records.'

DimensionReasoningScore

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 beyond 'populates tables with sample records.' It could be more specific about what kinds of records, how many, or what formats.

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 like adding sample data, seeding data, generating test records, or inserting demo data).

3 / 3

Trigger Term Quality

Excellent coverage of natural trigger terms: 'sample data', 'seed data', 'test records', 'demo data', 'insert', 'add', 'generate', 'Dataverse tables', 'Power Pages'. 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 purpose (sample/demo data) makes it very unlikely to conflict with other skills.

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.

Validation9 / 11 Passed

Validation for skill structure

CriteriaDescriptionResult

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
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.