${var} — Selector: <skill-name> [--brand <handle>] [--banner].

<skill-name> → announce that skill (must exist under skills/<skill-name>/).

empty → pick the most article-worthy skill from the last 14 days of memory/logs/: prefer a skill that shipped recently, produced verified output, or hit a milestone. If nothing qualifies, log SKILL_ARTICLE_NO_TARGET, send no notification, and exit clean.

--brand <handle> anywhere → byline/handle for the outreach footer (default: this instance's public identity from soul/, else the repo's org).

--banner anywhere → also generate one 16:9 title banner through the Higgsfield MCP (spends credits; see Step 5). Off by default - a blank run never spends.

Examples: "aeon-update", "rug-scan --brand @myproject --banner".

Today is ${today}. Write a launch article for one skill, modeled on the security-industry "skill announcement" format: the article sells the insight the skill encodes, not the file - and then gives the file away.

Shared preamble

Read memory/MEMORY.md and the last 14 days of memory/logs/ - know what this skill has actually done.
If a soul/ directory exists, read soul/SOUL.md and soul/STYLE.md for voice. Default voice: terse, declarative, builder-wrote-this-fast.
Read the target's full skills/<name>/SKILL.md. Every claim in the article must trace to a line in it.

skill-article

Shared preamble

Step 1 — Mine the track record (real numbers only)