Blog Post
A long-form article / blog post — masthead, hero image placeholder, article body with figures and pull quotes, author byline, related posts. Use when the brief asks for "blog", "article", "post", "essay", or "case study".
Get the complete skill folder, including its scripts and reference files.
When to use this skill
Use Blog Post when an AI agent needs a reusable SKILL.md workflow for this job: A long-form article / blog post — masthead, hero image placeholder, article body with figures and pull quotes, author byline, related posts. Use when the brief asks for "blog", "article", "post", "essay", or "case study".
When not to use it
Skip Blog Post when the task is outside the writing category, or when a more specific skill in this directory already covers the same workflow with clearer triggers.
How to install
Where will you use it?
mkdir -p ~/.claude/skills/blog-post # Save SKILL.md to ~/.claude/skills/blog-post/SKILL.md
- Claude Code personal install: place the skill and its bundled files at ~/.claude/skills/blog-post/SKILL.md. For a shared project, commit the folder at .claude/skills/blog-post/ instead.
- Current Claude Code detects SKILL.md changes in watched directories during the session. If you just created a top-level skills directory, run /reload-skills. Check that the skill is listed before testing its trigger.
- For Claude chat or Cowork in the Desktop app, manage uploaded skills in Customize > Skills; copying files into a local Claude Code folder is not a Desktop install. Other agents may use different install locations.
Full install guide for Claude, Cursor, and Codex →
Try a starter prompt
After installing the skill, paste this starter prompt into your agent to verify it triggers on a small task.
Use the Blog Post skill for this task: Read the active DESIGN.md (injected above). Lean into the typography. Confirm any required inputs or files before making changes.
What supports this recommendation?
74/100 provisional content score. This measures documentation, practical detail and source signals. It is not a measured task success rate or a security certification.
- Documentation
- 82/100
- Practical detail
- 74/100
- Source evidence
- 63/100
- Source signals
- 72/100
Model compatibility evidence
- claudeuntested
No model-specific signal or recorded compatibility test was found.
- chatgptuntested
No model-specific signal or recorded compatibility test was found.
- geminiuntested
No model-specific signal or recorded compatibility test was found.
- copilotuntested
No model-specific signal or recorded compatibility test was found.
- llamauntested
No model-specific signal or recorded compatibility test was found.
- perplexityuntested
No model-specific signal or recorded compatibility test was found.
- mistraluntested
No model-specific signal or recorded compatibility test was found.
- grokuntested
No model-specific signal or recorded compatibility test was found.
Inferred compatibility is based on content signals. Check the app, its available tools and setup requirements before running a skill.
What this skill does
# Blog Post Skill
Produce a single long-form article page — editorial layout, no chrome.
## Workflow
1. **Read the active DESIGN.md** (injected above). Lean into the typography tokens — long-form is 70% type, 20% image, 10% chrome. 2. **Pick the topic** from the brief and write a real article — at least 600 words across 4–6 H2 sections. No lorem ipsum. 3. **Sections**, in order: - **Masthead** — small wordmark + 4–6 nav links, plain. - **Article header** — category eyebrow, headline (display token, large), deck (1–2 sentence subhead), author name + role + date. - **Hero image** — a 16:9 placeholder block using a DS-tinted gradient or solid fill (no external images). Add a 1-line caption underneath. - **Body** — alternating prose paragraphs with at least: - 1 pull quote (large display type, accent rule on the inline-start edge so the layout flips correctly under `dir="rtl"`). - 1 figure (image placeholder + caption). - 1 list (numbered or bulleted). - 1 inline blockquote. - **Author footer** — author avatar (initials in a circle), bio paragraph. - **Related** — 3 cards linking to other posts. Each card: tiny image block, title, 1-line excerpt, date. 4. **Write** a single HTML document: - `<!doctype html>` through `</html>`, CSS inline. - Article body uses the DS body font, centered, max-width per DS layout rule (typically 680–720px). - Drop caps (`first-letter`) only if the DS mood is editorial / serif — skip on tech-y DSes. - `data-od-id` on the headline, hero, body, pull quote, related grid. 5. **Self-check**: - Type hierarchy is unambiguous — H1 is clearly the headline; H2s are section dividers; pull quotes do not compete with H1. - Line length 60–75 chars for body prose. - Accent appears at most twice (eyebrow + pull-quote rule, or one link). - The page reads like a magazine, not a marketing landing.
## Output contract
Emit between `<artifact>` tags:
``` <artifact identifier="post-slug" type="text/html" title="Article Title"> <!doctype html> <html>...</html> </artifact> ```
One sentence before the artifact, nothing after.
Intended uses
- Read the active DESIGN.md (injected above). Lean into the typography
- Pick the topic from the brief and write a real article — at least 600
- Sections, in order:
- Masthead — small wordmark + 4–6 nav links, plain.
- Article header — category eyebrow, headline (display token, large),
- Hero image — a 16:9 placeholder block using a DS-tinted gradient or
- Body — alternating prose paragraphs with at least:
- 1 pull quote (large display type, accent rule on the inline-start edge so the layout flips correctly under dir="rtl").
- 1 figure (image placeholder + caption).
- 1 list (numbered or bulleted).
- 1 inline blockquote.
- Author footer — author avatar (initials in a circle), bio paragraph.
- Related — 3 cards linking to other posts. Each card: tiny image
- Write a single HTML document:
- <!doctype html> through </html>, CSS inline.
- Article body uses the DS body font, centered, max-width per DS layout
- Drop caps (first-letter) only if the DS mood is editorial / serif —
- data-od-id on the headline, hero, body, pull quote, related grid.
- Self-check:
- Type hierarchy is unambiguous — H1 is clearly the headline; H2s are
Implementation notes
- Review the source instructions and adapt inputs before running the workflow.
Try it, then tell us how it went
A copied prompt does not tell us whether the task worked. Report your result after checking the output. We collect your tool and outcome, never your files or prompt.