[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M698T29X5K0BXXF1P14G05KX":3,"skill-same:01M698T29X5K0BXXF1P14G05KX":62},{"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},"01M698T29X5K0BXXF1P14G05KX","verify-release",null,"Verify regular or extended-stable OpenClaw releases against the exact publication surfaces, workflow identities, package provenance, and published CLI smoke tests expected for that release track.","openclaw\u002Fopenclaw","openclaw","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F252820863?v=4","01M698P3FSAZ6B4R928ZF19KPT","01M698PDMDRVH56MV30D253NFP",394406,"MIT","https:\u002F\u002Fgithub.com\u002Fopenclaw\u002Fopenclaw\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fverify-release\u002FSKILL.md",[],[18,19,20,21,22,23,24,25,26,27,28,29,30,31,32,9,33],"verify","release","verify release","surfaces","Publication","track","provenance","workflow","expected","smoke tests","package","tests","for","releases","smoke","cli","2026-11-10 10:12:30",false,"---\nname: verify-release\ndescription: \"Verify regular or extended-stable OpenClaw releases against the exact publication surfaces, workflow identities, package provenance, and published CLI smoke tests expected for that release track.\"\n---\n\n# Verify Release\n\nUse this when asked whether an OpenClaw release is fully released, published,\npromoted, smoke-tested, or live-verified. This is a verification skill, not a\npublish skill; use `$release-openclaw-maintainer` before changing release state.\n\n## Rules\n\n- Resolve short suffixes like `.27` to the concrete CalVer version from the\n  current date\u002Fcontext, then say the resolved version.\n- Resolve the track first. Both tracks use the shared GitHub Release evidence\n  ledger. Regular beta\u002Fstable also uses the platform graph; extended-stable\n  uses its canonical branch, npm selector, and Gateway surfaces. Do not require\n  one track's native or ClawHub artifacts from the other.\n- Verify live state. Do not trust local checkout state, release notes, or old\n  memory as current truth.\n- If the checkout is dirty or divergent, use it only for scripts\u002Freference.\n  For version metadata, fetch from GitHub release\u002Ftag or unpack the tag tarball\n  under `\u002Ftmp`.\n- Verify selected npm plugins published successfully before core npm.\n- Report ClawHub separately from core release readiness. Its pending or failed\n  publication\u002Fverification never blocks core, GitHub finalization, main\n  closeout, or the retrospective PR. Keep its exact run\u002Fattempt, owner, and next\n  action visible; do not call ClawHub complete without public-byte proof.\n- Never print secrets.\n- Keep the final terse: `yes\u002Fno`, evidence bullets, caveats, cleanup.\n\n## Regular beta\u002Fstable checks\n\nUse these checks only for the regular orchestrated release track.\n\n1. GitHub release:\n   - `gh release view v\u003CVERSION> --repo openclaw\u002Fopenclaw --json tagName,name,publishedAt,isDraft,isPrerelease,targetCommitish,url,body,assets`\n   - Confirm stable releases are not draft\u002Fprerelease.\n   - Confirm release body has npm, CI, plugin npm, ClawHub, mac\u002Fappcast evidence\n     links when expected.\n   - Confirm assets expected for stable mac releases are uploaded: zip, dmg,\n     dSYM, dependency evidence, immutable full-validation manifest,\n     postpublish evidence, and stable-main closeout manifest.\n   - Download each immutable evidence asset and its `.sha256` companion, then\n     verify the checksum before trusting the release record.\n2. Root npm:\n   - `npm view openclaw@\u003CVERSION> version dist-tags.latest dist.tarball dist.integrity time.\u003CVERSION> --json`\n   - `latest` must equal `\u003CVERSION>` for stable.\n   - Record tarball, integrity, publish time.\n   - Confirm the release postpublish evidence records\n     `npmRegistrySignaturesVerified: true` and\n     `npmProvenanceAttestationMatched: true`.\n3. Plugin publish set:\n   - Get exact tag metadata from GitHub, not the local checkout when dirty:\n     download `https:\u002F\u002Fapi.github.com\u002Frepos\u002Fopenclaw\u002Fopenclaw\u002Ftarball\u002Fv\u003CVERSION>`\n     into `\u002Ftmp\u002Fopenclaw-v\u003CVERSION>-src`.\n   - Derive the full expected npm and ClawHub package sets for the release track\n     with the canonical publication planners\u002Fcollector from the recorded release\n     Tooling SHA, using the exact tag's package metadata.\n     Do not count raw publish flags: `openclaw.build.bundledDist === true`\n     explicitly defers external publication even when publish flags are set.\n     Record deferred package names and reasons separately.\n   - Reconcile expected package identities, versions, and counts across original\n     publication, previously published versions, and selected recovery runs using\n     immutable publication plans, registry readback, and workflow jobs. A selected\n     recovery subset must not narrow the full expected release set:\n     `gh api repos\u002Fopenclaw\u002Fopenclaw\u002Factions\u002Fruns\u002F\u003CRUN>\u002Fjobs --paginate`.\n   - For each expected npm plugin, verify the planned version and npm selector\n     from that immutable publication plan. A regular beta publishes to `beta`;\n     do not require it to move `latest`. Verify any planned mirror tags separately.\n4. ClawHub (independent status, not a core or closeout gate):\n   - Check the Plugin ClawHub Release workflow conclusion and publish job count.\n     If pending or failed, record that state and its follow-up separately;\n     continue core verification and closeout without waiting.\n   - Use OpenClaw itself for live registry proof:\n     `openclaw plugins search \u003Cknown-plugin> --json`.\n   - Install one official plugin at the exact requested release version from\n     ClawHub in an isolated HOME:\n     `openclaw plugins install clawhub:@openclaw\u002Fmatrix@\u003CVERSION>`.\n     Prefer `matrix` unless that plugin is not in the expected set. ClawHub\n     versions belong in the spec; `--pin` is only supported for npm installs.\n5. Release workflows:\n   - Verify conclusions for release notes evidence links:\n     Full Release Validation, OpenClaw Release Checks, OpenClaw NPM Release,\n     Plugin NPM Release, mac preflight\u002Fvalidation\u002Fpublish when stable mac assets\n     are expected. Report Plugin ClawHub Release independently, even when its\n     result is still pending or failed.\n   - For stable, verify `OpenClaw Stable Main Closeout` succeeded and its\n     manifest records the matching release tag, current rollback drill, stable\n     soak, and blocking performance evidence.\n   - Summarize only relevant successful\u002Ffailed jobs; ignore routine skipped\n     optional lanes unless the release body promised them.\n6. Container registries:\n   - Resolve `VERCEL_VCR_IMAGE` from the repository variable and use the\n     trusted tooling checkout to run `scripts\u002Fcontainer-registry-readback.mjs`\n     with the exact version, both `ghcr.io\u002Fopenclaw\u002Fopenclaw` and\n     `docker.io\u002Fopenclaw\u002Fopenclaw`, and the Vercel image. Pass\n     `--include-browser` when the release Dockerfile includes that variant.\n   - Require every default, slim, browser, amd64, and arm64 immutable tag in all\n     three registries, matching cross-registry platform descriptors, and every\n     policy-owned moving alias at the immutable digest and descriptor set.\n     Beta intentionally has zero moving aliases; do not require a `beta`\n     container alias.\n   - Use existing Docker credential state for private Vercel reads. If it is\n     unavailable, report Vercel live readback as a gap rather than treating the\n     workflow conclusion as equivalent proof.\n\n## Extended-stable checks\n\nExtended-stable has a GitHub Release with shared release evidence but no native\nor ClawHub artifacts. Verify it alongside\nthe live tag, workflow, registry, provenance, and image state.\n\n1. **Identity:** require final `v\u003CVERSION>` at patch `33+`, with no suffix,\n   contained in `extended-stable\u002FYYYY.M.33`. Only an active candidate must equal\n   the tip. Root and every publishable official plugin must declare `\u003CVERSION>`.\n   Require the Git tag and a public, non-prerelease GitHub Release whose title\n   and canonical body match the tag. Require `isLatest=false`, the dependency\n   evidence, immutable Full Release Validation manifest, postpublish evidence,\n   and their checksums. Require no native or ClawHub assets.\n2. **Workflow chain:** find the successful parent release run plus its\n   preflight, complete validation, plugin npm, and core publish children.\n   Require a protected `release-publish\u002F*` parent and canonical `release-ci\u002F*`\n   validation producer with verified workflow SHA provenance. Validation must\n   use `rerun_group=all`, `release_profile=stable`, blocking soak\u002Fperformance,\n   and the saved attempt. Core publish must reference all three run IDs and bind\n   its manifest, workflow ref, and tarball digest to the release SHA.\n3. **Registry:** require exact and `extended-stable` selectors to return\n   `\u003CVERSION>` for root, every preflight `corePackageTarballs` entry, and every\n   `publishToNpm === true` official plugin derived from the tag. Compare the\n   plugin plan, jobs, and complete readback; never infer inventory from diffs.\n4. **Provenance:** from trusted current tooling, run\n   `node --import tsx scripts\u002Fopenclaw-npm-postpublish-verify.ts \u003CVERSION>`.\n   Require signatures, canonical-branch provenance, and publish\u002Fpreflight\n   digest binding to the release SHA. Preserve output and workflow URLs.\n5. **Docker:** run `scripts\u002Fcontainer-registry-readback.mjs` against\n   GHCR, Docker Hub, and the repository's `VERCEL_VCR_IMAGE`. Require exact\n   default, slim, browser, and architecture images, matching platform descriptor\n   sets, and only the three `extended-stable*` aliases at those immutable\n   digests. Separately verify attestations in GHCR and Docker Hub. Require the\n   successful `OpenClaw Release Publish` parent run and its completed Docker\n   verification. The normal route finalizes afterward; an explicitly requested\n   fast path may activate GitHub first. Repair aliases through current-main\n   `Docker Channel Promotion` for the exact tag, without rebuilding.\n6. **Recovery:** never republish. Use `promote_extended_stable` in the\n   `openclaw\u002Freleases` dist-tag workflow for the root selector (an unsuffixed\n   final patch `33+`) and approved credential-isolated tooling for others, then repeat\n   complete readback. Do not require ClawHub, native\u002Fmobile apps, website,\n   private dist-tags, or regular `latest`. Require shared release evidence, but\n   do not require regular native or ClawHub assets.\n\n## Published package smoke\n\nAfter the track-specific core publication checks pass, use a disposable\ninstallation\u002Fcache with isolated OpenClaw state. Do not wait for independent\nClawHub verification to run this smoke:\n\n- `npm exec --yes --package openclaw@\u003CVERSION> -- openclaw --version`.\n- Run at least one harmless command that touches the published CLI surface,\n  for example `plugins --help` or `gateway --help`.\n\nDo not start an extra local Gateway or run an ad hoc live model turn as a\npreliminary release check. Use the canonical release-validation workflows and\npublication evidence above; this does not remove any of their required lanes.\nRun additional manual live checks only when explicitly requested.\n\n## Caveats To Report\n\n- Dist-tag caveat: stable `latest` is release truth; if optional `beta` mirrors\n  still point at a beta version, report it as a caveat, not a stable-release\n  blocker, unless the user asked to verify beta promotion.\n- ClawHub caveat: distinguish “core release verified; ClawHub pending\u002Ffailed”\n  from “all selected publication surfaces verified.” The former still permits\n  main closeout and the retrospective PR.\n- Track caveat: name the track and intentionally absent surfaces. Do not call\n  missing regular-release artifacts an extended-stable failure.\n- Divergent checkout caveat: say when local source SHA differs from release tag\n  or origin and which live sources were used instead.\n","# Verify Release\n\nUse this when asked whether an OpenClaw release is fully released, published,\npromoted, smoke-tested, or live-verified. This is a verification skill, not a\npublish skill; use `$release-openclaw-maintainer` before changing release state.\n\n## Rules\n\n- Resolve short suffixes like `.27` to the concrete CalVer version from the\n  current date\u002Fcontext, then say the resolved version.\n- Resolve the track first. Both tracks use the shared GitHub Release evidence\n  ledger. Regular beta\u002Fstable also uses the platform graph; extended-stable\n  uses its canonical branch, npm selector, and Gateway surfaces. Do not require\n  one track's native or ClawHub artifacts from the other.\n- Verify live state. Do not trust local checkout state, release notes, or old\n  memory as current truth.\n- If the checkout is dirty or divergent, use it only for scripts\u002Freference.\n  For version metadata, fetch from GitHub release\u002Ftag or unpack the tag tarball\n  under `\u002Ftmp`.\n- Verify selected npm plugins published successfully before core npm.\n- Report ClawHub separately from core release readiness. Its pending or failed\n  publication\u002Fverification never blocks core, GitHub finalization, main\n  closeout, or the retrospective PR. Keep its exact run\u002Fattempt, owner, and next\n  action visible; do not call ClawHub complete without public-byte proof.\n- Never print secrets.\n- Keep the final terse: `yes\u002Fno`, evidence bullets, caveats, cleanup.\n\n## Regular beta\u002Fstable checks\n\nUse these checks only for the regular orchestrated release track.\n\n1. GitHub release:\n   - `gh release view v\u003CVERSION> --repo openclaw\u002Fopenclaw --json tagName,name,publishedAt,isDraft,isPrerelease,targetCommitish,url,body,assets`\n   - Confirm stable releases are not draft\u002Fprerelease.\n   - Confirm release body has npm, CI, plugin npm, ClawHub, mac\u002Fappcast evidence\n     links when expected.\n   - Confirm assets expected for stable mac releases are uploaded: zip, dmg,\n     dSYM, dependency evidence, immutable full-validation manifest,\n     postpublish evidence, and stable-main closeout manifest.\n   - Download each immutable evidence asset and its `.sha256` companion, then\n     verify the checksum before trusting the release record.\n2. Root npm:\n   - `npm view openclaw@\u003CVERSION> version dist-tags.latest dist.tarball dist.integrity time.\u003CVERSION> --json`\n   - `latest` must equal `\u003CVERSION>` for stable.\n   - Record tarball, integrity, publish time.\n   - Confirm the release postpublish evidence records\n     `npmRegistrySignaturesVerified: true` and\n     `npmProvenanceAttestationMatched: true`.\n3. Plugin publish set:\n   - Get exact tag metadata from GitHub, not the local checkout when dirty:\n     download `https:\u002F\u002Fapi.github.com\u002Frepos\u002Fopenclaw\u002Fopenclaw\u002Ftarball\u002Fv\u003CVERSION>`\n     into `\u002Ftmp\u002Fopenclaw-v\u003CVERSION>-src`.\n   - Derive the full expected npm and ClawHub package sets for the release track\n     with the canonical publication planners\u002Fcollector from the recorded release\n     Tooling SHA, using the exact tag's package metadata.\n     Do not count raw publish flags: `openclaw.build.bundledDist === true`\n     explicitly defers external publication even when publish flags are set.\n     Record deferred package names and reasons separately.\n   - Reconcile expected package identities, versions, and counts across original\n     publication, previously published versions, and selected recovery runs using\n     immutable publication plans, registry readback, and workflow jobs. A selected\n     recovery subset must not narrow the full expected release set:\n     `gh api repos\u002Fopenclaw\u002Fopenclaw\u002Factions\u002Fruns\u002F\u003CRUN>\u002Fjobs --paginate`.\n   - For each expected npm plugin, verify the planned version and npm selector\n     from that immutable publication plan. A regular beta publishes to `beta`;\n     do not require it to move `latest`. Verify any planned mirror tags separately.\n4. ClawHub (independent status, not a core or closeout gate):\n   - Check the Plugin ClawHub Release workflow conclusion and publish job count.\n     If pending or failed, record that state and its follow-up separately;\n     continue core verification and closeout without waiting.\n   - Use OpenClaw itself for live registry proof:\n     `openclaw plugins search \u003Cknown-plugin> --json`.\n   - Install one official plugin at the exact requested release version from\n     ClawHub in an isolated HOME:\n     `openclaw plugins install clawhub:@openclaw\u002Fmatrix@\u003CVERSION>`.\n     Prefer `matrix` unless that plugin is not in the expected set. ClawHub\n     versions belong in the spec; `--pin` is only supported for npm installs.\n5. Release workflows:\n   - Verify conclusions for release notes evidence links:\n     Full Release Validation, OpenClaw Release Checks, OpenClaw NPM Release,\n     Plugin NPM Release, mac preflight\u002Fvalidation\u002Fpublish when stable mac assets\n     are expected. Report Plugin ClawHub Release independently, even when its\n     result is still pending or failed.\n   - For stable, verify `OpenClaw Stable Main Closeout` succeeded and its\n     manifest records the matching release tag, current rollback drill, stable\n     soak, and blocking performance evidence.\n   - Summarize only relevant successful\u002Ffailed jobs; ignore routine skipped\n     optional lanes unless the release body promised them.\n6. Container registries:\n   - Resolve `VERCEL_VCR_IMAGE` from the repository variable and use the\n     trusted tooling checkout to run `scripts\u002Fcontainer-registry-readback.mjs`\n     with the exact version, both `ghcr.io\u002Fopenclaw\u002Fopenclaw` and\n     `docker.io\u002Fopenclaw\u002Fopenclaw`, and the Vercel image. Pass\n     `--include-browser` when the release Dockerfile includes that variant.\n   - Require every default, slim, browser, amd64, and arm64 immutable tag in all\n     three registries, matching cross-registry platform descriptors, and every\n     policy-owned moving alias at the immutable digest and descriptor set.\n     Beta intentionally has zero moving aliases; do not require a `beta`\n     container alias.\n   - Use existing Docker credential state for private Vercel reads. If it is\n     unavailable, report Vercel live readback as a gap rather than treating the\n     workflow conclusion as equivalent proof.\n\n## Extended-stable checks\n\nExtended-stable has a GitHub Release with shared release evidence but no native\nor ClawHub artifacts. Verify it alongside\nthe live tag, workflow, registry, provenance, and image state.\n\n1. **Identity:** require final `v\u003CVERSION>` at patch `33+`, with no suffix,\n   contained in `extended-stable\u002FYYYY.M.33`. Only an active candidate must equal\n   the tip. Root and every publishable official plugin must declare `\u003CVERSION>`.\n   Require the Git tag and a public, non-prerelease GitHub Release whose title\n   and canonical body match the tag. Require `isLatest=false`, the dependency\n   evidence, immutable Full Release Validation manifest, postpublish evidence,\n   and their checksums. Require no native or ClawHub assets.\n2. **Workflow chain:** find the successful parent release run plus its\n   preflight, complete validation, plugin npm, and core publish children.\n   Require a protected `release-publish\u002F*` parent and canonical `release-ci\u002F*`\n   validation producer with verified workflow SHA provenance. Validation must\n   use `rerun_group=all`, `release_profile=stable`, blocking soak\u002Fperformance,\n   and the saved attempt. Core publish must reference all three run IDs and bind\n   its manifest, workflow ref, and tarball digest to the release SHA.\n3. **Registry:** require exact and `extended-stable` selectors to return\n   `\u003CVERSION>` for root, every preflight `corePackageTarballs` entry, and every\n   `publishToNpm === true` official plugin derived from the tag. Compare the\n   plugin plan, jobs, and complete readback; never infer inventory from diffs.\n4. **Provenance:** from trusted current tooling, run\n   `node --import tsx scripts\u002Fopenclaw-npm-postpublish-verify.ts \u003CVERSION>`.\n   Require signatures, canonical-branch provenance, and publish\u002Fpreflight\n   digest binding to the release SHA. Preserve output and workflow URLs.\n5. **Docker:** run `scripts\u002Fcontainer-registry-readback.mjs` against\n   GHCR, Docker Hub, and the repository's `VERCEL_VCR_IMAGE`. Require exact\n   default, slim, browser, and architecture images, matching platform descriptor\n   sets, and only the three `extended-stable*` aliases at those immutable\n   digests. Separately verify attestations in GHCR and Docker Hub. Require the\n   successful `OpenClaw Release Publish` parent run and its completed Docker\n   verification. The normal route finalizes afterward; an explicitly requested\n   fast path may activate GitHub first. Repair aliases through current-main\n   `Docker Channel Promotion` for the exact tag, without rebuilding.\n6. **Recovery:** never republish. Use `promote_extended_stable` in the\n   `openclaw\u002Freleases` dist-tag workflow for the root selector (an unsuffixed\n   final patch `33+`) and approved credential-isolated tooling for others, then repeat\n   complete readback. Do not require ClawHub, native\u002Fmobile apps, website,\n   private dist-tags, or regular `latest`. Require shared release evidence, but\n   do not require regular native or ClawHub assets.\n\n## Published package smoke\n\nAfter the track-specific core publication checks pass, use a disposable\ninstallation\u002Fcache with isolated OpenClaw state. Do not wait for independent\nClawHub verification to run this smoke:\n\n- `npm exec --yes --package openclaw@\u003CVERSION> -- openclaw --version`.\n- Run at least one harmless command that touches the published CLI surface,\n  for example `plugins --help` or `gateway --help`.\n\nDo not start an extra local Gateway or run an ad hoc live model turn as a\npreliminary release check. Use the canonical release-validation workflows and\npublication evidence above; this does not remove any of their required lanes.\nRun additional manual live checks only when explicitly requested.\n\n## Caveats To Report\n\n- Dist-tag caveat: stable `latest` is release truth; if optional `beta` mirrors\n  still point at a beta version, report it as a caveat, not a stable-release\n  blocker, unless the user asked to verify beta promotion.\n- ClawHub caveat: distinguish “core release verified; ClawHub pending\u002Ffailed”\n  from “all selected publication surfaces verified.” The former still permits\n  main closeout and the retrospective PR.\n- Track caveat: name the track and intentionally absent surfaces. Do not call\n  missing regular-release artifacts an extended-stable failure.\n- Divergent checkout caveat: say when local source SHA differs from release tag\n  or origin and which live sources were used instead.\n",{"name":5,"description":7},"main","c6667b166c61bd125edeaab64ddc4a26f534a7e9",".agents\u002Fskills\u002Fverify-release",82884,"https:\u002F\u002Fgithub.com\u002Fopenclaw\u002Fopenclaw","https:\u002F\u002Fopenclaw.ai","https:\u002F\u002Fgithub.com\u002Fopenclaw","Your personal, open source AI assistant.","2026-11-13 03:01:37",{"source":8,"skillName":5,"commands":49,"prompt":59,"zipAvailable":60},[50,53,56],{"tool":51,"command":52},"npx","npx skills add openclaw\u002Fopenclaw --skill verify-release",{"tool":54,"command":55},"bunx","bunx skills add openclaw\u002Fopenclaw --skill verify-release",{"tool":57,"command":58},"pnpm","pnpm dlx skills add openclaw\u002Fopenclaw --skill verify-release","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fopenclaw\u002Fopenclaw\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fverify-release\u002FSKILL.md",true,[],[63,69,90,108,130,154],{"skillNo":64,"name":65,"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":66,"categories":67,"keywords":68,"publishedAt":34},"01M698VP84FNM6G9MR1HPX7MF7","lobster","https:\u002F\u002Fgithub.com\u002Fopenclaw\u002Fopenclaw\u002Fblob\u002Fmain\u002Fextensions\u002Flobster\u002FSKILL.md",[],[65],{"skillNo":70,"name":71,"nameZh":6,"description":72,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":73,"categories":74,"keywords":75,"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",[],[71,30,76,77,78,79,80,81,82,83,84,85,86,87,88,89,33],"api","calls","replies","posts","upload","tap","install","brew","node","Media","search","npm","status","auth",{"skillNo":91,"name":92,"nameZh":6,"description":93,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":94,"categories":95,"keywords":96,"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",[],[92,97,98,82,99,83,100,101,102,103,104,105,30,106,107],"travel planning","travel","fetch","curl","https","help","planning","web","back","temperature","with",{"skillNo":109,"name":110,"nameZh":6,"description":111,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":112,"categories":113,"keywords":119,"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",[114],{"categoryNo":115,"categoryName":116,"taxonomyType":117,"taxonomyTypeDesc":118},"01JBSEEDCAT000000000000033","数据分析师","PROFESSION","适用职业",[110,120,121,122,123,30,107,124,125,126,127,128,9,129],"widgets","openclaw dashboard","author","inline","show","code","create","visuals","dashboard","widget",{"skillNo":131,"name":132,"nameZh":6,"description":133,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":134,"categories":135,"keywords":144,"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",[136,141],{"categoryNo":137,"categoryName":138,"taxonomyType":139,"taxonomyTypeDesc":140},"01JBSEEDCAT000000000000010","后端与接口","SCENARIO","使用场景",{"categoryNo":142,"categoryName":143,"taxonomyType":117,"taxonomyTypeDesc":118},"01JBSEEDCAT000000000000030","开发工程师",[132,101,145,146,147,148,149,150,82,83,151,100,76,152,153],"cloud","manage","via","rest api","token","atlassian","jq","REST","developer",{"skillNo":155,"name":156,"nameZh":6,"description":157,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":158,"categories":159,"keywords":160,"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",[],[156,82,161,162,30,163,164,165,166,167,168,169,83,170,171,172,173,174,175],"send","darwin","keys","paste","output","control","prompts","interactive","list","capture","panes","text","monitor","sessions","linux"]