Source profileQuality 73/100

nexu-io/open-design/design-templates/blog-post/SKILL.md

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".

Source repository stars
82,073
Declared platforms
0
Static risk flags
0
Last source update
2026-07-28
Source checked
2026-07-28

Decision brief

What it does—and where it fits

Produce a single long-form article page — editorial layout, no chrome.

Best for

  • Use when the brief asks for "blog", "article", "post", "essay", or "case study".

Not for

  • Tasks that require unconfirmed production actions or broad system permissions.
  • Environments where the pinned source and install steps cannot be inspected.

Compatibility matrix

Platform support, with evidence labels

PlatformStatusEvidenceWhat to check
CodexNot declaredNo explicit evidencePortability before use
Claude CodeNot declaredNo explicit evidencePortability before use
CursorNot declaredNo explicit evidencePortability before use
Gemini CLINot declaredNo explicit evidencePortability before use
Open the compatibility checker

Installation

Inspect first. Install second.

The source command is displayed only when detected. A safe inspection prompt is always available so your agent can explain every action before execution.

Source-detected install commandSource
npx skills add https://github.com/nexu-io/open-design --skill "design-templates/blog-post"
Safe inspection promptEditorial

Inspect the Agent Skill "blog-post" from https://github.com/nexu-io/open-design/blob/89d6d4ef21baf80f871595abdf6f7de6e941dd44/design-templates/blog-post/SKILL.md at commit 89d6d4ef21baf80f871595abdf6f7de6e941dd44. List every install step, command, network request, credential, file read/write, external action, and rollback step. Explain whether it fits my task. Do not install or execute anything until I approve.

Workflow

What the source asks the agent to do

  1. 01

    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…

    Read the active DESIGN.md (injected above). Lean into the typographyPick the topic from the brief and write a real article — at least 600Sections, in order:
  2. 02

    Output contract

    One sentence before the artifact, nothing after.

    One sentence before the artifact, nothing after.

Permission review

Static risk signals and limitations

No configured static risk pattern was detected

This is not proof of safety. Runtime behavior, indirect dependencies, and hidden external systems are outside the static scan.

Evidence record

Why each signal appears

EvidenceSourceComputedTestedEditorial
SignalValueEvidence typeMeaning
Quality score73/100ComputedDocumentation, specificity, maintenance, and trust rules
Repository stars82,073SourceRepository attention, not individual Skill quality
Compatibility0 platformsSourceDeclared in the catalog source record
Usage guideautomated source guideEditorialGenerated or reviewed according to the visible evidence level

Pinned source

Provenance and original SKILL.md

Repository
nexu-io/open-design
Skill path
design-templates/blog-post/SKILL.md
Commit
89d6d4ef21baf80f871595abdf6f7de6e941dd44
License
Apache-2.0
Collected
2026-07-28
Default branch
main
View the original SKILL.md

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.

Alternatives

Compare before choosing