validate-sample-topic

Validate modified Copilot Studio sample topics against project conventions.

25|8|Updated Apr 8, 2026
One-click install
npx skills add https://github.com/microsoft/Employee-Self-Service-Agent-Developer-Kit --skill validate-sample-topic
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: validate-sample-topic
Source: https://github.com/microsoft/Employee-Self-Service-Agent-Developer-Kit/tree/main/.github/agents/skills/validate-sample-topic
Command: npx skills add https://github.com/microsoft/Employee-Self-Service-Agent-Developer-Kit --skill validate-sample-topic

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

When creating or updating Employee Self-Service agent sample topics, it is easy to overlook required formatting, naming, and scope conventions, leading to failed pull requests, wasted review time, and broken CI pipelines. This skill automates all required validation checks to catch issues before you submit a PR.

Core Features & Use Cases

  • Comprehensive Convention Validation: Checks YAML well-formedness, AdaptiveDialog kind, XML formatting, filename and folder naming rules, diff scope, and secret/internal URL leaks for all changed sample files.
  • Pre-PR Gate: Stops the workflow immediately if any check fails, preventing you from opening a non-compliant PR and reducing unnecessary review overhead.
  • Use Case: After modifying a sample topic for the ESS agent, run this skill to confirm all project requirements are met before submitting your changes for review.

Quick Start

Run the validate-sample-topic skill after making changes to a sample topic to receive a full validation summary of all required checks.

Frequently Asked Questions about validate-sample-topic

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I validate Copilot Studio sample topics before opening a PR?

To validate Copilot Studio sample topics before a PR, run a pre-check that enforces YAML/XML parsing, naming conventions, diff scope, and sensitive data detection to stop non-compliant changes early.

What formatting rules are required for Employee Self-Service agent sample files?

Required formatting rules for Employee Self-Service agent samples include YAML well-formedness, valid AdaptiveDialog kinds, proper XML formatting, and strict filename and folder naming conventions.

Why do my Copilot Studio sample topic pull requests keep failing CI checks?

Pull requests fail CI checks because modified sample topics often violate project-specific scope conventions, contain secret leaks, or have malformed YAML/XML, which can be caught using pre-PR validation.

Can I check for sensitive data leaks in ESS agent sample topics?

Yes, you can check for sensitive data leaks in ESS agent sample topics by running a validation workflow that detects secret and internal URL leaks before you submit your changes for review.

What is the best way to enforce diff boundaries in Copilot Studio topics?

The best way to enforce diff boundaries in Copilot Studio topics is to apply an automated validation check that ensures modified sample files stay within the required project scope before submission.