メニュー
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 に表示されている付属ファイルをお読みください。
SOC 職業分類に基づく
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
直接コマンドでは確認用 Prompt が省略されます。実行前にソースを確認してください。
npx skills add https://github.com/aidenlx/zotlit --skill discord-announcementコマンドは1行のまま表示されます。コピー前に横へスクロールして全体を確認してください。
ローカルで確認しますか？SkillsMP が現在取得できるファイルをダウンロードできます。
SKILL.md を表示中
Write declarative settings tabs for Obsidian plugins using the 1.13.0+ getSettingDefinitions() API. Use when creating or editing a PluginSettingTab, adding settings controls (toggle, text, number, dropdown, slider, file, folder, color), building settings groups/lists/sub-pages, wiring conditional visibility or validation, migrating from the imperative display() approach, or touching any file under apps/obsidian/src/services/*/setting-tab/. Also use when opening the settings modal from code, deep-linking to a settings sub-page, or revealing/highlighting one setting row. Also use when the user mentions "setting tab", "plugin settings", "getSettingDefinitions", "SettingControl", "SettingDefinitionItem", "app.setting", or "openTabById", even if they don't explicitly ask for this skill.
Verify Next.js runtime behavior after editing app code. Use this skill to confirm a change actually works in a running app — not just that it compiles or type-checks. Combines /_next/mcp (Next.js's view) with agent-browser (the browser's view). Requires a running `next dev`.
Write a user-facing changelog entry under apps/docs/content/changelog/. Use when the user asks to "write the changelog", "draft changelog for v...", "add changelog entry", "document this release", or after a batch of obsidian/zotero fixes has landed and they want end-user release notes. Derives content from git history, filtering to user-observable changes only.
| 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.