[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M78PF8DVTF8P9QFT6G0SW80Z":3,"skill-same:01M78PF8DVTF8P9QFT6G0SW80Z":46},{"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":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":29,"ownerHtmlUrl":30,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":31,"install":32,"resources":45},"01M78PF8DVTF8P9QFT6G0SW80Z","chatto-release-checklist",null,"Check Chatto release readiness, including release metadata, upgrade guidance, and docs website consistency. Use when preparing or reviewing a Chatto release or release PR.","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-checklist\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: chatto-release-checklist\ndescription: Check Chatto release readiness, including release metadata, upgrade guidance, and docs website consistency. Use when preparing or reviewing a Chatto release or release PR.\n---\n\n# Chatto Release Checklist\n\nRead [the release process](..\u002F..\u002F..\u002Fdocs\u002FRELEASING.md). Paths below are relative to\nthe repository root. This checklist applies to Chatto, not the independently\nversioned products and libraries in this repository.\n\n## Before Publication\n\nDuring release preparation or PR review, check the proposed release commit\nand available CI evidence. Mark publication checks as pending until publication\noccurs; missing published artifacts at this stage are not failures.\n\n- Identify the target version and whether it is planned, prerelease, or stable\n  from Sweet Release state, the release PR, and published tags or releases.\n  Check that version targets and changelog entries agree with that state.\n- Confirm the intended source commit. If the tag exists, verify that it points\n  to the commit that introduced the version. Check that workflow runs use\n  that tag and commit. Do not move published tags.\n- Check that release notes describe the changes since the previous stable\n  release and include required upgrade actions. Use\n  [chatto-release-notes](..\u002Fchatto-release-notes\u002FSKILL.md) when writing or\n  updating the release page.\n- Check required CI results for the release commit. Distinguish failed checks\n  from checks that are still running or waiting for approval.\n\n## Compatibility And Upgrades\n\n- Use [chatto-api-compatibility](..\u002Fchatto-api-compatibility\u002FSKILL.md) for\n  public API and protocol changes since the previous stable release.\n- Check changes to `MINIMUM_SUPPORTED_SERVER_VERSION` and\n  `MINIMUM_CONNECTABLE_SERVER_VERSION` against root `AGENTS.md`. Verify the\n  required PR labels and explanations, including the justification and\n  operator upgrade action for a connection-threshold increase.\n- Check evidence of upgrades from the previous stable release, especially\n  when persisted events, schemas, storage, or migrations change. State the\n  source and target versions, what was tested, and the results. Flag missing\n  upgrade evidence; fresh-install tests alone do not verify upgrades.\n- Confirm that release notes and operator guidance contain the required\n  migration actions and any supported rollback limits.\n\n## Docs Website\n\nWhen preparing or reviewing a Chatto release, check the docs website as well\nas the release page. Read `docs\u002FRELEASING.md#documentation-channels` to\ndistinguish stable documentation from development documentation.\n\n- Check the homepage's `Release Notes` action in\n  `apps\u002Fdocs-website\u002Fsrc\u002Fcontent\u002Fdocs\u002Findex.mdx`. It must link to the release\n  page for the latest stable minor version represented by the site. Preparing\n  an unreleased page alone does not make it the latest stable release.\n- Check release navigation in `apps\u002Fdocs-website\u002Fastro.config.mjs` and links\n  from guides to release notes. Verify that target pages and fragments exist\n  and match the release discussed. Preserve intentional historical links.\n- Check release titles, descriptions, hero status, version labels, and GitHub\n  release links against the release state. Check installation examples,\n  upgrade guidance, and compatibility guidance for stale version references\n  or claims that conflict with the release notes.\n- Follow the human-authored page rules in `apps\u002Fdocs-website\u002FAGENTS.md`.\n  Report required corrections to protected pages unless the user has requested\n  those edits. For review-only tasks, report findings without edits.\n- Verify changed navigation links in a local browser preview. If checking a\n  deployed site, report its channel and distinguish deployed behavior from\n  local changes. Stable docs corrections ship with the next patch release.\n\n## After Publication\n\nUse [the release process](..\u002F..\u002F..\u002Fdocs\u002FRELEASING.md) for the expected\nartifacts and publication workflows. Check each applicable target separately:\n\n- Server archives and checksums on the GitHub release.\n- Server and frontend container images in GHCR.\n- Desktop packages and checksums, with successful signing verification for\n  Windows and signing and notarisation for macOS.\n- The `@chatto\u002Fclient` npm package.\n- The Homebrew update and stable docs build for a stable release. Verify the\n  deployed stable docs version and release links after deployment.\n- The independent iOS TestFlight workflow and upload result.\n\nConfirm that artifacts and workflow results match the intended version and\nsource commit. Check GitHub's draft and prerelease status; only the highest\nstable Chatto version must claim **Latest**. A successful server workflow or\nGitHub release does not prove that every publication target succeeded.\n\nReport each target as verified, pending, failed, or not applicable, with\nevidence or the reason. Follow the release process for partial publication\nand retries; do not rebuild a published version with changed contents.\n\n## Verification And Report\n\nRun `mise x -- pnpm --filter docs-website build` after page edits. Report\nfindings, checks run, and checks still needed. Do not claim release readiness\nfrom documentation checks alone. This checklist does not authorize tagging,\npublication, deployment, or approval of release workflows.\n","# Chatto Release Checklist\n\nRead [the release process](..\u002F..\u002F..\u002Fdocs\u002FRELEASING.md). Paths below are relative to\nthe repository root. This checklist applies to Chatto, not the independently\nversioned products and libraries in this repository.\n\n## Before Publication\n\nDuring release preparation or PR review, check the proposed release commit\nand available CI evidence. Mark publication checks as pending until publication\noccurs; missing published artifacts at this stage are not failures.\n\n- Identify the target version and whether it is planned, prerelease, or stable\n  from Sweet Release state, the release PR, and published tags or releases.\n  Check that version targets and changelog entries agree with that state.\n- Confirm the intended source commit. If the tag exists, verify that it points\n  to the commit that introduced the version. Check that workflow runs use\n  that tag and commit. Do not move published tags.\n- Check that release notes describe the changes since the previous stable\n  release and include required upgrade actions. Use\n  [chatto-release-notes](..\u002Fchatto-release-notes\u002FSKILL.md) when writing or\n  updating the release page.\n- Check required CI results for the release commit. Distinguish failed checks\n  from checks that are still running or waiting for approval.\n\n## Compatibility And Upgrades\n\n- Use [chatto-api-compatibility](..\u002Fchatto-api-compatibility\u002FSKILL.md) for\n  public API and protocol changes since the previous stable release.\n- Check changes to `MINIMUM_SUPPORTED_SERVER_VERSION` and\n  `MINIMUM_CONNECTABLE_SERVER_VERSION` against root `AGENTS.md`. Verify the\n  required PR labels and explanations, including the justification and\n  operator upgrade action for a connection-threshold increase.\n- Check evidence of upgrades from the previous stable release, especially\n  when persisted events, schemas, storage, or migrations change. State the\n  source and target versions, what was tested, and the results. Flag missing\n  upgrade evidence; fresh-install tests alone do not verify upgrades.\n- Confirm that release notes and operator guidance contain the required\n  migration actions and any supported rollback limits.\n\n## Docs Website\n\nWhen preparing or reviewing a Chatto release, check the docs website as well\nas the release page. Read `docs\u002FRELEASING.md#documentation-channels` to\ndistinguish stable documentation from development documentation.\n\n- Check the homepage's `Release Notes` action in\n  `apps\u002Fdocs-website\u002Fsrc\u002Fcontent\u002Fdocs\u002Findex.mdx`. It must link to the release\n  page for the latest stable minor version represented by the site. Preparing\n  an unreleased page alone does not make it the latest stable release.\n- Check release navigation in `apps\u002Fdocs-website\u002Fastro.config.mjs` and links\n  from guides to release notes. Verify that target pages and fragments exist\n  and match the release discussed. Preserve intentional historical links.\n- Check release titles, descriptions, hero status, version labels, and GitHub\n  release links against the release state. Check installation examples,\n  upgrade guidance, and compatibility guidance for stale version references\n  or claims that conflict with the release notes.\n- Follow the human-authored page rules in `apps\u002Fdocs-website\u002FAGENTS.md`.\n  Report required corrections to protected pages unless the user has requested\n  those edits. For review-only tasks, report findings without edits.\n- Verify changed navigation links in a local browser preview. If checking a\n  deployed site, report its channel and distinguish deployed behavior from\n  local changes. Stable docs corrections ship with the next patch release.\n\n## After Publication\n\nUse [the release process](..\u002F..\u002F..\u002Fdocs\u002FRELEASING.md) for the expected\nartifacts and publication workflows. Check each applicable target separately:\n\n- Server archives and checksums on the GitHub release.\n- Server and frontend container images in GHCR.\n- Desktop packages and checksums, with successful signing verification for\n  Windows and signing and notarisation for macOS.\n- The `@chatto\u002Fclient` npm package.\n- The Homebrew update and stable docs build for a stable release. Verify the\n  deployed stable docs version and release links after deployment.\n- The independent iOS TestFlight workflow and upload result.\n\nConfirm that artifacts and workflow results match the intended version and\nsource commit. Check GitHub's draft and prerelease status; only the highest\nstable Chatto version must claim **Latest**. A successful server workflow or\nGitHub release does not prove that every publication target succeeded.\n\nReport each target as verified, pending, failed, or not applicable, with\nevidence or the reason. Follow the release process for partial publication\nand retries; do not rebuild a published version with changed contents.\n\n## Verification And Report\n\nRun `mise x -- pnpm --filter docs-website build` after page edits. Report\nfindings, checks run, and checks still needed. Do not claim release readiness\nfrom documentation checks alone. This checklist does not authorize tagging,\npublication, deployment, or approval of release workflows.\n",{"name":5,"description":7},"main","beb74f1d17da32345f51988dca20e2094c34d01f",".agents\u002Fskills\u002Fchatto-release-checklist",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":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add chattocorp\u002Fchatto --skill chatto-release-checklist",{"tool":38,"command":39},"bunx","bunx skills add chattocorp\u002Fchatto --skill chatto-release-checklist",{"tool":41,"command":42},"pnpm","pnpm dlx skills add chattocorp\u002Fchatto --skill chatto-release-checklist","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fchattocorp\u002Fchatto\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fchatto-release-checklist\u002FSKILL.md",true,[],[47,55,78,97,113,137],{"skillNo":48,"name":49,"nameZh":6,"description":50,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":51,"categories":52,"keywords":53,"publishedAt":54},"01M747DN6Q5J07Z2N6P1JEVASV","github","Work with GitHub issues, pull requests, and repository information for Chatto. Use for issue searches, bug reports, feature requests, issue updates, and GitHub access checks.","https:\u002F\u002Fgithub.com\u002Fchattocorp\u002Fchatto\u002Fblob\u002Fmain\u002Fexamples\u002Fbotto\u002F.agents\u002Fskills\u002Fgithub\u002FSKILL.md",[],[],"2026-11-11 15:11:14",{"skillNo":56,"name":57,"nameZh":6,"description":58,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":59,"categories":60,"keywords":71,"publishedAt":77},"01M6P8S7F1NYMKD9PW2RGZ0B2P","writing-tests","Instructions and hints for writing tests.","https:\u002F\u002Fgithub.com\u002Fchattocorp\u002Fchatto\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fwriting-tests\u002FSKILL.md",[61,66],{"categoryNo":62,"categoryName":63,"taxonomyType":64,"taxonomyTypeDesc":65},"01JBSEEDCAT000000000000018","写作与文案","SCENARIO","使用场景",{"categoryNo":67,"categoryName":68,"taxonomyType":69,"taxonomyTypeDesc":70},"01JBSEEDCAT000000000000036","内容创作者","PROFESSION","适用职业",[72,73,74,75,76],"tests","writing","writing tests","instructions","for","2026-11-10 10:12:30",{"skillNo":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":87,"publishedAt":77},"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",[84],{"categoryNo":85,"categoryName":86,"taxonomyType":64,"taxonomyTypeDesc":65},"01JBSEEDCAT000000000000009","前端开发",[88,89,90,91,92,93,94,95,96,72],"project","dependencies","update","update project dependencies","run tests","version","go","run","frontend",{"skillNo":98,"name":99,"nameZh":6,"description":100,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":101,"categories":102,"keywords":103,"publishedAt":77},"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",[],[104,105,106,107,108,109,110,111,112],"svelte","svelte docs","docs","up","documentation","official","cli","sveltekit","look",{"skillNo":114,"name":115,"nameZh":6,"description":116,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":117,"categories":118,"keywords":119,"publishedAt":77},"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",[],[120,121,104,122,123,124,125,126,88,73,127,128,129,130,131,132,133,134,135,136],"svelte core bestpractices","core","with","integration","guidance","fast","load","code","analyze","libraries","component","write","edit","styling","event","more","module",{"skillNo":138,"name":139,"nameZh":6,"description":140,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":141,"categories":142,"keywords":149,"publishedAt":77},"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",[143,146],{"categoryNo":144,"categoryName":145,"taxonomyType":64,"taxonomyTypeDesc":65},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":147,"categoryName":148,"taxonomyType":69,"taxonomyTypeDesc":70},"01JBSEEDCAT000000000000030","开发工程师",[104,127,150,151,152,76,153,136,154,155,156,108,130,110,157,158,159,160,161,162],"svelte code writer","writer","js","editing","analysis","file","code analysis","results","documentation lookup","editor","analyzing","svelte 5","Tools"]