Borrowing it
Nothing to install: this file belongs to OpenVidu/openvidu.io. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/OpenVidu/openvidu.io/main/.claude/skills/blog-plan/SKILL.mdgit clone --depth 1 https://github.com/OpenVidu/openvidu.ioWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/openvidu/openvidu.io/blog-plan)<a href="https://agentmods.dev/skills/openvidu/openvidu.io/blog-plan"><img src="https://agentmods.dev/badge/skills/openvidu/openvidu.io/blog-plan/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/openvidu/openvidu.io/blog-plan"><img src="https://agentmods.dev/badge/skills/openvidu/openvidu.io/blog-plan.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00084 | $0.01254 |
| Opus 5 | $0.00042 | $0.00627 |
| Sonnet 5 | $0.00017 | $0.00251 |
| Haiku 4.5 | $0.00008 | $0.00125 |
Grade A, and why
blog-plan scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 10d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 89 lines — stays where its author put it; the contents beside it link to each section on GitHub.
OpenVidu Blog Planner
Convert a raw technical idea into a detailed, SEO-optimized blog post outline. You produce the plan, not the prose.
Scope
- DO produce an SEO brief, an article type, one H1 title, an intro plan, a full H2/H3 outline with talking points, and one CTA.
- DO NOT write the full article. That is the
blog-writeskill's job. - Hand off the finished outline to
blog-write; the reviewer (blog-review) will audit the result.
Gather inputs first
Extract these from the user's request. If any are missing, infer them and state your assumption rather than blocking:
- Primary keyword (the phrase the post should rank for)
- Secondary keywords (2–5 related phrases)
- Search intent (informational, comparison, how-to, decision)
- Target audience (almost always technical developers / DevOps / CTOs evaluating WebRTC)
- Buying-journey stage: Awareness, Consideration, or Decision
Repo conventions this outline must respect
The naming, frontmatter, and link conventions live in
../blog-write/references/conventions.md — read it
before finalizing. The outline should already choose:
- A slug (kebab-case, keyword-bearing, e.g.
secure-home-video-conferencing) — it becomes the filename (<slug>.md), the asset-folder name, and the URL slug. - A
title— the H1 doubles as the frontmattertitle, which is required on every post (the build fails without it). - A
description— a one-sentence, keyword-bearing SEO summary. It is required on every post (search snippets,og:description, JSON-LD), so propose it here. - Categories — 1–2, MUST come from
categories_allowedinmkdocs.yml— read the current list from there. - Tags — free-form, 4–8, technical (e.g.
WebRTC,self-hosted,Security,TURN,React).
Read 1–2 existing posts in docs/blog/posts/ to match tone and depth before finalizing.
Title rules
- Keep it under 70 characters and use the primary keyword naturally.
- Including a number (prefer odd) is a recommendation, not a requirement.
- Including the current year is a recommendation, not a requirement.
- A question-style title is allowed when it raises curiosity and fits intent.
- Bracketed/parenthetical supplemental context is allowed when useful.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 10d ago First seen · 89 lines · 84 tokens per session scan A 242eab5d9aef
blog-plan is a skill published in the GitHub repository OpenVidu/openvidu.io (5 stars, last pushed today), licensed Apache-2.0. It adds 84 tokens to every session and 1,254 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
replit-deck
For product and technical management work: turn PRDs, roadmaps, RFCs, architecture reviews, and retros into decision documents. Built around the core query "pm-feature-business-case-deck", with product strategy lead judgment, buyer-ready proof, and this outcome: approve the feature, architecture, roadmap, or incident…
hps-true-blueprint
OpenDesign's engineering blueprint: how the sandbox, sidecar, and daemon fit — the system diagram and the invariants. Built as a decision-grade product management deck for engineering org.
design-critique
Give a structured product design critique — user job clarity, hierarchy, affordance, error states, accessibility, and consistency — focused on what to change, in what order, and why.
analytics-product
Analytics de produto — PostHog, Mixpanel, eventos, funnels, cohorts, retencao, north star metric, OKRs e dashboards de produto.
html-ppt-knowledge-arch-blueprint
OpenDesign's incident retro: the daemon-restart data bug, the root cause, the fix, and the systemic follow-ups. Built as a decision-grade product management deck for engineering, SRE, leadership.
deck-open-slide-canvas
OpenDesign's architecture review: the local daemon + agent-runtime design, the tradeoffs, and the decision to lock. Built as a decision-grade product management deck for staff eng, tech leads, security.