[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M698RZMX7SWKTNPQAZFR8VNY":3,"skill-same:01M698RZMX7SWKTNPQAZFR8VNY":68},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":34,"linkOnly":35,"markdownContent":36,"markdownBody":37,"frontMatter":38,"refName":39,"commitSha":40,"skillDirectory":41,"forksCount":42,"repositoryHtmlUrl":43,"repositoryHomepageUrl":44,"ownerHtmlUrl":45,"ownerBlogUrl":44,"ownerDescription":46,"updatedAt":47,"install":48,"resources":61},"01M698RZMX7SWKTNPQAZFR8VNY","release-openclaw-announcement",null,"Draft or post OpenClaw beta, stable, or extended-stable Discord release announcements from changelog, tag, registry, and validation evidence. Use when announcing a release, release candidate, or asking what users should test after an OpenClaw release.","openclaw\u002Fopenclaw","openclaw","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F252820863?v=4","01M698P3FSAZ6B4R928ZF19KPT","01M698PDMDRVH56MV30D253NFP",394302,"MIT","https:\u002F\u002Fgithub.com\u002Fopenclaw\u002Fopenclaw\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Frelease-openclaw-announcement\u002FSKILL.md",[],[18,19,20,9,21,22,23,24,25,26,27,28,29,30,31,32,33],"release openclaw announcement","announcement","release","test","discord","registry","validation","changelog","beta","use","evidence","draft","users","post","candidate","when","2026-11-10 10:12:30",false,"---\nname: release-openclaw-announcement\ndescription: \"Draft or post OpenClaw beta, stable, or extended-stable Discord release announcements from changelog, tag, registry, and validation evidence. Use when announcing a release, release candidate, or asking what users should test after an OpenClaw release.\"\n---\n\n# OpenClaw Release Announcement\n\nUse with `release-openclaw-maintainer` after a release is live.\nUse with `$discord-user-post` when actually posting to Discord as the logged-in\nuser.\n\n## Evidence First\n\nBefore drafting focus areas, read real release evidence:\n\n1. GitHub release body and immutable tag; for extended-stable, also confirm the\n   npm\u002Fcontainer-only scope and non-Latest classification.\n2. The released base version's `CHANGELOG\u002F\u003Cversion>.md` and contribution\n   record, resolved with `node scripts\u002Frelease-changelog.mjs read --version \u003Cversion> [--ref \u003Csha-or-tag>]`\n   (add `--record` for accounting). The shared\n   resolver reads historical monolithic tags; current `CHANGELOG.md` is an\n   index. After approved docs publication, read the complete docs mirror and\n   frozen record rather than treating the compact GitHub body as full notes.\n3. Commits since the previous shipped version or the operator-specified base.\n4. Registry\u002Fpackage metadata for the exact version and current dist-tag.\n5. Validation status that is relevant to user confidence.\n\nDo not claim a full changelog audit unless you did it. If you only read the\ngenerated release notes or selected changelog section, say that and either audit\nproperly or draft with that limitation.\n\nFor beta focus areas, prioritize user-observable changes over internal test or\nCI mechanics:\n\n- install\u002Fupdate paths\n- OS\u002Fplatform-specific behavior\n- Gateway startup\u002Frestart, config, and runtime behavior\n- provider\u002Fmodel\u002Fruntime routing\n- plugin loading and local plugin development\n- channels and media paths\n- security\u002Fdata-loss\u002Fuser-impact fixes\n\nDo not let late release-branch fixes automatically dominate the announcement.\nIf the version includes a large delta from the previous shipped version, rank\nfocus areas by the whole release delta and expected user impact; mention late\nfixes in their natural category.\n\n## Required Copy\n\nEvery beta announcement must make beta status explicit and include:\n\n- exact version, e.g. `OpenClaw 2026.5.25-beta.1`\n- one-sentence risk framing: beta, useful for testing, not stable promotion\n- focused test areas derived from evidence, not guesswork\n- update command promoted near the top:\n  ```sh\n  openclaw update --channel beta --yes\n  openclaw --version\n  ```\n- fresh install path:\n  `Install from https:\u002F\u002Fopenclaw.ai`\n- GitHub release link\n- concise validation note, without making CI the headline\n\nDo not suggest npm install commands in beta announcements unless the operator\nexplicitly asks for npm-specific copy or troubleshooting text. It is fine to use\nregistry metadata as evidence; do not turn that into public install guidance.\n\nFor stable announcements, use the stable channel wording:\n\n```sh\nopenclaw update --channel stable --yes\nopenclaw --version\n```\n\nFresh installs still point to `https:\u002F\u002Fopenclaw.ai`.\n\nFor extended-stable, name the exact version and trailing month. Mention only\nobservable backports, and use:\n\n```sh\nopenclaw update --channel extended-stable\nopenclaw --version\n```\n\nDo not add `--yes`: users moving from newer regular stable must see the downgrade\nwarning because older versions may not understand newer configuration. Link the\nGitHub Release, but do not inherit regular stable macOS, Windows, ClawHub,\n`latest`, or website claims.\n\n## Style\n\n- Discord Markdown, no tables.\n- Keep it skimmable: short intro, bullets, commands, links.\n- Lead with what users can feel or test, not proof plumbing.\n- Mention validation only after install\u002Fupdate instructions.\n- Be specific about where feedback is useful.\n- Do not mention private local proof paths in public announcements.\n- Do not overstate unverified platforms, channels, or provider behavior.\n\n## Posting\n\nWhen asked to post, use `$discord-user-post` to operate the logged-in Discord\ndesktop app as the user. Resolve and visibly verify the exact server\u002Fchannel,\ninspect the final body, and request action-time confirmation before entering or\nsending it. Never use OpenClaw channel sends, bots, webhooks, relays, or tokens.\n","# OpenClaw Release Announcement\n\nUse with `release-openclaw-maintainer` after a release is live.\nUse with `$discord-user-post` when actually posting to Discord as the logged-in\nuser.\n\n## Evidence First\n\nBefore drafting focus areas, read real release evidence:\n\n1. GitHub release body and immutable tag; for extended-stable, also confirm the\n   npm\u002Fcontainer-only scope and non-Latest classification.\n2. The released base version's `CHANGELOG\u002F\u003Cversion>.md` and contribution\n   record, resolved with `node scripts\u002Frelease-changelog.mjs read --version \u003Cversion> [--ref \u003Csha-or-tag>]`\n   (add `--record` for accounting). The shared\n   resolver reads historical monolithic tags; current `CHANGELOG.md` is an\n   index. After approved docs publication, read the complete docs mirror and\n   frozen record rather than treating the compact GitHub body as full notes.\n3. Commits since the previous shipped version or the operator-specified base.\n4. Registry\u002Fpackage metadata for the exact version and current dist-tag.\n5. Validation status that is relevant to user confidence.\n\nDo not claim a full changelog audit unless you did it. If you only read the\ngenerated release notes or selected changelog section, say that and either audit\nproperly or draft with that limitation.\n\nFor beta focus areas, prioritize user-observable changes over internal test or\nCI mechanics:\n\n- install\u002Fupdate paths\n- OS\u002Fplatform-specific behavior\n- Gateway startup\u002Frestart, config, and runtime behavior\n- provider\u002Fmodel\u002Fruntime routing\n- plugin loading and local plugin development\n- channels and media paths\n- security\u002Fdata-loss\u002Fuser-impact fixes\n\nDo not let late release-branch fixes automatically dominate the announcement.\nIf the version includes a large delta from the previous shipped version, rank\nfocus areas by the whole release delta and expected user impact; mention late\nfixes in their natural category.\n\n## Required Copy\n\nEvery beta announcement must make beta status explicit and include:\n\n- exact version, e.g. `OpenClaw 2026.5.25-beta.1`\n- one-sentence risk framing: beta, useful for testing, not stable promotion\n- focused test areas derived from evidence, not guesswork\n- update command promoted near the top:\n  ```sh\n  openclaw update --channel beta --yes\n  openclaw --version\n  ```\n- fresh install path:\n  `Install from https:\u002F\u002Fopenclaw.ai`\n- GitHub release link\n- concise validation note, without making CI the headline\n\nDo not suggest npm install commands in beta announcements unless the operator\nexplicitly asks for npm-specific copy or troubleshooting text. It is fine to use\nregistry metadata as evidence; do not turn that into public install guidance.\n\nFor stable announcements, use the stable channel wording:\n\n```sh\nopenclaw update --channel stable --yes\nopenclaw --version\n```\n\nFresh installs still point to `https:\u002F\u002Fopenclaw.ai`.\n\nFor extended-stable, name the exact version and trailing month. Mention only\nobservable backports, and use:\n\n```sh\nopenclaw update --channel extended-stable\nopenclaw --version\n```\n\nDo not add `--yes`: users moving from newer regular stable must see the downgrade\nwarning because older versions may not understand newer configuration. Link the\nGitHub Release, but do not inherit regular stable macOS, Windows, ClawHub,\n`latest`, or website claims.\n\n## Style\n\n- Discord Markdown, no tables.\n- Keep it skimmable: short intro, bullets, commands, links.\n- Lead with what users can feel or test, not proof plumbing.\n- Mention validation only after install\u002Fupdate instructions.\n- Be specific about where feedback is useful.\n- Do not mention private local proof paths in public announcements.\n- Do not overstate unverified platforms, channels, or provider behavior.\n\n## Posting\n\nWhen asked to post, use `$discord-user-post` to operate the logged-in Discord\ndesktop app as the user. Resolve and visibly verify the exact server\u002Fchannel,\ninspect the final body, and request action-time confirmation before entering or\nsending it. Never use OpenClaw channel sends, bots, webhooks, relays, or tokens.\n",{"name":5,"description":7},"main","f1c93577085244aa96aa87b53a2df9b59d293bd7",".agents\u002Fskills\u002Frelease-openclaw-announcement",82862,"https:\u002F\u002Fgithub.com\u002Fopenclaw\u002Fopenclaw","https:\u002F\u002Fopenclaw.ai","https:\u002F\u002Fgithub.com\u002Fopenclaw","Your personal, open source AI assistant.","2026-11-11 08:46:30",{"source":8,"skillName":5,"commands":49,"prompt":59,"zipAvailable":60},[50,53,56],{"tool":51,"command":52},"npx","npx skills add openclaw\u002Fopenclaw --skill release-openclaw-announcement",{"tool":54,"command":55},"bunx","bunx skills add openclaw\u002Fopenclaw --skill release-openclaw-announcement",{"tool":57,"command":58},"pnpm","pnpm dlx skills add openclaw\u002Fopenclaw --skill release-openclaw-announcement","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fopenclaw\u002Fopenclaw\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Frelease-openclaw-announcement\u002FSKILL.md",true,[62],{"path":63,"resourceType":64,"resourceTypeDesc":65,"sizeBytes":66,"sourceHtmlUrl":67},"agents\u002Fopenai.yaml","REFERENCE","参考文档",347,"https:\u002F\u002Fgithub.com\u002Fopenclaw\u002Fopenclaw\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Frelease-openclaw-announcement\u002Fagents\u002Fopenai.yaml",[69,75,98,116,138,162],{"skillNo":70,"name":71,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":34},"01M698VP84FNM6G9MR1HPX7MF7","lobster","https:\u002F\u002Fgithub.com\u002Fopenclaw\u002Fopenclaw\u002Fblob\u002Fmain\u002Fextensions\u002Flobster\u002FSKILL.md",[],[71],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":34},"01M698YY8QGQ7S8TJNKJG6VTPH","xurl","xurl CLI for authenticated X posts, replies, reads\u002Fsearch, DMs, media upload, followers, auth status, or raw v2 API calls.","https:\u002F\u002Fgithub.com\u002Fopenclaw\u002Fopenclaw\u002Fblob\u002Fmain\u002Fskills\u002Fxurl\u002FSKILL.md",[],[77,82,83,84,85,86,87,88,89,90,91,92,93,94,95,96,97],"for","api","calls","replies","posts","upload","tap","install","brew","node","Media","search","npm","status","auth","cli",{"skillNo":99,"name":100,"nameZh":6,"description":101,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":102,"categories":103,"keywords":104,"publishedAt":34},"01M698YWT1CJ0WK88WB909R9RT","weather","Current weather and forecasts with web_fetch, falling back to wttr.in curl for locations, rain, temperature, travel planning.","https:\u002F\u002Fgithub.com\u002Fopenclaw\u002Fopenclaw\u002Fblob\u002Fmain\u002Fskills\u002Fweather\u002FSKILL.md",[],[100,105,106,89,107,90,108,109,110,111,112,113,82,114,115],"travel planning","travel","fetch","curl","https","help","planning","web","back","temperature","with",{"skillNo":117,"name":118,"nameZh":6,"description":119,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":120,"categories":121,"keywords":127,"publishedAt":34},"01M698YV2Q0R0JJKAWGFS21K0N","visualize","Create inline visuals for code and explanations, or author persistent OpenClaw dashboard widgets with show_widget.","https:\u002F\u002Fgithub.com\u002Fopenclaw\u002Fopenclaw\u002Fblob\u002Fmain\u002Fskills\u002Fvisualize\u002FSKILL.md",[122],{"categoryNo":123,"categoryName":124,"taxonomyType":125,"taxonomyTypeDesc":126},"01JBSEEDCAT000000000000033","数据分析师","PROFESSION","适用职业",[118,128,129,130,131,82,115,132,133,134,135,136,9,137],"widgets","openclaw dashboard","author","inline","show","code","create","visuals","dashboard","widget",{"skillNo":139,"name":140,"nameZh":6,"description":141,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":142,"categories":143,"keywords":152,"publishedAt":34},"01M698YS2TRJH9ENG28HD9CD87","trello","Manage Trello boards, lists, and cards via the Trello REST API.","https:\u002F\u002Fgithub.com\u002Fopenclaw\u002Fopenclaw\u002Fblob\u002Fmain\u002Fskills\u002Ftrello\u002FSKILL.md",[144,149],{"categoryNo":145,"categoryName":146,"taxonomyType":147,"taxonomyTypeDesc":148},"01JBSEEDCAT000000000000010","后端与接口","SCENARIO","使用场景",{"categoryNo":150,"categoryName":151,"taxonomyType":125,"taxonomyTypeDesc":126},"01JBSEEDCAT000000000000030","开发工程师",[140,109,153,154,155,156,157,158,89,90,159,108,83,160,161],"cloud","manage","via","rest api","token","atlassian","jq","REST","developer",{"skillNo":163,"name":164,"nameZh":6,"description":165,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":166,"categories":167,"keywords":168,"publishedAt":34},"01M698YQ9Q3M4W78EWV2KSCSVW","tmux","Control tmux sessions\u002Fpanes for interactive CLIs: list, capture output, send keys, paste text, monitor prompts.","https:\u002F\u002Fgithub.com\u002Fopenclaw\u002Fopenclaw\u002Fblob\u002Fmain\u002Fskills\u002Ftmux\u002FSKILL.md",[],[164,89,169,170,82,171,172,173,174,175,176,177,90,178,179,180,181,182,183],"send","darwin","keys","paste","output","control","prompts","interactive","list","capture","panes","text","monitor","sessions","linux"]