netresearch/matrix-skill / skills/matrix-announcement
matrix-announcement
VerifiedUse 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.
| File | Kind | Size |
|---|---|---|
| README.md | markdown | 4.0 KB |
| SKILL.md | skill md | 3.5 KB |
| evals/evals.json | config | 8.2 KB |
| references/anti-patterns.md | markdown | 6.6 KB |
| references/gallery.html | other | 45.6 KB |
| references/glyphs.md | markdown | 2.0 KB |
| references/html-subset.md | markdown | 3.7 KB |
| references/image-cards.md | markdown | 5.0 KB |
| references/structure.md | markdown | 7.6 KB |
| references/templates/comparison.html | other | 3.7 KB |
| references/templates/release-card.html | other | 4.4 KB |
| references/templates/weekly-digest.html | other | 5.1 KB |
| references/text-templates.md | markdown | 6.5 KB |
| references/threading.md | markdown | 5.2 KB |
references/glyphs.md
View on GitHub<!-- SPDX-License-Identifier: CC-BY-SA-4.0 -->
<!-- SPDX-FileCopyrightText: Netresearch DTT GmbH -->
# Iconography & emoji
Emoji are powerful as **prefix glyphs** and dangerous as decoration.
The rule: **one glyph at the front of the title**, optionally one inline glyph per bullet to mark category. Never trailing decoration. Never celebrations. The glyph carries meaning β if it doesn't, drop it.
## Approved prefix glyphs
| Glyph | Meaning | Use case |
| --- | --- | --- |
| π€ | bot | agent-authored announcement |
| π¦ | release | new feature version |
| π§ | tooling | infra, build, dev experience |
| π‘ | security | CVE, hardening, lockdown |
| β οΈ | heads-up | breaking change, deprecation |
| π | digest | weekly / multi-skill roundup |
| π¬ | RFC | proposal, request for comment |
| π | hotfix | urgent patch |
| π₯ | postmortem | incident summary |
| π | findings | investigation or audit result |
| β¨ | new capability | use sparingly; never on every release |
## Banned
| Glyph | Why |
| --- | --- |
| π | "It's a release, not a launchpad." Cheapens the message. |
| π | "Nobody is celebrating." Sounds like marketing. |
| π― | meaningless |
| π₯ (as "cool") | reserved for postmortems |
| Multi-emoji ladders (πβ¨π, π₯π₯π₯) | Always wrong. |
| Emoji as bullet markers (π’ π‘ π΄) | Use a real `<ul>` and let the client style it. |
## Inline category glyphs
Inside a bullet, a leading 1-character category glyph is OK:
```
β’ β¨ new: progressive-disclosure refactor
β’ π§ changed: checkpoint runner hardened against ~10 edge cases
β’ π fixed: transitive dev-deps resolution
```
But **two glyphs in one bullet is a smell**. Pick the most important one or drop both.
## Why this matters
A coding agent posting `πβ¨π NEW RELEASE!!! πβ¨π` reads to humans as AI slop. The same announcement with `π¦ Release: matrix-skill v1.20.0` reads as professional. The information content is identical; the emoji choice is the entire signal of seriousness.
When in doubt: **one glyph or none**.
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: 322k | 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: 198k | 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: 119k | 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 |