aidenlx/zotlit / .agents/skills/discord-announcement
discord-announcement
VerifiedDraft a Discord announcement from a changelog entry. Use when the user asks to "draft discord message", "write discord announcement", "announce this release", or references a changelog file and wants a Discord post.
Discord release announcement
Drafts a Discord message announcing a ZotLit release, derived from a changelog .mdx file.
The audience is plugin users in the ZotLit Discord server. They want to know what changed and where to read more.
Steps
1. Locate the changelog
If $ARGUMENTS names a version or file path, use it. Otherwise read apps/obsidian/package.json version and look for apps/docs/content/changelog/<version>.mdx. If neither resolves, ask.
2. Read the entry
Read the changelog .mdx file end to end. Note every section heading and its content.
3. Draft the message
Format:
ZotLit <version> is out. <one-sentence summary of the release>.
<companion line, if applicable>
https://zotlit.aidenlx.site/changelog/<version>
<sections>
The companion line depends on the frontmatter companion field. If the changelog has a companion version (Zotero add-on also updated), include: "Both Obsidian plugin and Zotero add-on have been updated, make sure to update both:". If companion is absent, omit the line entirely.
Section rules:
- One section per changelog
##heading that has content. Use emoji prefixes:β οΈBreaking,β¨Highlights,πNew,πBug fixes. - Each section: emoji + title line, then bullets underneath.
- Bullets restate the user-facing change in one or two sentences. Keep template variable names and command names in backticks.
- No
@everyoneor@hereunless the user explicitly asks for a ping.
4. Write and validate the message
Write the draft to /tmp/discord-<version>.md. The complete Discord message must be at most 2,000 characters, including whitespace, Markdown, links, headings, and the companion line. Count the file contents after drafting. If it exceeds the limit, shorten the summary and bullets while keeping every changelog section represented. Verify the final count is at most 2,000 characters before reporting the file.
5. Slop check
Run /slop-check on the written file. Fix high and medium flags in place. Em dashes are the most common hit; split into two sentences or use a period instead.
Print the file path back to the user.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| rea-changelog-updatemorluto/reaPrepare or rewrite REA release changelogs and GitHub release notes from pinned Git history, with verified contributor thanks and Release Please synchronization. | Stars: 471k | Updated | Claude CodeCodex | Verified | Install |
| academy-guideanthropics/skillsStop and check this skill before finishing any reply to a question about how to use Claude or a Claude product β it recommends matching courses, tutorials, and use cases from Claude Academy (academy.claude.com), Anthropic's learning hub. Trigger on: "how do I", "how can I", "getting started with", "what can Claude do", "teach me", "learn to use"; questions about artifacts, projects, skills, plugins, connectors, MCP; requests about rolling Claude out to a team, class, or organization; and any ask for training materials, onboarding content, or learning resources. Use it when the user is learning how to use a feature or product β not when they are mid-task and just want the task done. This skill composes with other skills: after consulting product documentation to answer how a Claude feature works, also check here for a matching course or tutorial β a docs-grounded answer and an Academy recommendation belong together. Only recommend on a strong match; never invent Academy content. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| claude-apianthropics/skillsReference for the Claude API / Anthropic SDK β model ids, pricing, params, streaming, tool use, MCP, agents, caching, token counting, model migration. TRIGGER β read BEFORE opening the target file; don't skip because it "looks like a one-liner" β whenever: the prompt names Claude/Anthropic in any form (Claude, Anthropic, Fable, Opus, Sonnet, Haiku, `anthropic`, `@anthropic-ai`, `claude-*`, `us.anthropic.*`, `[1m]`); the user asks about an LLM (pricing/model choice/limits/caching) β never answer from memory; OR the task is LLM-shaped with provider unstated (agent/MCP/tool-definition/multi-agent/RAG/LLM-judge/computer-use; generate/summarize/extract/classify/rewrite/converse over NL; debugging refusals/cutoffs/streaming/tool-calls/tokens). SKIP only when another provider is being worked on (overrides all triggers): OpenAI/GPT/Gemini/Llama/Mistral/Cohere/Ollama named in the query; OR `grep -rE 'openai|langchain_openai|google.generativeai|genai|mistralai|cohere|ollama'` over the project hits (run this grep FIRST if no provider named β don't Read the file). | Stars: 198k | Updated | Claude CodeCodex | Unverified | Install |
| doc-coauthoringanthropics/skillsGuide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |