mcscatblog-new-post

Create a new blog post with branch, front matter, and asset folder

11 stars

Best use case

mcscatblog-new-post is best used when you need a repeatable AI agent workflow instead of a one-off prompt.

Create a new blog post with branch, front matter, and asset folder

Teams using mcscatblog-new-post should expect a more consistent output, faster repeated execution, less prompt rewriting.

When to use this skill

You want a reusable workflow that can be run more than once with consistent structure.

When not to use this skill

You only need a quick one-off answer and do not need a reusable workflow.
You cannot install or maintain the underlying files, dependencies, or repository context.

Installation

Claude Code / Cursor / Codex

$curl -o ~/.claude/skills/mcscatblog-new-post/SKILL.md --create-dirs "https://raw.githubusercontent.com/microsoft/mcscatblog/main/.claude/skills/mcscatblog-new-post/SKILL.md"

Manual Installation

Download SKILL.md from GitHub
Place it in .claude/skills/mcscatblog-new-post/SKILL.md inside your project
Restart your AI agent — it will auto-discover the skill

How mcscatblog-new-post Compares

Feature / Agent	mcscatblog-new-post	Standard Approach
Platform Support	Not specified	Limited / Varies
Context Awareness	High	Baseline
Installation Complexity	Unknown	N/A

Frequently Asked Questions

What does this skill do?

Create a new blog post with branch, front matter, and asset folder

Where can I find the source code?

You can find the source code on GitHub using the link provided at the top of the page.

SKILL.md Source

# Create a New Blog Post

Scaffold a new blog post with everything ready to write.

## Arguments

The argument should be a short description of the post topic, e.g. "Dataverse search for unauthenticated agents" or "WebChat middleware patterns". If not provided, ask.

## Steps

1. **Ask for details** (if not provided):
   - Post topic / working title
   - Author GitHub username (check `_data/authors.yml` — if not there, add them)

2. **Generate the slug** from the topic. Use lowercase, hyphens, no special characters. Keep it short but descriptive. Today's date for the prefix.

3. **Create a branch**: `post/<slug>` (e.g., `post/dataverse-search-unauthenticated`)

4. **Create the post file** at `_posts/YYYY-MM-DD-<slug>.md` with front matter:

```yaml
---
layout: post
title: "<Working Title>"
date: YYYY-MM-DD
categories: [copilot-studio, <second-category>]
tags: []
description: ""
author: <author-key>
image:
  path: /assets/posts/<slug>/header.png
  alt: ""
---

<!-- Write your post here -->
```

5. **Create the assets folder**: `assets/posts/<slug>/`

6. **Add author to `_data/authors.yml`** if they're not already there. Ask for their display name if needed.

7. **Report** the file path, branch name, and next steps:
   - Write the post in the markdown file
   - Add images to `assets/posts/<slug>/`
   - Preview with `/mcscatblog-local-server`
   - Review with `/mcscatblog-review-post <file>`
   - Submit with `/mcscatblog-submit-pr`

## Notes

- Do NOT set `published: false` — the post lives on a feature branch so there's no risk of it going live prematurely. Unpublished posts don't render on the local dev server, which makes previewing impossible.
- Leave tags empty — they should be chosen during review to maximize Chirpy "Further Reading" overlap
- Leave description empty — it should be written after the post content is finalized
- Categories: always include `copilot-studio` as the first category

Related Skills

We are still matching the closest adjacent skills for this page. In the meantime, continue through the full directory.