메뉴
Draft 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.
기본적으로 소스를 먼저 확인하는 Prompt가 선택됩니다. 직접 명령으로 전환하거나 로컬 사본을 다운로드할 수도 있습니다.
설치 여부를 결정하기 전에 SKILL.md와 SkillsMP에 표시된 보조 파일을 읽어 보세요.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
직접 명령은 검토 Prompt를 거치지 않습니다. 실행하기 전에 소스를 확인하세요.
npx skills add https://github.com/aidenlx/zotlit --skill discord-announcement명령은 한 줄로 유지됩니다. 복사하기 전에 가로로 스크롤해 전체 내용을 확인하세요.
로컬 사본을 원하시나요? SkillsMP에서 현재 제공할 수 있는 파일을 다운로드하세요.
SOC 직업 분류 기준
SKILL.md 표시 중
| name | discord-announcement |
| description | Draft 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. |
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.
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.
Read the changelog .mdx file end to end. Note every section heading and its content.
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:
## heading that has content. Use emoji prefixes: ⚠️ Breaking, ✨ Highlights, 🔗 New, 🐛 Bug fixes.@everyone or @here unless the user explicitly asks for a ping.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.
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.