blog-post — Claude Code skill: what it does, how to install
Generates self-contained editorial blog posts and long-form articles in HTML based on design system tokens.
Apache-2.0 245 installs ★ 108,855 updated 2026-10-25
npx skills add nexu-io/open-design --skill blog-post -a claude-codeWhat blog-post does
This skill outputs a standalone HTML document formatted as an editorial article without external images or scripts. Styles remain inline. The layout includes a masthead, hero placeholder, author block, pull quote, and three related story cards. Content avoids placeholder text: the agent writes an actual article of at least 600 words across 4–6 H2 headings.
Formatting follows DESIGN.md tokens. Body prose is constrained to 680–720px with line lengths between 60–75 characters. Pull quotes use inline-start rules to flip cleanly in RTL layouts. Accent colors appear no more than twice across the entire page.
Without DESIGN.md in the workspace, the skill cannot resolve typography tokens.
What it helps with
- generate standalone long-form HTML articles with inline CSS
- draft full-length 600-word prototype articles without lorem ipsum
- format editorial layouts with pull quotes and RTL alignment
- build related story grids and author bio blocks
Example prompts for the agent
- Draft a long-form article about design tokens using the blog-post skill
- Generate an essay prototype in HTML with a masthead and pull quotes
- Create a marketing case study page following DESIGN.md
How to install blog-post
1Skills CLI (Vercel)
npx skills add nexu-io/open-design --skill blog-post -a claude-code2Manually: put the files in place
~/.claude/skills/blog-post/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/blog-post/
1Skills CLI (Vercel)
npx skills add nexu-io/open-design --skill blog-post -a codex2Manually: put the files in place
.agents/skills/blog-post/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add nexu-io/open-design --skill blog-post -a cursor2Manually: put the files in place
.cursor/skills/blog-post/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install nexu-io/open-design design-templates/blog-post/SKILL.md2Manually: put the files in place
.github/skills/blog-post/SKILL.md1Skills CLI (Vercel)
npx skills add nexu-io/open-design --skill blog-post -a gemini-cli2Platform CLI
gemini skills install https://github.com/nexu-io/open-design --path design-templates/blog-postManually: put the files in place
.devin/skills/blog-post/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add nexu-io/open-design --skill blog-post -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about blog-post
How do I install blog-post in Claude Code?
Run npx skills add nexu-io/open-design --skill blog-post -a claude-code. The skill definition will be placed at ~/.claude/skills/blog-post/SKILL.md.
What does the blog-post skill generate?
It produces a single HTML page with inline styles, a hero placeholder, an article body over 600 words, an author bio, and three related post cards.
Does the layout require external images?
No external assets are needed. Hero and figure placeholders rely on solid fills or gradients derived directly from the design system.
Source text
SKILL.md · Apache-2.0
---
name: blog-post
description: |
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".
triggers:
- "blog"
- "blog post"
- "article"
- "essay"
- "case study"
- "newsletter"
- "博客"
- "文章"
od:
mode: prototype
platform: desktop
scenario: marketing
preview:
type: html
entry: index.html
design_system:
requires: true
sections: [color, typography, layout, components]
craft:
requires: [typography, typography-hierarchy, typography-hierarchy-editorial, rtl-and-bidi]
---
# 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.
© nexu-io · Apache-2.0 · nexu-io/open-design