skills.rest
microsoft
microsoftOFFICIAL
Explore all skills by this author →
Website𝕏@OpenAtMicrosoftGitHub

mcscatblog-review-post

Review Microsoft Copilot Studio CAT blog post pull requests for content and front matter.

18|10|Updated Sep 21, 2025
Search Tags:#markdown#publishing#pull request#jekyll#content editing#blog review
One-click install
npx skills add https://github.com/microsoft/mcscatblog --skill mcscatblog-review-post
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: mcscatblog-review-post
Source: https://github.com/microsoft/mcscatblog/tree/main/.claude/skills/mcscatblog-review-post
Command: npx skills add https://github.com/microsoft/mcscatblog --skill mcscatblog-review-post

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill streamlines the end-to-end review of Microsoft Copilot Studio CAT blog post pull requests, helping you assess quality, accuracy, terminology, and publishing readiness without missing important checks.

Core Features & Use Cases

  • PR checkout and identification: Finds the target pull request, checks out the branch, and locates the new or modified post in _posts/.
  • Content review: Evaluates the post for reader clarity, structure, technical accuracy, canonical Copilot Studio terminology, front matter correctness, and image handling.
  • Fix-and-publish workflow: Applies approved edits, commits and pushes changes, comments on the PR, merges the PR, verifies the build, and confirms the live production page.

Quick Start

Review the specified blog post pull request, identify the top issues ranked by impact, and prepare only the approved fixes for application.

Frequently Asked Questions about mcscatblog-review-post

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

FAQPage Schema
How do I review a markdown blog post pull request for terminology and front matter accuracy?▼

To review a markdown blog post pull request, check out the PR branch, inspect the post in `_posts/`, and validate content quality, canonical Copilot Studio terminology, front matter correctness, and image handling.

What's the best way to automate blog post publishing from a Jekyll pull request?▼

Automate blog post publishing from a Jekyll pull request by applying approved edits, committing and pushing changes, commenting on the PR, merging it, verifying the build, and confirming the live production page.

Do I need GitHub CLI and a local Jekyll environment to review blog post pull requests?▼

Yes, you need GitHub CLI access, a local Jekyll-based preview environment, and repository-specific review instructions to complete the blog post pull request review and publishing workflow safely.

Can I check and fix image handling issues in markdown blog posts before merging?▼

Yes, the blog post review process evaluates image handling and structural issues, allowing you to apply approved edits and fixes to the markdown post before committing and merging the pull request.

How does a fix-and-publish workflow handle content editing and pull request merging?▼

A fix-and-publish workflow handles content editing by applying approved edits to the markdown post, committing and pushing the changes, commenting on the PR, merging it, and verifying the live production page.

What content quality checks are applied when reviewing markdown publishing pull requests?▼

Content quality checks for markdown publishing pull requests evaluate reader clarity, structure, technical accuracy, canonical terminology, front matter correctness, and image handling before publishing.

Related Skills

Explore More Content & Communication Skills→
tile-aitile-ai
346

tilelang-github-operations

Install GitHub CLI and create pull requests via authenticated workflows.

Official
Advanced
HomericIntelligenceHomericIntelligence
18

pr-cleanup

Squash commits, rebase onto main, and verify CI status for GitHub pull requests.

Official
Intermediate
notquenotque
415

pre-publish-checker

Validate Hugo post front matter, links, images, and draft status.

Community
Advanced
georgekhananaevgeorgekhananaev
27

md

Enforce consistent Markdown syntax across documentation and README files.

Community
Basic