release-changelog-discord-message

Generates a copy-pasteable Discord release announcement from a Paperclip release changelog.

Updated Jun 16, 2026
One-click install
npx skills add https://github.com/adamtpang/summon.company --skill release-changelog-discord-message-adamtpang
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: release-changelog-discord-message
Source: https://github.com/adamtpang/summon.company/tree/main/.agents/skills/release-changelog-discord-message
Command: npx skills add https://github.com/adamtpang/summon.company --skill release-changelog-discord-message-adamtpang

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Writing a Discord release announcement that matches the founder's voice and stays consistent with the changelog is tedious and error-prone. This Skill turns a stable Paperclip release changelog into a ready-to-paste Discord post, stored as the release issue's discord_announcement document. ## Core Features & Use Cases - Changelog-to-Discord conversion: Reads releases/vYYYY.MDD.P.md and produces a single fenced markdown block in dotta's voice, with matching version, date, and contributor list. - Voice and format template: Enforces the canonical structure (Highlights, WHATS NEXT, What's on my mind, Community, In Summary) with Discord emoji shortcodes and verbatim past examples as ground truth. - Issue and case integration: Upserts the discord_announcement document on the release issue with baseRevisionId handling, posts a copy-pasteable comment, and creates a tweet_storm child case. - Use Case: After the release-changelog skill produces releases/v2026.427.0.md, run this Skill to draft the Discord announcement, attach it to the release issue, and hand dotta a paste-ready block. ## Quick Start Read the matching releases/vYYYY.MDD.P.md changelog and generate the Discord announcement for the release issue, then update its discord_announcement document.

Frequently Asked Questions about release-changelog-discord-message

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I write a Discord release announcement from a changelog?

Read the matching releases/vYYYY.MDD.P.md file, then draft the announcement using the fixed template: highlights with emoji shortcodes, WHATS NEXT roadmap themes, What's on my mind, Community contributors, and the closing tagline. Version, date, and contributors must match the changelog exactly.

How do I update the discord_announcement document on a release issue?

Send a PUT request to /api/issues/{releaseIssueId}/documents/discord_announcement with the title, markdown format, and body. If the document already exists, fetch it first and pass the current baseRevisionId so updates never silently overwrite prior content.

Can this skill run without the release changelog file?

No. The skill must never run in isolation because the version, date, contributor list, and highlights must match the changelog produced by the release-changelog skill. If the changelog is updated, the announcement must be refreshed too.

Does the skill post the announcement to Discord automatically?

No. The skill only prepares the artifact: it updates the discord_announcement document, upserts a tweet_storm child case, and posts a fenced code block comment on the release issue. A human copies and posts it to Discord manually.

Where do the WHATS NEXT and What's on my mind sections come from?

They are pulled from the release issue thread, linked issues, active goals, and recent company issues. Themes must reflect real in-flight work and never be invented, keeping the announcement grounded in actual project activity.