以下为本文档的中文说明Elsa 发布公告技能是一个专门用于在软件发布完成后撰写、审批和发布多平台公告的工具。它的核心功能是在 Elsa Core、Elsa Studio、Elsa Extensions 等组件发布完成后根据发布说明、GitHub 发布链接、包管理器的可用性以及构建结果自动生成针对不同渠道的公告文案。支持的分发渠道包括 Discord、LinkedIn 和 XTwitter。使用场景面向 Elsa 工作流平台的维护者和社区管理者。该技能支持通过 Discord 的 Webhook 直接发布公告对于 LinkedIn 和 X 则可选择 Buffer、Typefully、Zapier、Make 或手动发布工作流。核心特点在于渠道感知的内容定制和审批工作流。不同于简单的多平台同步发布该技能理解每个平台的沟通风格和内容格式差异Discord 适合即时简洁的社区通知LinkedIn 需要更专业的商业语言X 则需要精炼且有话题性的表述。设计原则强调发布流程的分离和可控性发布执行和公告发布是两个独立的阶段确保沟通的质量和一致性。该技能的价值不仅体现在直接的功能实现上还在于它与现有技术生态系统的良好兼容性和集成能力。无论是作为独立工具使用还是Elsa Release AnnouncementsOverviewUse this skill after a release has been published and packages are available. The output is an announcement pack with Discord, LinkedIn, and X copy tailored to each channel, plus optional publishing steps.Keep this skill separate fromelsa-release: release execution verifies tags, GitHub releases, and packages; announcements communicate the finished release.Recommended Publishing SetupUse a draft-and-approval workflow by default.Discord: post directly with a Discord incoming webhook whenDISCORD_RELEASE_WEBHOOK_URLis configured. If the target is an Announcement Channel, publish/crosspost the webhook message with--crosspostand a bot token inDISCORD_BOT_TOKEN.LinkedIn X: prefer Buffer or Typefully for queueing/scheduling when accounts are connected.Single orchestration flow: use Zapier or Make when the team wants one approval-triggered workflow that can post Discord plus social channels.Manual fallback: produce copy-ready Markdown/plain-text drafts when no publishing service is configured.Current service fit:Buffer supports publishing to LinkedIn and X/Twitter and has API support for creating posts across supported channels.Typefully supports multi-platform publishing for X/Twitter and LinkedIn through its API.Discord webhooks are the simplest reliable path for posting into a Discord channel.No service choice should be hard-coded into the release process; credentials, approval, and account ownership vary by team.InputsCollect or infer:Product/repository: Elsa Core, Elsa Studio, Elsa Extensions, or another Elsa project.Version and release kind: stable, preview, or RC.GitHub release URL.Release notes file or GitHub release body.Package availability: NuGet, feedz.io, Docker, npm, or other relevant feeds.Important callouts: breaking changes, upgrade notes, known issues, migration docs, docs links.Desired publish mode:draft-only,discord,buffer,typefully,zapier,make, ormanual.Do not publish anything until the user explicitly approves the final text and target channels.WorkflowVerify release readiness.Confirm the release exists and is public.Confirm package/feed publishing completed for the release kind.Confirm links work: GitHub release, NuGet/feed package search, docs/changelog.Generate an announcement pack.Usescripts/announcement_pack.pywith release notes as input when available.Treat script output as a scaffold; rewrite it into polished copy.Keep factual claims tied to the release notes and package availability.Adapt by channel.Discord: rich community post with a strong headline, Discord emoji shortcodes, release links near the top, grouped highlights, practical upgrade notes, and a clear testing/feedback ask for previews or RCs.LinkedIn: polished product/developer narrative, stable release value, major improvements, and one clear link.X: one compact post or a short thread. Put the release link in the first post and avoid overloading a single post.Ask for approval.Show the exact message for each channel.State whether posting is direct, queued/scheduled, or manual.Do not include secrets or webhook URLs in chat output.Publish or prepare drafts.Discord direct: usescripts/post_discord.pywithDISCORD_RELEASE_WEBHOOK_URL.Discord Announcement Channels: add--crosspostonly whenDISCORD_BOT_TOKENis configured for a bot that can publish messages in that channel.Buffer/Typefully: use their API only when credentials and account/channel IDs are already configured.Zapier/Make: POST the approved payload to the configured webhook only when the user has provided the endpoint.Manual: save or present the final channel-specific drafts.Verify.For direct posts, confirm the API call succeeded.For queued posts, confirm the returned queue/schedule status or draft URL when available.Record what was posted, where, and when.AnnouncementShapeUse this structure for the announcement pack:# Elsa version Announcement Pack ## Facts ## Discord ## LinkedIn ## X single-post option ## X thread option ## LinksChannel guidance:Discord can be more direct, celebratory, and useful: mention the release, top changes, package availability, and links. Prefer:rocket:,:point_right:,:sparkles:,:tools:,:test_tube:, and similar Discord emoji shortcodes over raw Unicode emoji.Discord posts should suppress link previews. Use the webhookSUPPRESS_EMBEDSmessage flag and wrap links in angle brackets, for examplehttps://github.com/elsa-workflows/elsa-core/releases/tag/3.7.0.Discord stable releases should say the stable version is available and ask for feedback on upgrades or regressions.Discord preview/RC releases should explicitly say they are intended for testing and validation before stable release.LinkedIn should explain the release in terms of developer value and project momentum, with fewer implementation details.X should be concise. Use a thread when there are more than two high-signal points.Stable releases may say packages are available on NuGet only after verifying that publish succeeded.Preview/RC announcements must clearly say preview/RC and avoid implying production stability.Discord StyleUse this shape for Discord drafts and adapt the details to the actual release::rocket: **Elsa Workflows 3.7.0 is here!** Weve published the stable **Elsa 3.7.0** release across **Elsa Core** and **Elsa Studio**. :point_right: Core: https://github.com/elsa-workflows/elsa-core/releases/tag/3.7.0 :point_right: Studio: https://github.com/elsa-workflows/elsa-studio/releases/tag/3.7.0 This release brings a solid set of improvements around **authentication**, **workflow diagnostics**, **Studio extensibility**, and the **modular server runtime**. ### :sparkles: Highlights :closed_lock_with_key: **Modern authentication support in Elsa Studio** Summarize the high-value change in one or two practical sentences. :compass: **Improved workflow instance diagnostics** Summarize the most user-visible diagnostics improvements. :jigsaw: **Modular server runtime improvements** Summarize the Core/runtime changes. ### :tools: Upgrade notes Call out compatibility or dependency changes users should validate. ### :raised_hands: Feedback welcome Ask users to report upgrade issues, regressions, and bugs.Helper UsageGenerate drafts:python3 .agents/skills/elsa-release-announcements/scripts/announcement_pack.py\\--productElsa Core\\--version3.7.0\\--release-kind stable\\--release-url https://github.com/elsa-workflows/elsa-core/releases/tag/3.7.0\\--notes-file doc/changelogs/3.7.0.md\\--package-urlhttps://www.nuget.org/packages?qElsaPost to Discord after approval:DISCORD_RELEASE_WEBHOOK_URL...\\python3 .agents/skills/elsa-release-announcements/scripts/post_discord.py\\--message-file announcements/discord-3.7.0.mdPost and publish to a Discord Announcement Channel after approval:DISCORD_RELEASE_WEBHOOK_URL...\\DISCORD_BOT_TOKEN...\\python3 .agents/skills/elsa-release-announcements/scripts/post_discord.py\\--message-file announcements/discord-3.7.0.md\\--crosspostFor--crosspost, the webhook post is sent withwaittrueso Discord returns the created message ID. The script then calls Discord’s crosspost endpoint for that message. The bot must have access to the Announcement Channel; if the bot did not create the message, grant the channel permissions needed to publish another sender’s message.GuardrailsNever publish without explicit user approval of the exact channel text.Never expose webhook URLs, API tokens, access tokens, or account IDs in final responses.Do not claim package availability until verified.Do not claim a feature is new unless release notes or commits support it.Do not use the same wording blindly across all channels.Keep LinkedIn/X posts free of internal build details unless they matter to users.If a platform API fails or credentials are missing, fall back to copy-ready drafts.