netresearch/matrix-skill / skills/matrix-announcement
matrix-announcement
UnverifiedUse when composing a Matrix announcement — skill release, version bump, weekly digest, breaking-change heads-up, postmortem, RFC, multi-skill pipeline summary, or any agent-authored room post longer than a single line. Trigger before any matrix-send call that produces structured content. Companion to matrix-communication.
Matrix Announcement
Content rules for Matrix announcements. matrix-communication does the sending.
The five rules
- One headline, one purpose.
formatted_bodyin the HTML subset, not Markdown.bodyis the plaintext fallback — clients aren't required to parse Markdown.- Lists beat paragraphs. Enumerable items — findings, projects, failures, tickets — are a
<ul>, however long each runs. A bold-led paragraph is emphasis, not structure. - Wrap code — and name the thing itself. Commands, paths, versions, IDs, env vars in
<code>; multi-line in<pre><code class="language-…">. Name the identifier, not a category standing in for it (html-subset.md). - Layout > words → render an HTML card to PNG. Comparisons, dashboards and multi-row tables die in
formatted_body.
Type tags (pick one — never stack)
New skill first release · Release feature version · Patch bugfix-only · Digest weekly roundup · Heads-up breaking change or deprecation · Postmortem incident · Findings investigation or audit · RFC proposal seeking feedback
Findings reports group by category of finding, never by who was wrong (structure.md).
Glyphs
One leading glyph at most. Never trailing decoration, multi-emoji ladders, 🚀, or 🎉. Approved: 🤖 bot · 📦 release · 🔧 tooling · 🛡 security · ⚠️ heads-up · 📋 digest · 🔬 RFC · 🚑 hotfix · 🔥 postmortem · 🔎 findings · ✨ new capability (sparingly).
Pre-send checklist
- One-line title at 1280px, opening with the change — not "we're excited to".
- URLs wrapped in
<a>, destination as text. - Every entity is a link: issue keys (even mid-sentence), versions → release page, MRs/PRs (
project/path!N/org/repo#N), pipelines, commits. Status updates: one item per line, linked key first, blank lines between. - Rules 3–5 applied: list structure, code wrapped, one glyph at most.
- Findings headings name the category, not the person.
-
bodyreads standalone, not stripped HTML. -
m.noticefor unattended automation,m.textotherwise; no@roomunless it is an outage. - Under 3000 chars, or threaded; image card if layout-heavy.
References
In references/:
html-subset.md— allowed/banned tags,data-mx-*, naming the identifierstructure.md— skeleton, length budget,m.textvsm.notice, how to sendglyphs.md·anti-patterns.md— glyph table; wall-of-text, emoji ladder, mention stormimage-cards.md— chromium → upload →m.imagethreading.md— threads, mentions, edits, redactionstext-templates.md·templates/·gallery.html— skeletons, HTML cards, preview
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deployment | Stars: 319k | Updated | Claude CodeCodex | Verified | Install |
| xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved. | Stars: 196k | Updated | Claude CodeCodex | Verified | Install |
| shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy. | Stars: 118k | Updated | Claude CodeCodex | Verified | Install |
| childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release. | Stars: 118k | Updated | Claude CodeCodex | Verified | Install |