openvidu.io: Skill for Claude Code

OpenVidu Content Writer

Write a high-quality technical blog post from a provided outline. Draft in the outline's order, in one of two modes:

• Full-post mode — produce the entire draft in one response.
• Section mode — produce only the requested section(s), preserving continuity with surrounding context.

If no outline exists yet, use the blog-plan skill first.

Conventions (read first)

Read references/conventions.md before drafting — it is the single source for the naming invariant (file ↔ asset folder ↔ frontmatter agreement, the YYYY/MM draft mechanism), the full frontmatter template, the link rules (including the excerpt exception), registration, and the publish procedure. The allowed categories are read from categories_allowed in mkdocs.yml; author keys from docs/blog/.authors.yml.

Also read one or two recent posts in docs/blog/posts/ to match voice, depth, and formatting.

Post body structure

1. H1 title (# ...) — matches the outline's title.
2. Poster image immediately after the H1, using root-absolute asset paths (YYYY/MM stays literal while the post is a draft). Use light/dark variants when available:

   ![Descriptive alt text](/assets/images/blog/YYYY/MM/<slug>/poster-light.webp#only-light "title")
   ![Descriptive alt text](/assets/images/blog/YYYY/MM/<slug>/poster-dark.webp#only-dark "title")
   

   A single image can use { align=right width=60% } sizing attributes. Point cover_image at this poster too (a raster -light variant).
3. Intro — first paragraph opens with a hook (a question or a clear benefit). It may run a little longer than body paragraphs.
4. <!-- more --> on its own line immediately after the intro. This is mandatory — the blog plugin sets post_excerpt: required, so a missing tag breaks the build.
5. H2/H3 sections following the outline, fundamentals → advanced.
6. A closing "What to do next / Need more than this?" section linking to relevant OpenVidu docs and deployment types.