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.
1---2name: blog-post-structure-pass3description: 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.4---56# Blog Post Structure Pass78Use 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.910## Core rules1112- Do not invent evidence, examples, client stories, dates, results, or quotes.13- Preserve the author's stance unless asked to change it.14- Improve the shape of the argument before polishing sentences.15- Keep the revised post suitable for the intended audience and channel.16- If important evidence is missing, mark it as a gap rather than filling it in.1718## Default post skeleton1920Use this skeleton as a guide, not a rigid template:21221. **Hook / tension** - Why this matters now.232. **Problem** - What people usually misunderstand or struggle with.243. **Reframe** - The more useful way to think about it.254. **Practical implications** - What changes in decisions, behaviour, governance, delivery, or operations.265. **Example or proof** - Evidence from supplied material.276. **Takeaway** - What the reader should do, question, or remember.2829## Workflow30311. Read the source post or draft.322. Identify the current thesis and intended audience.333. Diagnose structural issues: weak opening, unclear argument, repetition, missing transitions, unsupported claims, premature solutioning, or weak ending.344. Create a revised outline.355. Rewrite the post into the improved structure.366. Preserve factual claims from the source and avoid adding unsupported material.377. Provide a short change note only if useful.3839## Output format4041```markdown42# [Revised title]4344[Rewritten post]4546---4748## Change notes4950- [Only include important changes, assumptions, or evidence gaps.]51```5253If the user asks for the structure only, use:5455```markdown56## Recommended structure57581. [Section]592. [Section]603. [Section]6162## Rationale6364[Short explanation]65```666768## References6970This skill includes supporting reference material. Read the relevant reference file when the task needs additional structure, rubric detail, examples, or checklist support.7172- `references/post-structure-patterns.md` - use this when additional structure, examples, or checks are useful for the task.7374## Quality checklist7576Before responding, check:7778- The revised post has a clear thesis.79- The opening creates relevance quickly.80- The middle develops the argument rather than listing points.81- The ending lands the insight or next action.82- No unsupported facts have been added.83- The copy sounds natural and human.