matrix-announcement
Matrix Announcement
Content guidance for Matrix announcements; matrix-communication does the sending.
The five rules
- One headline, one purpose. A Matrix message is a tweet, not a blog post.
- Send
formatted_bodywith the HTML subset.bodystays as plaintext fallback. Never send only Markdown — clients are not required to parse it. - Lists beat paragraphs. If you're tempted to write "and also …", start a
<ul>. - Wrap code. Inline
<code>for commands, paths, version strings, IDs, env vars — every one of them. Multi-line snippets in<pre><code class="language-…">. - Layout > words → render an HTML card to PNG. Comparisons, dashboards, multi-row tables die in
formatted_body.
Type tags (pick one — never stack)
| Tag | Meaning | Title example |
|---|---|---|
New skill |
first public release | New skill: github-release-skill v0.2.0 |
Release |
feature version | Release: jira-skill v3.12.0 |
Patch |
bugfix-only | Patch: docker-development-skill v1.7.0 |
More from netresearch/matrix-skill
matrix-communication
Use when communicating via Matrix chat, notifying teams, or managing E2EE. Triggers on #room:server references, Matrix URLs, and chat requests.
27matrix-administration
Use when administering a Synapse / Matrix homeserver — list or snapshot all rooms, rate room health (public, unencrypted, orphaned), render a Graphviz map of the room/space tree, force-join users, promote room admins, harden rooms (add-to-space + restrict + encrypt), deactivate Matrix users (with GDPR erase), find biggest rooms by DB size, audit where a user is admin or member, replay join/leave timelines, or search unencrypted history. Trigger on any '/_synapse/admin', server-wide room operation, Matrix user offboarding, or anything requiring a homeserver-admin token — even without 'admin API' in the prompt. Companion to matrix-communication.
9