[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M73869BE8CBGSW3FSSZTYJDV":3,"skill-same:01M73869BE8CBGSW3FSSZTYJDV":65},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":33,"commitSha":34,"skillDirectory":35,"forksCount":36,"repositoryHtmlUrl":37,"repositoryHomepageUrl":6,"ownerHtmlUrl":38,"ownerBlogUrl":39,"ownerDescription":6,"updatedAt":40,"install":41,"resources":54},"01M73869BE8CBGSW3FSSZTYJDV","deliver-release-notes",null,"Creates user-facing release notes that communicate new features, improvements, and fixes in clear, benefit-focused language. Use when shipping updates to communicate changes to users, customers, or stakeholders.","roohe\u002Fagentic-super-skills","roohe","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F99054084?v=4","01M734WCDFP6RZVT5CNM00QR26","01M734WCE4BD0T4NZS5PCV9V5F",10,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Froohe\u002Fagentic-super-skills\u002Fblob\u002Fmaster\u002Fskills_library\u002Fdeliver-release-notes\u002FSKILL.md",[],[],"2026-11-11 15:11:14",false,"---\nname: deliver-release-notes\ndescription: Creates user-facing release notes that communicate new features, improvements, and fixes in clear, benefit-focused language. Use when shipping updates to communicate changes to users, customers, or stakeholders.\nphase: deliver\nversion: \"2.0.0\"\nupdated: 2026-01-26\nlicense: Apache-2.0\nmetadata:\n  category: coordination\n  frameworks: [triple-diamond, lean-startup, design-thinking]\n  author: product-on-purpose\n---\n\u003C!-- PM-Skills | https:\u002F\u002Fgithub.com\u002Fproduct-on-purpose\u002Fpm-skills | Apache 2.0 -->\n# Release Notes\n\nRelease notes communicate product changes to users in a way that highlights value and builds excitement. Unlike changelogs (which document what changed technically), release notes translate changes into user benefits. Good release notes help users discover new capabilities, understand improvements, and trust that issues are being addressed.\n\n## When to Use\n\n- Shipping product updates to customers\n- Communicating changes to internal stakeholders\n- Preparing app store update descriptions\n- Writing customer-facing email announcements\n- Documenting changes for support and sales teams\n\n## Instructions\n\nWhen asked to create release notes, follow these steps:\n\n1. **Gather the Changelog**\n   Collect all changes included in this release: features, improvements, and bug fixes. Work from engineering changelogs, completed tickets, or pull request descriptions.\n\n2. **Identify the Highlights**\n   Select 1-3 changes that deserve top billing. These should be changes users will notice and care about most. Lead with the most impactful change.\n\n3. **Translate to Benefits**\n   Rewrite each change in terms of user value. Instead of \"Added pagination to search results,\" write \"Find what you need faster with improved search that handles large result sets.\" Focus on what users can now do or what's now better.\n\n4. **Categorize Changes**\n   Group remaining changes into clear categories: New Features, Improvements, and Bug Fixes. Within each category, order by impact (most valuable first).\n\n5. **Write Scannable Descriptions**\n   Each item should be 1-2 sentences. Lead with the benefit, optionally followed by the \"how.\" Users scan release notes . make each line valuable.\n\n6. **Acknowledge Known Issues**\n   If there are known limitations or issues, be transparent. Users appreciate honesty, and it reduces support burden.\n\n7. **Tease Coming Soon (Optional)**\n   If appropriate, hint at what's coming next. This builds anticipation and shows momentum, but don't over-promise.\n\n## Output Format\n\nUse the template in `references\u002FTEMPLATE.md` to structure the output.\n\n## Quality Checklist\n\nBefore finalizing, verify:\n\n- [ ] Highlights feature the 1-3 most impactful changes\n- [ ] Each item leads with user benefit, not technical description\n- [ ] Language is jargon-free and accessible to all users\n- [ ] Items are concise (1-2 sentences each)\n- [ ] Bug fixes mention the problem that was solved\n- [ ] Tone is positive and professional\n\n## Examples\n\nSee `references\u002FEXAMPLE.md` for a completed example.\n","\u003C!-- PM-Skills | https:\u002F\u002Fgithub.com\u002Fproduct-on-purpose\u002Fpm-skills | Apache 2.0 -->\n# Release Notes\n\nRelease notes communicate product changes to users in a way that highlights value and builds excitement. Unlike changelogs (which document what changed technically), release notes translate changes into user benefits. Good release notes help users discover new capabilities, understand improvements, and trust that issues are being addressed.\n\n## When to Use\n\n- Shipping product updates to customers\n- Communicating changes to internal stakeholders\n- Preparing app store update descriptions\n- Writing customer-facing email announcements\n- Documenting changes for support and sales teams\n\n## Instructions\n\nWhen asked to create release notes, follow these steps:\n\n1. **Gather the Changelog**\n   Collect all changes included in this release: features, improvements, and bug fixes. Work from engineering changelogs, completed tickets, or pull request descriptions.\n\n2. **Identify the Highlights**\n   Select 1-3 changes that deserve top billing. These should be changes users will notice and care about most. Lead with the most impactful change.\n\n3. **Translate to Benefits**\n   Rewrite each change in terms of user value. Instead of \"Added pagination to search results,\" write \"Find what you need faster with improved search that handles large result sets.\" Focus on what users can now do or what's now better.\n\n4. **Categorize Changes**\n   Group remaining changes into clear categories: New Features, Improvements, and Bug Fixes. Within each category, order by impact (most valuable first).\n\n5. **Write Scannable Descriptions**\n   Each item should be 1-2 sentences. Lead with the benefit, optionally followed by the \"how.\" Users scan release notes . make each line valuable.\n\n6. **Acknowledge Known Issues**\n   If there are known limitations or issues, be transparent. Users appreciate honesty, and it reduces support burden.\n\n7. **Tease Coming Soon (Optional)**\n   If appropriate, hint at what's coming next. This builds anticipation and shows momentum, but don't over-promise.\n\n## Output Format\n\nUse the template in `references\u002FTEMPLATE.md` to structure the output.\n\n## Quality Checklist\n\nBefore finalizing, verify:\n\n- [ ] Highlights feature the 1-3 most impactful changes\n- [ ] Each item leads with user benefit, not technical description\n- [ ] Language is jargon-free and accessible to all users\n- [ ] Items are concise (1-2 sentences each)\n- [ ] Bug fixes mention the problem that was solved\n- [ ] Tone is positive and professional\n\n## Examples\n\nSee `references\u002FEXAMPLE.md` for a completed example.\n",{"name":5,"phase":23,"license":14,"updated":24,"version":25,"metadata":26,"description":7},"deliver",1769385600000,"2.0.0",{"author":27,"category":28,"frameworks":29},"product-on-purpose","coordination",[30,31,32],"triple-diamond","lean-startup","design-thinking","master","f483e54f3ad5f202a77d45f2e57f8d970b71195f","skills_library\u002Fdeliver-release-notes",2,"https:\u002F\u002Fgithub.com\u002Froohe\u002Fagentic-super-skills","https:\u002F\u002Fgithub.com\u002Froohe","yoou.link","2026-05-19 15:56:07",{"source":8,"skillName":5,"commands":42,"prompt":52,"zipAvailable":53},[43,46,49],{"tool":44,"command":45},"npx","npx skills add roohe\u002Fagentic-super-skills --skill deliver-release-notes",{"tool":47,"command":48},"bunx","bunx skills add roohe\u002Fagentic-super-skills --skill deliver-release-notes",{"tool":50,"command":51},"pnpm","pnpm dlx skills add roohe\u002Fagentic-super-skills --skill deliver-release-notes","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Froohe\u002Fagentic-super-skills\u002Fblob\u002Fmaster\u002Fskills_library\u002Fdeliver-release-notes\u002FSKILL.md",true,[55,61],{"path":56,"resourceType":57,"resourceTypeDesc":58,"sizeBytes":59,"sourceHtmlUrl":60},"references\u002FEXAMPLE.md","REFERENCE","参考文档",3549,"https:\u002F\u002Fgithub.com\u002Froohe\u002Fagentic-super-skills\u002Fblob\u002Fmaster\u002Fskills_library\u002Fdeliver-release-notes\u002Freferences\u002FEXAMPLE.md",{"path":62,"resourceType":57,"resourceTypeDesc":58,"sizeBytes":63,"sourceHtmlUrl":64},"references\u002FTEMPLATE.md",1672,"https:\u002F\u002Fgithub.com\u002Froohe\u002Fagentic-super-skills\u002Fblob\u002Fmaster\u002Fskills_library\u002Fdeliver-release-notes\u002Freferences\u002FTEMPLATE.md",[66,74,81,88,95,102],{"skillNo":67,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":70,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":18},"01M73D865CZME2FCMKA4PQM348","zarr-python","Chunked N-D arrays for cloud storage. Compressed arrays, parallel I\u002FO, S3\u002FGCS integration, NumPy\u002FDask\u002FXarray compatible, for large-scale scientific computing pipelines.","MIT","https:\u002F\u002Fgithub.com\u002Froohe\u002Fagentic-super-skills\u002Fblob\u002Fmaster\u002Fskills_library\u002Fzarr-python\u002FSKILL.md",[],[],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":70,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":18},"01M73D7Z64J4ABWZJD7P44XBBF","youtube-downloader","Download and process YouTube content for research. Use when: downloading competitor videos for analysis; extracting audio for podcasts; getting transcripts for content repurposing; archiving webinars; research content curation","https:\u002F\u002Fgithub.com\u002Froohe\u002Fagentic-super-skills\u002Fblob\u002Fmaster\u002Fskills_library\u002Fyoutube-downloader\u002FSKILL.md",[],[],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":70,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":18},"01M73D7K8778TGZV3GJFR3703D","yc-pitch-deck","Create a compelling startup pitch deck that follows the structure proven to raise billions from top investors. Master the YC and Sequoia formats that get founders funded. Use when: **Fundraising** to create investor pitch decks; **YC application** to structure your narrative; **Demo Day prep** to craft your 2-minute pitch; **Angel investors** to communicate your opportunity; **Partnership pitches** to structure compelling asks","https:\u002F\u002Fgithub.com\u002Froohe\u002Fagentic-super-skills\u002Fblob\u002Fmaster\u002Fskills_library\u002Fyc-pitch-deck\u002FSKILL.md",[],[],{"skillNo":89,"name":90,"nameZh":6,"description":91,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":70,"licenseFileUrl":6,"sourceHtmlUrl":92,"categories":93,"keywords":94,"publishedAt":18},"01M73D70KJSE0E8Z28YMNNRT04","x-twitter-scraper","Use when the user needs X (Twitter) data or confirmation-gated X actions through Xquik: tweet search, user lookup, follower extraction, media download, monitoring, webhooks, MCP, SDKs, posting, likes, DMs, and profile updates. Requires a Xquik API key. Never ask for X login material.","https:\u002F\u002Fgithub.com\u002Froohe\u002Fagentic-super-skills\u002Fblob\u002Fmaster\u002Fskills_library\u002Fx-twitter-scraper\u002FSKILL.md",[],[],{"skillNo":96,"name":97,"nameZh":6,"description":98,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":70,"licenseFileUrl":6,"sourceHtmlUrl":99,"categories":100,"keywords":101,"publishedAt":18},"01M73D6ED01GV077R7K4NZNFZJ","write-vignette","Create R package vignettes using R Markdown or Quarto. Covers vignette setup, YAML configuration, code chunk options, building and testing, and CRAN requirements for vignettes. Use when adding a Getting Started tutorial, documenting complex workflows spanning multiple functions, creating domain-specific guides, or when CRAN submission requires user-facing documentation beyond function help pages.","https:\u002F\u002Fgithub.com\u002Froohe\u002Fagentic-super-skills\u002Fblob\u002Fmaster\u002Fskills_library\u002Fwrite-vignette\u002FSKILL.md",[],[],{"skillNo":103,"name":104,"nameZh":6,"description":105,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":70,"licenseFileUrl":6,"sourceHtmlUrl":106,"categories":107,"keywords":108,"publishedAt":18},"01M73D69YJR0BK3NFHE0CYG3EF","write-validation-documentation","Write IQ\u002FOQ\u002FPQ validation documentation for computerized systems in regulated environments. Covers protocols, reports, test scripts, deviation handling, and approval workflows. Use when validating R or other software for regulated use, preparing for a regulatory audit, documenting qualification of computing environments, or creating and updating validation protocols and reports for new or re-qualified systems.","https:\u002F\u002Fgithub.com\u002Froohe\u002Fagentic-super-skills\u002Fblob\u002Fmaster\u002Fskills_library\u002Fwrite-validation-documentation\u002FSKILL.md",[],[]]