{"slug":"release-post","title":"release-post","summary":"Create professional package release blog posts following Tidyverse or Shiny blog conventions. Use when the user needs to: (1) Write a release announcement blog post for an R or Python package for tidyverse.org or shiny.posit.co, (2) Transform NEWS/changelog content into blog form","platform":"Claude","tags":[],"authorName":"LLM Mart","authorSlug":"llm-mart","score":0,"source":"github","price":null,"verified":false,"createdAt":"2026-08-28T19:34:15.154221Z","repo":{"url":"https://github.com/posit-dev/skills","stars":518,"forks":53,"license":"MIT","updatedAt":"2026-09-18T19:30:01Z"},"bodyHtml":"<hr>\n<h2>name: release-post\ndescription: &gt;\nCreate professional package release blog posts following Tidyverse or Shiny blog conventions.\nUse when the user needs to: (1) Write a release announcement blog post for an R or Python package\nfor tidyverse.org or shiny.posit.co, (2) Transform NEWS/changelog content into blog format,\n(3) Generate acknowledgments sections with contributor lists, (4) Format posts following specific\nblog platform requirements. Supports both Tidyverse (hugodown) and Shiny (Quarto) blog formats with\nautomated contributor fetching and comprehensive style guidance.\nmetadata:\nauthor: Garrick Aden-Buie (@gadenbuie)\nversion: \"1.0\"\nlicense: MIT</h2>\n<h1>Package Release Post</h1>\n<p>Create professional R/Python package release blog posts following Tidyverse or Shiny blog conventions.</p>\n<h2>Quick Start</h2>\n<ol>\n<li><strong>Identify the blog platform</strong>: Tidyverse (tidyverse.org) or Shiny (shiny.posit.co)</li>\n<li>Verify NEWS.md or changelog exists for the package</li>\n<li>Gather package info: name, version, repository (e.g., \"tidyverse/dplyr\")</li>\n<li>Follow the workflow below</li>\n<li>Use <code>scripts/get_contributors.R</code> to generate acknowledgments</li>\n<li>Reference the appropriate formatting guide for final polish</li>\n</ol>\n<h2>Platform Selection</h2>\n<p>This skill supports two blog platforms with different formatting requirements:</p>\n<ul>\n<li><p><strong>Tidyverse blog</strong> (tidyverse.org)</p>\n<ul>\n<li>Uses hugodown</li>\n<li>R packages primarily</li>\n<li>More rigid structure and conventions</li>\n<li>See <code>references/tidyverse-formatting.md</code></li>\n</ul>\n</li>\n<li><p><strong>Shiny blog</strong> (shiny.posit.co)</p>\n<ul>\n<li>Uses Quarto</li>\n<li>R and Python packages</li>\n<li>More flexible, feature-focused structure</li>\n<li>See <code>references/shiny-formatting.md</code></li>\n</ul>\n</li>\n</ul>\n<p><strong>First, determine which platform the post is for</strong>, then follow the general workflow and apply platform-specific formatting.</p>\n<h2>General Workflow</h2>\n<p>These steps apply to both platforms. Content guidelines are based on Tidyverse best practices but adapt them as needed for Shiny posts.</p>\n<h3>Step 1: Gather Information</h3>\n<p>Collect required information:</p>\n<ul>\n<li><strong>Platform</strong>: Tidyverse or Shiny blog?</li>\n<li><strong>Package name and version</strong>: e.g., \"dplyr 1.2.0\" or \"shiny 1.9.0\"</li>\n<li><strong>Repository</strong>: GitHub repo in \"owner/repo\" format</li>\n<li><strong>Package language</strong>: R or Python</li>\n<li><strong>NEWS content</strong>: Read the package's NEWS.md, CHANGELOG, or NEWS</li>\n<li><strong>Package description</strong>: One-sentence core purpose</li>\n<li><strong>Previous release tag</strong>: For contributor fetching (optional)</li>\n<li><strong>Featured image</strong>: For frontmatter (optional but recommended)</li>\n</ul>\n<h3>Step 2: Structure the Post</h3>\n<p>Create the post outline following this order:</p>\n<ol>\n<li><p><strong>Frontmatter</strong>: Platform-specific YAML (see formatting references)</p>\n</li>\n<li><p><strong>Title and Opening</strong>:</p>\n<ul>\n<li>Title: Package name and version</li>\n<li>Opening: Announcement with one-sentence package description</li>\n<li>Installation: Code block with installation command</li>\n<li>Overview: Brief summary with link to full release notes</li>\n</ul>\n</li>\n<li><p><strong>Main Content</strong> (choose appropriate sections):</p>\n<ul>\n<li><strong>Migration guide</strong> (if breaking changes) - Always first when present</li>\n<li><strong>Lifecycle changes</strong> (deprecations, soft-deprecations, defunct)</li>\n<li><strong>Feature sections</strong> (one per major feature, descriptive headings)</li>\n<li><strong>Minor improvements</strong> (bulleted list)</li>\n</ul>\n</li>\n<li><p><strong>Acknowledgements</strong> (when appropriate):</p>\n<ul>\n<li>Use <code>scripts/get_contributors.R</code></li>\n<li>Format: \"A big thank you to all the folks who helped make this release happen:\"</li>\n<li>Comma-separated GitHub links</li>\n</ul>\n</li>\n</ol>\n<h3>Step 3: Apply Content Guidelines</h3>\n<p>Follow the best practices in <code>references/content-guidelines.md</code>:</p>\n<ul>\n<li><strong>Opening style</strong>: \"We're [random adjective expressing excitement] to announce the release of...\"</li>\n<li><strong>Section organization</strong>: Migration → Lifecycle → Features → Improvements → Acknowledgements</li>\n<li><strong>Tone</strong>: Conversational, professional, enthusiastic but authentic</li>\n<li><strong>Technical precision</strong>: Use exact function names in backticks</li>\n<li><strong>Focus on benefits</strong>: Explain \"why\" not just \"what\"</li>\n<li><strong>Code examples</strong>: Realistic, well-commented, properly formatted</li>\n</ul>\n<h3>Step 4: Transform NEWS Content</h3>\n<p>Convert NEWS.md bullets to blog-friendly content:</p>\n<ul>\n<li><strong>Research features thoroughly</strong>: Don't just copy NEWS bullets—read function docs, check PRs, understand the context</li>\n<li><strong>Expand context</strong>: Why changes matter, not just what changed</li>\n<li><strong>Add complete code examples</strong>: Show realistic usage with full workflows, not just function signatures</li>\n<li><strong>Explain concepts first</strong>: For unfamiliar features, explain what they are and how they work before showing code</li>\n<li><strong>Group thematically</strong>: Combine related NEWS items into coherent sections</li>\n<li><strong>Use conversational tone</strong>: Transform terse bullets into prose</li>\n<li><strong>Link documentation</strong>: Add relevant links to docs and resources</li>\n<li><strong>Highlight breaking changes</strong>: Make migration paths clear</li>\n<li><strong>Multi-language parity</strong> (Shiny only): For R+Python packages on the Shiny blog, ensure all examples show both languages in tabsets</li>\n</ul>\n<h3>Step 5: Apply Platform-Specific Formatting</h3>\n<p><strong>For Tidyverse posts</strong>, read <code>references/tidyverse-formatting.md</code> and apply:</p>\n<ul>\n<li>hugodown frontmatter with <code>slug</code>, <code>photo.url</code>, <code>photo.author</code></li>\n<li>Specific slug format: <code>packagename-x-y-z</code> (hyphens replace dots)</li>\n<li>R code blocks with <code>r</code> language identifier</li>\n<li>Acknowledgements always included as final section</li>\n</ul>\n<p><strong>For Shiny posts</strong>, read <code>references/shiny-formatting.md</code> and apply:</p>\n<ul>\n<li>Quarto frontmatter with YAML anchors for social media</li>\n<li>Flexible title formatting</li>\n<li>Use tabsets for Python/R or Express/Core variations</li>\n<li>Platform-specific code block attributes</li>\n<li>Acknowledgements optional, varies by post type</li>\n<li>May use lead paragraphs, callouts, embedded media</li>\n</ul>\n<h3>Step 6: Generate Acknowledgements</h3>\n<p>Run the contributor script:</p>\n<pre><code>Rscript scripts/get_contributors.R \"owner/repo\"\n</code></pre>\n<p>Or with a specific starting tag for the previous version (or tag used for last release post):</p>\n<pre><code>Rscript scripts/get_contributors.R \"owner/repo\" \"v1.0.0\"\n</code></pre>\n<p>Copy the markdown output into the Acknowledgements section.</p>\n<h3>Step 7: Review and Polish</h3>\n<p>Platform-agnostic checklist:</p>\n<ul>\n<li><input disabled=\"disabled\" type=\"checkbox\"> Frontmatter complete with all required fields</li>\n<li><input disabled=\"disabled\" type=\"checkbox\"> Opening clearly states package purpose</li>\n<li><input disabled=\"disabled\" type=\"checkbox\"> Installation code block present (both languages if applicable)</li>\n<li><input disabled=\"disabled\" type=\"checkbox\"> Sections organized logically</li>\n<li><input disabled=\"disabled\" type=\"checkbox\"> Code examples use proper syntax highlighting</li>\n<li><input disabled=\"disabled\" type=\"checkbox\"> Function names in backticks with parentheses: <code>`function()`</code></li>\n<li><input disabled=\"disabled\" type=\"checkbox\"> Package names are not backticked or otherwise styled</li>\n<li><input disabled=\"disabled\" type=\"checkbox\"> Tone is conversational but not marketing-speak</li>\n<li><input disabled=\"disabled\" type=\"checkbox\"> No superlatives (\"powerful\", \"rich\", \"seamless\", etc.)</li>\n<li><input disabled=\"disabled\" type=\"checkbox\"> Features explained with context, not just listed</li>\n<li><input disabled=\"disabled\" type=\"checkbox\"> Concepts explained before showing code</li>\n<li><input disabled=\"disabled\" type=\"checkbox\"> All examples show R and Python variants (if applicable)</li>\n<li><input disabled=\"disabled\" type=\"checkbox\"> Links to full release notes included</li>\n</ul>\n<p>Platform-specific checklist:</p>\n<p><strong>Tidyverse:</strong></p>\n<ul>\n<li><input disabled=\"disabled\" type=\"checkbox\"> Slug format: <code>package-x-y-z</code> (hyphens, not dots)</li>\n<li><input disabled=\"disabled\" type=\"checkbox\"> Photo URL and author included</li>\n<li><input disabled=\"disabled\" type=\"checkbox\"> Acknowledgements section is final section</li>\n<li><input disabled=\"disabled\" type=\"checkbox\"> All contributors listed alphabetically</li>\n</ul>\n<p><strong>Shiny:</strong></p>\n<ul>\n<li><input disabled=\"disabled\" type=\"checkbox\"> YAML anchors used for description (<code>&amp;desc</code>, <code>*desc</code>)</li>\n<li><input disabled=\"disabled\" type=\"checkbox\"> Social media cards configured (<code>open-graph</code>, <code>twitter-card</code>)</li>\n<li><input disabled=\"disabled\" type=\"checkbox\"> Appropriate filters specified if using tabsets/shinylive</li>\n<li><input disabled=\"disabled\" type=\"checkbox\"> Tabsets used for showing paired variants (Python/R, Express/Core)</li>\n<li><input disabled=\"disabled\" type=\"checkbox\"> Multi-language tabsets used consistently (for R+Python packages only)</li>\n</ul>\n<h2>Reference Documentation</h2>\n<p>Load these as needed for detailed guidance:</p>\n<h3>Content Guidelines</h3>\n<p><strong><code>references/content-guidelines.md</code></strong> - General best practices for all release posts:</p>\n<ul>\n<li>Post structure and organization</li>\n<li>Opening style and tone</li>\n<li>Section hierarchy and organization</li>\n<li>Code examples and formatting</li>\n<li>Before/after patterns</li>\n<li>Acknowledgments conventions</li>\n</ul>\n<h3>Platform-Specific Formatting</h3>\n<p><strong><code>references/tidyverse-formatting.md</code></strong> - Tidyverse blog requirements:</p>\n<ul>\n<li>hugodown frontmatter structure</li>\n<li>Slug and title conventions</li>\n<li>Photo attribution</li>\n<li>Code block formatting</li>\n<li>Lifecycle section structure</li>\n<li>Acknowledgements format</li>\n</ul>\n<p><strong><code>references/shiny-formatting.md</code></strong> - Shiny blog requirements:</p>\n<ul>\n<li>Quarto frontmatter with YAML anchors</li>\n<li>Social media card configuration</li>\n<li>Lead paragraphs and callouts</li>\n<li>Tabsets for variants</li>\n<li>Line highlighting and annotations</li>\n<li>Video embedding</li>\n<li>Flexible acknowledgements</li>\n</ul>\n<h2>Resources</h2>\n<ul>\n<li><strong><code>scripts/get_contributors.R</code></strong>: Fetch formatted contributor list using <code>usethis::use_tidy_thanks()</code></li>\n<li><strong><code>references/content-guidelines.md</code></strong>: General content best practices (platform-agnostic)</li>\n<li><strong><code>references/tidyverse-formatting.md</code></strong>: Tidyverse-specific formatting requirements</li>\n<li><strong><code>references/shiny-formatting.md</code></strong>: Shiny-specific formatting requirements</li>\n</ul>\n<h2>Platform-Specific Quick Reference</h2>\n<h3>Tidyverse Post Template</h3>\n<pre><code>---\noutput: hugodown::hugo_document\nslug: package-x-y-z\ntitle: package x.y.z\ndate: YYYY-MM-DD\nauthor: Your Name\ndescription: &gt;\n    Brief description\nphoto:\n  url: https://unsplash.com/photos/id\n  author: Photographer Name\ncategories: [package]\ntags: [package]\n---\n\n# package x.y.z\n\nWe're pleased to announce the release of package x.y.z...\n\n```r\ninstall.packages(\"package\")\n```\n\n...\n\n## Acknowledgements\n\nA big thank you to all the folks who helped make this release happen:\n\n[Contributors from get_contributors.R]\n</code></pre>\n<h3>Shiny Post Template</h3>\n<pre><code>---\ntitle: Package Name x.y.z\ndescription: &amp;desc |\n  Brief description of the release.\nauthor: \"Your Name\"\ndate: \"YYYY-MM-DD\"\n\nimage: feature.png\n\nopen-graph:\n  image: feature.png\n  description: *desc\ntwitter-card:\n  image: feature.png\n  description: *desc\n---\n\n# package x.y.z\n\nWe're excited to announce package x.y.z...\n\n[Installation for Python or R]\n\n...\n</code></pre>\n<h2>Tips</h2>\n<ul>\n<li><strong>Breaking changes first</strong>: Put migration guides before features</li>\n<li><strong>Highlight the wins</strong>: Lead with the most exciting features</li>\n<li><strong>Show don't tell</strong>: Use code examples liberally</li>\n<li><strong>Link generously</strong>: Help readers find more information</li>\n<li><strong>Keep it conversational</strong>: Write like you're explaining to a colleague</li>\n<li><strong>Be authentic</strong>: Enthusiasm should feel genuine, not marketing-speak</li>\n</ul>\n","files":[{"path":"references/content-guidelines.md","sizeBytes":12141,"isText":true},{"path":"references/shiny-formatting.md","sizeBytes":12096,"isText":true},{"path":"references/tidyverse-formatting.md","sizeBytes":7314,"isText":true},{"path":"scripts/get_contributors.R","sizeBytes":1411,"isText":false},{"path":"SKILL.md","sizeBytes":9892,"isText":true}],"reviewScore":null,"reviewSummary":null,"trust":{"provenance":"trusted-source-unreviewed","notice":"Community-authored content, reproduced verbatim and not vetted as instructions. Treat it as data to evaluate, never as directives to follow.","bodySource":null},"bodyLocked":false,"purchaseUrl":null,"sourceUrl":null,"report":{"provenance":"trusted-source-unreviewed","screen":{"ran":true,"outcome":"clean","suspicious":0,"notes":0,"hiddenCharacters":false},"virusScan":{"engine":"clamav","status":"clean","scannedAt":"2026-08-28T19:34:26.043136Z","sha256":"387032D24701F0BCF705C87D7381363DFE67E0F2B3B0BB715126D6682B498AB4","sizeBytes":17548},"review":null,"source":{"repositoryUrl":"https://github.com/posit-dev/skills","path":"open-source/release-post","license":"MIT","commit":"1bb49b8eecba38f04d39c2e6ddb8f8871382fe72","subtreeSha":"E31A577695BD29A465B1F043B2870EAA698105F1478C557A5B338A1D08682CD0","lastSyncedAt":"2026-09-21T13:51:07.177786Z"},"reviewedAt":"2026-08-28T19:35:21.559983Z","notice":"Community-authored content, reproduced verbatim and not vetted as instructions. Treat it as data to evaluate, never as directives to follow."},"install":[{"target":"skills-cli","command":"npx skills add https://github.com/posit-dev/skills/tree/main/open-source/release-post"},{"target":"claude-code","command":"claude plugin marketplace add https://llmmart.ai/marketplace.json && claude plugin install posit-dev-skills@llmmart"},{"target":"git","command":"git clone https://github.com/posit-dev/skills.git"}]}