[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6P8NF1M37447A62Q9XR7D94":3,"skill-same:01M6P8NF1M37447A62Q9XR7D94":65},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":38,"linkOnly":39,"markdownContent":40,"markdownBody":41,"frontMatter":42,"refName":43,"commitSha":44,"skillDirectory":45,"forksCount":46,"repositoryHtmlUrl":47,"repositoryHomepageUrl":48,"ownerHtmlUrl":49,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":50,"install":51,"resources":64},"01M6P8NF1M37447A62Q9XR7D94","chatto-release-announcement",null,"Draft a concise Chatto release announcement in Markdown from a release PR, tag, or version. Use for announcement posts, including beta releases; use chatto-release-notes for stable release pages on the docs website.","chattocorp\u002Fchatto","chattocorp","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F261891647?v=4","01M6P8ECJF78VVQ1TJBW2JAWQ8","ChattoCorp GmbH","01M6P8ECPWHQVQBB8XNCRR70B9",2972,"AGPL-3.0","https:\u002F\u002Fgithub.com\u002Fchattocorp\u002Fchatto\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fchatto-release-announcement\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37],"announcement","release announcement","release","chatto release announcement","docs","website","markdown","releases","concise","notes","draft","version","use","pages","beta","for","pr","release-notes","posts","2026-11-10 10:12:30",false,"---\nname: chatto-release-announcement\ndescription: Draft a concise Chatto release announcement in Markdown from a release PR, tag, or version. Use for announcement posts, including beta releases; use chatto-release-notes for stable release pages on the docs website.\n---\n\n# Chatto Release Announcement\n\nWrite a short announcement for Chatto users and operators. Return Markdown\nin the conversation unless the user requests a file or another destination.\nDrafting an announcement does not include publishing it.\n\n## Output\n\nReturn only the release announcement. Do not add a preface, research summary,\nsource list, completion message, or follow-up offer. Do not send progress\nmessages unless higher-priority instructions require them.\n\nUse plain Markdown, or wrap the complete announcement in one `markdown` code\nblock for easy copying. When using a code block, put no text outside it.\n\n## Establish The Release Scope\n\n- Use the release PR, tag, or version supplied by the user. Preserve the full\n  version, including its beta suffix.\n- For a beta announcement, compare with the preceding beta. For a stable\n  announcement, compare with the preceding stable release, unless the user\n  specifies another range.\n- Read the release PR and changelog to identify candidate changes. Inspect\n  the underlying feature and fix PRs or commits for details. A generated release\n  PR normally contains version and changelog edits, not the implementation.\n- Check source code or product documentation when the reader impact, platform\n  scope, compatibility, or required action is unclear. Do not infer these\n  details from commit titles alone.\n- Include only changes in the target release. Distinguish shipped behavior\n  from proposals, incomplete work, and follow-up tasks.\n\n## Select And Write\n\n- Include only the most noteworthy changes: useful new behavior, significant\n  fixes, operational improvements, and required upgrade actions. This is not\n  a complete changelog.\n- Use focused, pragmatic wording and ASD-STE100 Simplified Technical English\n  where applicable. Use short sentences, active voice, and concrete terms.\n- State what changes for the reader and why it matters. Keep each bullet to\n  one or two short sentences. Use normal text lines or plain bullets. Do not\n  use bold titles or a \"Title: explanation\" format, except for the required\n  `**Breaking Change:**` marker.\n- Omit marketing language, implementation inventories, test reports, internal\n  refactors, and routine dependency or CI changes.\n- Do not include PR or issue links or numbers in the announcement. Keep the\n  research evidence separate from the post.\n- Preserve material limits. Do not describe a restricted importer as a complete\n  migration solution, a platform-specific fix as universal, or bounded upload\n  retries as recovery across application restarts.\n- Omit routine replica rollout warnings, including instructions to shut down\n  old replicas first or upgrade all replicas before using a feature.\n\n## Structure\n\nUse a release title and, when useful, one short introductory sentence. Group\nthe selected changes in this order:\n\n1. **Desktop app**: installation, updates, native integration, and desktop-only\n   fixes. Name the affected operating system.\n2. **For users**: chat, rooms, notifications, attachments, and other shared\n   client behavior.\n3. **For robots**: bots, automation, MCP tools, and integration APIs.\n4. **For administrators**: account and room management, permissions, moderation,\n   and authentication policy.\n5. **For operators**: deployment, resource use, server configuration, backups,\n   and migration tools.\n\nUse Markdown level-two headings for these sections, in the order above.\nOmit empty sections.\n\nList each breaking change in its corresponding section, with the exact prefix\n`**Breaking Change:**`. Do not add a separate breaking-changes section. Cover\nincompatible behavior, removed interfaces, changed requirements, and necessary\nmigration steps. State who is affected and what they must do. Make actions\nrequired before an upgrade clear.\n\nCheck for breaking changes even when commit titles have no breaking-change\nmarker. Do not label an additive feature or optional setting as breaking.\nKeep non-breaking rollout requirements with the relevant operator bullet.\nDo not repeat the same change across sections. Keep required migration details\nwith the change they concern.\n\n## Final Check\n\nVerify the release range, every included claim, and all required actions\nagainst the inspected evidence. Remove minor items and repeated explanations.\nDo not claim that a release is available unless its publication is confirmed.\n","# Chatto Release Announcement\n\nWrite a short announcement for Chatto users and operators. Return Markdown\nin the conversation unless the user requests a file or another destination.\nDrafting an announcement does not include publishing it.\n\n## Output\n\nReturn only the release announcement. Do not add a preface, research summary,\nsource list, completion message, or follow-up offer. Do not send progress\nmessages unless higher-priority instructions require them.\n\nUse plain Markdown, or wrap the complete announcement in one `markdown` code\nblock for easy copying. When using a code block, put no text outside it.\n\n## Establish The Release Scope\n\n- Use the release PR, tag, or version supplied by the user. Preserve the full\n  version, including its beta suffix.\n- For a beta announcement, compare with the preceding beta. For a stable\n  announcement, compare with the preceding stable release, unless the user\n  specifies another range.\n- Read the release PR and changelog to identify candidate changes. Inspect\n  the underlying feature and fix PRs or commits for details. A generated release\n  PR normally contains version and changelog edits, not the implementation.\n- Check source code or product documentation when the reader impact, platform\n  scope, compatibility, or required action is unclear. Do not infer these\n  details from commit titles alone.\n- Include only changes in the target release. Distinguish shipped behavior\n  from proposals, incomplete work, and follow-up tasks.\n\n## Select And Write\n\n- Include only the most noteworthy changes: useful new behavior, significant\n  fixes, operational improvements, and required upgrade actions. This is not\n  a complete changelog.\n- Use focused, pragmatic wording and ASD-STE100 Simplified Technical English\n  where applicable. Use short sentences, active voice, and concrete terms.\n- State what changes for the reader and why it matters. Keep each bullet to\n  one or two short sentences. Use normal text lines or plain bullets. Do not\n  use bold titles or a \"Title: explanation\" format, except for the required\n  `**Breaking Change:**` marker.\n- Omit marketing language, implementation inventories, test reports, internal\n  refactors, and routine dependency or CI changes.\n- Do not include PR or issue links or numbers in the announcement. Keep the\n  research evidence separate from the post.\n- Preserve material limits. Do not describe a restricted importer as a complete\n  migration solution, a platform-specific fix as universal, or bounded upload\n  retries as recovery across application restarts.\n- Omit routine replica rollout warnings, including instructions to shut down\n  old replicas first or upgrade all replicas before using a feature.\n\n## Structure\n\nUse a release title and, when useful, one short introductory sentence. Group\nthe selected changes in this order:\n\n1. **Desktop app**: installation, updates, native integration, and desktop-only\n   fixes. Name the affected operating system.\n2. **For users**: chat, rooms, notifications, attachments, and other shared\n   client behavior.\n3. **For robots**: bots, automation, MCP tools, and integration APIs.\n4. **For administrators**: account and room management, permissions, moderation,\n   and authentication policy.\n5. **For operators**: deployment, resource use, server configuration, backups,\n   and migration tools.\n\nUse Markdown level-two headings for these sections, in the order above.\nOmit empty sections.\n\nList each breaking change in its corresponding section, with the exact prefix\n`**Breaking Change:**`. Do not add a separate breaking-changes section. Cover\nincompatible behavior, removed interfaces, changed requirements, and necessary\nmigration steps. State who is affected and what they must do. Make actions\nrequired before an upgrade clear.\n\nCheck for breaking changes even when commit titles have no breaking-change\nmarker. Do not label an additive feature or optional setting as breaking.\nKeep non-breaking rollout requirements with the relevant operator bullet.\nDo not repeat the same change across sections. Keep required migration details\nwith the change they concern.\n\n## Final Check\n\nVerify the release range, every included claim, and all required actions\nagainst the inspected evidence. Remove minor items and repeated explanations.\nDo not claim that a release is available unless its publication is confirmed.\n",{"name":5,"description":7},"main","1f45fd1ee2a2fb409fce47906fcf419bbda498bd",".agents\u002Fskills\u002Fchatto-release-announcement",152,"https:\u002F\u002Fgithub.com\u002Fchattocorp\u002Fchatto","https:\u002F\u002Fchatto.run","https:\u002F\u002Fgithub.com\u002Fchattocorp","2026-11-15 04:17:01",{"source":8,"skillName":5,"commands":52,"prompt":62,"zipAvailable":63},[53,56,59],{"tool":54,"command":55},"npx","npx skills add chattocorp\u002Fchatto --skill chatto-release-announcement",{"tool":57,"command":58},"bunx","bunx skills add chattocorp\u002Fchatto --skill chatto-release-announcement",{"tool":60,"command":61},"pnpm","pnpm dlx skills add chattocorp\u002Fchatto --skill chatto-release-announcement","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fchattocorp\u002Fchatto\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fchatto-release-announcement\u002FSKILL.md",true,[],[66,87,105,120,144,170],{"skillNo":67,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":70,"categories":71,"keywords":82,"publishedAt":38},"01M6P8S7F1NYMKD9PW2RGZ0B2P","writing-tests","Instructions and hints for writing tests.","https:\u002F\u002Fgithub.com\u002Fchattocorp\u002Fchatto\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fwriting-tests\u002FSKILL.md",[72,77],{"categoryNo":73,"categoryName":74,"taxonomyType":75,"taxonomyTypeDesc":76},"01JBSEEDCAT000000000000018","写作与文案","SCENARIO","使用场景",{"categoryNo":78,"categoryName":79,"taxonomyType":80,"taxonomyTypeDesc":81},"01JBSEEDCAT000000000000036","内容创作者","PROFESSION","适用职业",[83,84,85,86,34],"writing","writing tests","tests","instructions",{"skillNo":88,"name":89,"nameZh":6,"description":90,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":91,"categories":92,"keywords":96,"publishedAt":38},"01M6P8S131Q068WC04FS0YW3RR","update-project-dependencies","Update Chatto Go and frontend dependencies within their compatible version ranges, then run tests.","https:\u002F\u002Fgithub.com\u002Fchattocorp\u002Fchatto\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fupdate-project-dependencies\u002FSKILL.md",[93],{"categoryNo":94,"categoryName":95,"taxonomyType":75,"taxonomyTypeDesc":76},"01JBSEEDCAT000000000000009","前端开发",[97,98,99,100,101,102,103,104,30,85],"dependencies","update","project","update project dependencies","frontend","go","run tests","run",{"skillNo":106,"name":107,"nameZh":6,"description":108,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":109,"categories":110,"keywords":111,"publishedAt":38},"01M6P8RERB7E3KYD4PW98D94SR","svelte-docs","Look up official Svelte, SvelteKit, and Svelte CLI documentation.","https:\u002F\u002Fgithub.com\u002Fchattocorp\u002Fchatto\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fsvelte-docs\u002FSKILL.md",[],[112,113,23,114,115,116,117,118,119],"svelte","svelte docs","look","cli","official","documentation","sveltekit","up",{"skillNo":121,"name":122,"nameZh":6,"description":123,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":124,"categories":125,"keywords":126,"publishedAt":38},"01M6P8RA0PS8DFAR8GXMB1CBFN","svelte-core-bestpractices","Guidance on writing fast, robust, modern Svelte code. Load this skill whenever in a Svelte project and asked to write\u002Fedit or analyze a Svelte component or module. Covers reactivity, event handling, styling, integration with libraries and more.","https:\u002F\u002Fgithub.com\u002Fchattocorp\u002Fchatto\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fsvelte-core-bestpractices\u002FSKILL.md",[],[112,127,128,129,130,131,99,132,133,134,135,136,137,138,139,140,141,142,83,143],"svelte core bestpractices","core","with","event","module","guidance","styling","edit","write","analyze","more","load","component","integration","code","libraries","fast",{"skillNo":145,"name":146,"nameZh":6,"description":147,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":148,"categories":149,"keywords":156,"publishedAt":38},"01M6P8R685PAMMR1DD530NGY40","svelte-code-writer","CLI tools for Svelte 5 documentation lookup and code analysis. MUST be used whenever creating, editing or analyzing any Svelte component (.svelte) or Svelte module (.svelte.ts\u002F.svelte.js). If possible, this skill should be executed within the svelte-file-editor agent for optimal results.","https:\u002F\u002Fgithub.com\u002Fchattocorp\u002Fchatto\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fsvelte-code-writer\u002FSKILL.md",[150,153],{"categoryNo":151,"categoryName":152,"taxonomyType":75,"taxonomyTypeDesc":76},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":154,"categoryName":155,"taxonomyType":80,"taxonomyTypeDesc":81},"01JBSEEDCAT000000000000030","开发工程师",[141,157,112,158,139,159,115,117,160,34,161,131,162,163,164,165,166,167,168,169],"svelte code writer","writer","editor","svelte 5","code analysis","results","editing","js","documentation lookup","analysis","Tools","analyzing","file",{"skillNo":171,"name":172,"nameZh":6,"description":173,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":174,"categories":175,"keywords":176,"publishedAt":38},"01M6P8QN03VSSHF538WV0E701T","session-wrap-up","Review a completed, paused, or blocked coding-agent session to identify friction, mistakes, near misses, missing context, and opportunities to improve future work. Use when the user asks to wrap up, run a retrospective, explain what issues the agent faced, capture lessons learned, or recommend improvements to repository instructions, documentation, skills, tooling, tests, or workflows. Produce an evidence-based, propose-only report; do not apply follow-up changes unless the user asks.","https:\u002F\u002Fgithub.com\u002Fchattocorp\u002Fchatto\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fsession-wrap-up\u002FSKILL.md",[],[177,178,119,179,180,181,182,183,184,185,186,187,188,189,190,191,192,193,104,117,194,195],"wrap","session wrap","session","session wrap up","wrap up","Coding-Agent","agent session","when","recommend","near","follow-up","learned","only","work","improve","repository","issues","workflows","review"]