CO

copilot-studio-sample-review

Automates the review process for Copilot Studio samples in the pnp repository.

Install

mkdir -p .claude/skills/copilot-studio-sample-review && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/17907" && unzip -o skill.zip -d .claude/skills/copilot-studio-sample-review && rm skill.zip

Installs to .claude/skills/copilot-studio-sample-review

Activation

This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.

Review PRs for Microsoft Copilot Studio samples (mcs-* folders) in pnp/copilot-pro-dev-samples.
95 charsno explicit “when” trigger
Beginner

Key capabilities

  • Verify sample folder starts with mcs-
  • Check for required top-level files/folders
  • Ensure assets/sample.json includes correct sample folder references
  • Request changes if packaged .zip exports are committed

How it works

The skill checks a Copilot Studio sample PR against repository guidelines for folder structure, file presence, and metadata consistency.

Inputs & outputs

You give it
A pull request for a Microsoft Copilot Studio sample
You get back
A GitHub review with comments or an approval/request for changes

When to use copilot-studio-sample-review

  • Review a Copilot Studio sample PR
  • Check sample folder structure
  • Validate sample metadata

About this skill

Copilot Studio Sample Review

Review Copilot Studio sample PRs (folders starting with mcs-) for compliance with repo guidelines. Use when a request asks to review an mcs-* sample PR (e.g., "review PR" or "review this sample").

Workflow

  1. Checkout PR: gh pr checkout <number>
  2. Verify sample folder starts with mcs-
  3. Run checks below, collecting comments (file, line, issue)
  4. Submit all comments in single API call (GitHub limitation)

Checks

1. Folder and file structure

  • Sample is under samples/mcs-*
  • Required top-level files/folders are present: README.md, assets/, src/
  • assets/sample.json exists and includes correct sample folder references

2. No packaged exports

  • Request changes if any packaged .zip exports are committed under samples/mcs-* (e.g., samples/mcs-example/export.zip). Extracted source files are required, whether the contributor used pac solution clone or the VS Code clone method.
  • Copilot Studio exports must be committed as extracted source files only

3. README and template alignment

  • README is based on /templates/mcs-copilot-studio/README.md
  • Setup steps include one of the supported contributor flows:
    • Solution export via Power Platform CLI (pac solution clone)
    • Copilot Studio Visual Studio Code clone method

4. Metadata consistency

  • assets/sample.json name uses pnp-copilot-pro-dev-<sample-folder>
  • url and downloadUrl target the correct samples/mcs-* path
  • Author information and thumbnail paths match repository conventions

Submitting Reviews

GitHub API does not support adding comments to a review after it has been created. Collect all comments first and submit them in one API call.

Get commit SHA:

gh pr view <PR> --json headRefOid

Create review.json:

{
  "commit_id": "<sha>",
  "event": "<REQUEST_CHANGES|COMMENT|APPROVE>",
  "body": "Summary message",
  "comments": [
    {"path": "file/path", "line": 10, "body": "Issue description"}
  ]
}

Use the review event type based on findings:

  • REQUEST_CHANGES: blocking issues (e.g., .zip files in samples/mcs-*/, missing required mcs-* structure, or incorrect sample metadata paths)
  • COMMENT: non-blocking feedback (e.g., small README wording/template improvements)
  • APPROVE: checks pass

Submit:

gh api repos/pnp/copilot-pro-dev-samples/pulls/<PR>/reviews --method POST --input review.json

When not to use it

  • When reviewing PRs for samples not starting with 'mcs-'

Limitations

  • GitHub API does not support adding comments to a review after it has been created
  • Copilot Studio exports must be committed as extracted source files only

How it compares

This skill automates the review process for Copilot Studio samples, ensuring compliance with specific repository guidelines.

Compared to similar skills

copilot-studio-sample-review side by side with the closest alternatives in the catalog.

SkillInstallsUpdatedSafetyDifficulty
copilot-studio-sample-review (this skill)01moReviewBeginner
deepwiki-rs259moReviewIntermediate
python-code-style95moReviewIntermediate
code-review-excellence194moNo flagsIntermediate

Try saying

Example prompts that trigger this skill in your AI assistant.

You might also like

deepwiki-rs

sopaco

AI-powered Rust documentation generation engine for comprehensive codebase analysis, C4 architecture diagrams, and automated technical documentation. Use when Claude needs to analyze source code, understand software architecture, generate technical specs, or create professional documentation from any programming language.

25170

python-code-style

wshobson

Python code style, linting, formatting, naming conventions, and documentation standards. Use when writing new code, reviewing style, configuring linters, writing docstrings, or establishing project standards.

971

code-review-excellence

wshobson

Master effective code review practices to provide constructive feedback, catch bugs early, and foster knowledge sharing while maintaining team morale. Use when reviewing pull requests, establishing review standards, or mentoring developers.

1958

code-walk-thru

pchalasani

Use this when user wants you to walk through (code or text) files in a EDITOR to either explain how some code works, or to show the user what changes you made, etc. You would typically use this repeatedly to show the user your changes or code files one by one, sometimes with specific line-numbers. This way the user is easily able to follow along in their favorite EDITOR as you point at various files possibly at specific line numbers within those files.

670

cookbook-audit

anthropics

Audit an Anthropic Cookbook notebook based on a rubric. Use whenever a notebook review or audit is requested.

568

schema-markup

davila7

When the user wants to add, fix, or optimize schema markup and structured data on their site. Also use when the user mentions "schema markup," "structured data," "JSON-LD," "rich snippets," "schema.org," "FAQ schema," "product schema," "review schema," or "breadcrumb schema." For broader SEO issues, see seo-audit.

1042

Search skills

Search the agent skills registry