mcpbeat Sign in

Blog Post Structure Pass Agent Skill

Use this skill when the user asks to restructure, reorganise, improve, rewrite, tighten, or strengthen a blog post, article, newsletter, essay, or thought-leadership draft.

673 tokens
context cost
SKILL.md, read when the skill is used
3
files
plus reference files
0
copies elsewhere
how many repositories repackaged it
107 d ago
last touched
this folder, not the whole repository

Install

one command, takes just this skill from the repository
npx skills add https://github.com/microsoft/cat-agent-skills --skill blog-post-structure-pass

What comes with it

1 447 bytes besides the instruction
metadata.json
references/post-structure-patterns.md

The instruction itself

7 sections, as written by the author

Blog Post Structure Pass

Use this skill to improve the structure, argument, flow, and readability of a blog post while preserving the source facts and the author's intended point of view.

Core rules

  • Do not invent evidence, examples, client stories, dates, results, or quotes.
  • Preserve the author's stance unless asked to change it.
  • Improve the shape of the argument before polishing sentences.
  • Keep the revised post suitable for the intended audience and channel.
  • If important evidence is missing, mark it as a gap rather than filling it in.

Default post skeleton

Use this skeleton as a guide, not a rigid template:

  • Hook / tension - Why this matters now.
  • Problem - What people usually misunderstand or struggle with.
  • Reframe - The more useful way to think about it.
  • Practical implications - What changes in decisions, behaviour, governance, delivery, or operations.
  • Example or proof - Evidence from supplied material.
  • Takeaway - What the reader should do, question, or remember.

Workflow

  • Read the source post or draft.
  • Identify the current thesis and intended audience.
  • Diagnose structural issues: weak opening, unclear argument, repetition, missing transitions, unsupported claims, premature solutioning, or weak ending.
  • Create a revised outline.
  • Rewrite the post into the improved structure.
  • Preserve factual claims from the source and avoid adding unsupported material.
  • Provide a short change note only if useful.

Output format

# [Revised title]

[Rewritten post]

---

## Change notes

- [Only include important changes, assumptions, or evidence gaps.]

If the user asks for the structure only, use:

## Recommended structure

1. [Section]
2. [Section]
3. [Section]

## Rationale

[Short explanation]

References

This skill includes supporting reference material. Read the relevant reference file when the task needs additional structure, rubric detail, examples, or checklist support.

  • references/post-structure-patterns.md - use this when additional structure, examples, or checks are useful for the task.

Quality checklist

Before responding, check:

  • The revised post has a clear thesis.
  • The opening creates relevance quickly.
  • The middle develops the argument rather than listing points.
  • The ending lands the insight or next action.
  • No unsupported facts have been added.
  • The copy sounds natural and human.

Other skills for the same job

different authors, same section of the catalogue
Doc Coauthoring
by anthropics
vendor ×13

Guide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.

4k tokens
Test Driven Development
by w95
×9

Use when implementing any feature or bugfix, before writing implementation code

2.5k tokens
Changelog Generator
by frostant
×9

Automatically creates user-facing changelogs from git commits by analyzing commit history, categorizing changes, and transforming technical commits into clear, customer-friendly release notes. Turns hours of manual changelog writing into minutes of automated generation.

774 tokens
Writing Plans
by ZhanlinCui
×6

Use when you have a spec or requirements for a multi-step task, before touching code

816 tokens
Writing Skills
by ZhanlinCui
×6

Use when creating new skills, editing existing skills, or verifying skills work before deployment

5.6k tokens scripts
Crafting Effective Readmes
by softaworks
×4

Use when writing or improving README files. Not all READMEs are the same — provides templates and guidance matched to your audience and project type.

669 tokens
Writing Hookify Rules
by anthropics
vendor ×3

This skill should be used when the user asks to "create a hookify rule", "write a hook rule", "configure hookify", "add a hookify rule", or needs guidance on hookify rule syntax and patterns.

2.1k tokens
Humanizer
by softaworks
×3

| Remove signs of AI-generated writing from text. Use when editing or reviewing text to make it sound more natural and human-written. Based on Wikipedia's inflated symbolism, promotional language, superficial -ing analyses, vague attributions, em dash overuse, rule of three, AI vocabulary words, negative parallelisms, and excessive conjunctive phrases.

4.5k tokens

How to use it

Copy the folder

Take microsoft/blog-post-structure-pass from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.