[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M698S3GMRPTZT6HVYH46ABCP":3,"skill-same:01M698S3GMRPTZT6HVYH46ABCP":54},{"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":26,"linkOnly":27,"markdownContent":28,"markdownBody":29,"frontMatter":30,"refName":31,"commitSha":32,"skillDirectory":33,"forksCount":34,"repositoryHtmlUrl":35,"repositoryHomepageUrl":36,"ownerHtmlUrl":37,"ownerBlogUrl":36,"ownerDescription":38,"updatedAt":39,"install":40,"resources":53},"01M698S3GMRPTZT6HVYH46ABCP","release-openclaw-mac",null,"Run or recover OpenClaw macOS release signing, notarization, appcast, and asset promotion.","openclaw\u002Fopenclaw","openclaw","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F252820863?v=4","01M698P3FSAZ6B4R928ZF19KPT","01M698PDMDRVH56MV30D253NFP",394352,"MIT","https:\u002F\u002Fgithub.com\u002Fopenclaw\u002Fopenclaw\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Frelease-openclaw-mac\u002FSKILL.md",[],[9,18,19,20,21,22,23,24,25],"release openclaw mac","release","mac","macos","run","asset","promotion","signing","2026-11-10 10:12:30",false,"---\nname: release-openclaw-mac\ndescription: \"Run or recover OpenClaw macOS release signing, notarization, appcast, and asset promotion.\"\n---\n\n# OpenClaw Mac Release\n\nUse with `$release-openclaw-maintainer`, `$release-openclaw-ci`, `$one-password`, and `$release-private` if it exists when stable macOS assets, release-ops mac preflight, notarization, appcast promotion, or mac release recovery is involved.\n\nThis is a regular stable-release skill. Do not invoke it for extended-stable;\nthat track's GitHub Release carries shared validation evidence but does not\ninherit macOS assets or appcast promotion.\n\n## Release authorization\n\nAn explicit stable or full release request includes macOS publication unless\nthe operator limits its scope. Continue through validation, signing,\nnotarization, promotion, and verification without asking for separate macOS\nconsent. Keep the exact release identity and all artifact checks. macOS\npublication runs in parallel with npm and never blocks it; a mac failure does\nnot hold the npm\u002FClawHub release, GitHub release finalization, or main closeout.\nFix it in parallel.\n\nFollow the current owner-configured environment policy. Do not invent an extra\nreviewer requirement or recreate an obsolete one. If GitHub still enforces an\napproval, report the actual rule and resolve it through its owner; policy changes\nrequire explicit organization-owner direction and verified active admin\nmembership. Never impersonate a reviewer, fabricate approval, or use another\nsigning path to bypass an enforced rule.\n\n## Credentials\n\n- Resolve Peter-owned ASC item refs, key ids, issuer ids, and service-token provenance from `$release-private`.\n- Fields: `private_key_p8`, `key_id`, `issuer_id`.\n- Stale\u002Frevoked key symptom: `xcrun notarytool submit` fails with `HTTP status code: 401. Unauthenticated`.\n- Validate candidate ASC credentials with `xcrun notarytool history` before setting GitHub secrets.\n\n## 1Password\n\n- Use `$one-password`: all `op` work inside one persistent tmux session, no secret output.\n- Use the service-token guidance from `$release-private` when available.\n- If a service token fails, run status-only checks: token present\u002Flength and `op whoami`; never print token values.\n- If desktop app auth is needed but Touch ID is unavailable, set `OP_BIOMETRIC_UNLOCK_ENABLED=false` for the manual `op account add --signin` path.\n\n## GitHub Secrets\n\nTarget release-ops repo environment: `openclaw\u002Freleases`, env `mac-release`.\n\nSet only after local notary auth validation:\n\n- `APP_STORE_CONNECT_API_KEY_P8`\n- `APP_STORE_CONNECT_KEY_ID`\n- `APP_STORE_CONNECT_ISSUER_ID`\n\nDo not update these from mixed sources. All three ASC fields must come from the same 1Password item.\n\n## Workflow Shape\n\n- `openclaw\u002Fopenclaw` is the public product repo. Its GitHub Releases page is\n  where macOS assets are ultimately attached.\n- `openclaw\u002Fopenclaw` `macos-release.yml` is public handoff validation only.\n  It never signs, notarizes, or uploads macOS assets, regardless of\n  `preflight_only`.\n- `openclaw\u002Freleases` is the restricted release-ops repo. Its macOS workflows\n  sign, notarize, validate, and promote assets onto the\n  `openclaw\u002Fopenclaw` GitHub release.\n- Public release branch may carry mac-only packaging fixes after the stable tag\u002Fnpm are already live.\n- Use `source_ref=release\u002FYYYY.M.PATCH` for release-ops mac preflight\u002Fvalidation when building that branch variation.\n- Keep `tag=vYYYY.M.PATCH` pointing at the original stable release commit.\n- Real mac publish must reuse:\n  - a successful release-ops mac preflight run for the same tag\u002Fsource SHA\n  - a successful release-ops mac validation run for the same tag\u002Fsource SHA\n- Release-ops preflight and real publish use the `mac-release` environment for\n  signing and promotion secrets and its main-only deployment policy. The\n  authorized release operator continues under that environment's current rules.\n- If preflight source SHA differs from tag SHA, validation must also use the same `source_ref`; promotion rejects mismatched proof.\n\n## Notarization\n\n- OpenClaw uses `scripts\u002Fnotarize-mac-artifact.sh`.\n- `xcrun notarytool submit` should use `--no-s3-acceleration`; accelerated upload can surface misleading 401s even when `notarytool history` succeeds.\n- If signing succeeds but notarization fails immediately with 401, check ASC key freshness first.\n- If notarization stays in progress for several minutes after key-file write, that is normal Apple wait time; do not edit blindly.\n\n## Dispatch\n\nThe public handoff workflow validates the tag, source, build, and package\nmetadata before publication. It does not require a GitHub release page because\nit does not upload assets. Keep this validation before the real publish\nworkflow. The core publisher owns GitHub release finalization; macOS promotion\nattaches its verified assets to that release whether it is still a draft or\nalready public, so it never waits for the npm flip.\n\nPublic handoff validation:\n\n```bash\ngh workflow run macos-release.yml --repo openclaw\u002Fopenclaw \\\n  --ref release\u002FYYYY.M.PATCH \\\n  -f tag=vYYYY.M.PATCH \\\n  -f preflight_only=true \\\n  -f public_release_branch=release\u002FYYYY.M.PATCH\n```\n\n- Use the public release branch as the workflow ref so the Actions list displays\n  `release\u002FYYYY.M.PATCH`, matching prior stable macOS handoff runs.\n- Do not use `--ref main` or `--ref vYYYY.M.PATCH` for this public handoff\n  validation. The workflow checks out the tag from the `tag` input internally.\n\nRelease-ops preflight:\n\n```bash\ngh workflow run openclaw-macos-publish.yml --repo openclaw\u002Freleases --ref main \\\n  -f tag=vYYYY.M.PATCH \\\n  -f source_ref=release\u002FYYYY.M.PATCH \\\n  -f preflight_only=true \\\n  -f smoke_test_only=false \\\n  -f allow_late_calver_recovery=false \\\n  -f public_release_branch=release\u002FYYYY.M.PATCH\n```\n\nFollow the run through signing and notarization under the configured environment\npolicy. Record the successful preflight run id; an approval pause is not a\nsuccessful preflight.\n\nResume is the default. Re-dispatching the same preflight command after a\nfailure (notary outage, DMG packaging, collector) resumes every variant from\nthe newest checkpoint left by a failed or cancelled `main` dispatch for the same\ntag and source SHA; only variants without a checkpoint rebuild. The run log\nprints `Resuming \u003Cvariant> from run \u003Cid> attempt \u003Cn>` or `Building \u003Cvariant>`.\n`ignore_checkpoints=true` forces fresh builds. Pass `resume_notarization_run_id`,\n`resume_notarization_run_attempt`, and `resume_notarization_variant` only to pin\none specific run, or for checkpoints made before the resume index existed\n(`macos-resume-\u003Ctag>-\u003Cvariant>-\u003Csha>` artifacts). Prefer\n`gh run rerun \u003Crun-id> --failed --repo openclaw\u002Freleases` when the failed job is\nstill in the current run.\n\nRelease-ops validation for a branch-variation preflight:\n\n```bash\ngh workflow run openclaw-macos-validate.yml --repo openclaw\u002Freleases --ref main \\\n  -f tag=vYYYY.M.PATCH \\\n  -f source_ref=release\u002FYYYY.M.PATCH\n```\n\nRecord the successful validation run id.\n\nReal publish:\n\n```bash\ngh workflow run openclaw-macos-publish.yml --repo openclaw\u002Freleases --ref main \\\n  -f tag=vYYYY.M.PATCH \\\n  -f preflight_only=false \\\n  -f smoke_test_only=false \\\n  -f preflight_run_id=\u003Csuccessful-preflight-run> \\\n  -f validate_run_id=\u003Csuccessful-validation-run> \\\n  -f allow_late_calver_recovery=false \\\n  -f public_release_branch=release\u002FYYYY.M.PATCH\n```\n\nFollow promotion through asset upload and appcast publication under the same\nrelease authorization and current environment policy.\n\n- Release-ops `openclaw\u002Freleases` publish\u002Fvalidate workflows run from their own\n  trusted `main` workflow ref. Real publish has a guard that rejects any other\n  workflow ref. That displayed `main` ref is expected; the public OpenClaw\n  source is selected by `tag` and optional `source_ref`.\n\n## Verify\n\n- `gh release view vYYYY.M.PATCH --repo openclaw\u002Fopenclaw` shows zip, dmg, dSYM zip; once the npm publisher has flipped it: not draft, not prerelease.\n- Public `main` `appcast.xml` points at `OpenClaw-YYYY.M.PATCH.zip`.\n- Appcast entry has `sparkle:version`, `sparkle:shortVersionString`, length, and `sparkle:edSignature`.\n","# OpenClaw Mac Release\n\nUse with `$release-openclaw-maintainer`, `$release-openclaw-ci`, `$one-password`, and `$release-private` if it exists when stable macOS assets, release-ops mac preflight, notarization, appcast promotion, or mac release recovery is involved.\n\nThis is a regular stable-release skill. Do not invoke it for extended-stable;\nthat track's GitHub Release carries shared validation evidence but does not\ninherit macOS assets or appcast promotion.\n\n## Release authorization\n\nAn explicit stable or full release request includes macOS publication unless\nthe operator limits its scope. Continue through validation, signing,\nnotarization, promotion, and verification without asking for separate macOS\nconsent. Keep the exact release identity and all artifact checks. macOS\npublication runs in parallel with npm and never blocks it; a mac failure does\nnot hold the npm\u002FClawHub release, GitHub release finalization, or main closeout.\nFix it in parallel.\n\nFollow the current owner-configured environment policy. Do not invent an extra\nreviewer requirement or recreate an obsolete one. If GitHub still enforces an\napproval, report the actual rule and resolve it through its owner; policy changes\nrequire explicit organization-owner direction and verified active admin\nmembership. Never impersonate a reviewer, fabricate approval, or use another\nsigning path to bypass an enforced rule.\n\n## Credentials\n\n- Resolve Peter-owned ASC item refs, key ids, issuer ids, and service-token provenance from `$release-private`.\n- Fields: `private_key_p8`, `key_id`, `issuer_id`.\n- Stale\u002Frevoked key symptom: `xcrun notarytool submit` fails with `HTTP status code: 401. Unauthenticated`.\n- Validate candidate ASC credentials with `xcrun notarytool history` before setting GitHub secrets.\n\n## 1Password\n\n- Use `$one-password`: all `op` work inside one persistent tmux session, no secret output.\n- Use the service-token guidance from `$release-private` when available.\n- If a service token fails, run status-only checks: token present\u002Flength and `op whoami`; never print token values.\n- If desktop app auth is needed but Touch ID is unavailable, set `OP_BIOMETRIC_UNLOCK_ENABLED=false` for the manual `op account add --signin` path.\n\n## GitHub Secrets\n\nTarget release-ops repo environment: `openclaw\u002Freleases`, env `mac-release`.\n\nSet only after local notary auth validation:\n\n- `APP_STORE_CONNECT_API_KEY_P8`\n- `APP_STORE_CONNECT_KEY_ID`\n- `APP_STORE_CONNECT_ISSUER_ID`\n\nDo not update these from mixed sources. All three ASC fields must come from the same 1Password item.\n\n## Workflow Shape\n\n- `openclaw\u002Fopenclaw` is the public product repo. Its GitHub Releases page is\n  where macOS assets are ultimately attached.\n- `openclaw\u002Fopenclaw` `macos-release.yml` is public handoff validation only.\n  It never signs, notarizes, or uploads macOS assets, regardless of\n  `preflight_only`.\n- `openclaw\u002Freleases` is the restricted release-ops repo. Its macOS workflows\n  sign, notarize, validate, and promote assets onto the\n  `openclaw\u002Fopenclaw` GitHub release.\n- Public release branch may carry mac-only packaging fixes after the stable tag\u002Fnpm are already live.\n- Use `source_ref=release\u002FYYYY.M.PATCH` for release-ops mac preflight\u002Fvalidation when building that branch variation.\n- Keep `tag=vYYYY.M.PATCH` pointing at the original stable release commit.\n- Real mac publish must reuse:\n  - a successful release-ops mac preflight run for the same tag\u002Fsource SHA\n  - a successful release-ops mac validation run for the same tag\u002Fsource SHA\n- Release-ops preflight and real publish use the `mac-release` environment for\n  signing and promotion secrets and its main-only deployment policy. The\n  authorized release operator continues under that environment's current rules.\n- If preflight source SHA differs from tag SHA, validation must also use the same `source_ref`; promotion rejects mismatched proof.\n\n## Notarization\n\n- OpenClaw uses `scripts\u002Fnotarize-mac-artifact.sh`.\n- `xcrun notarytool submit` should use `--no-s3-acceleration`; accelerated upload can surface misleading 401s even when `notarytool history` succeeds.\n- If signing succeeds but notarization fails immediately with 401, check ASC key freshness first.\n- If notarization stays in progress for several minutes after key-file write, that is normal Apple wait time; do not edit blindly.\n\n## Dispatch\n\nThe public handoff workflow validates the tag, source, build, and package\nmetadata before publication. It does not require a GitHub release page because\nit does not upload assets. Keep this validation before the real publish\nworkflow. The core publisher owns GitHub release finalization; macOS promotion\nattaches its verified assets to that release whether it is still a draft or\nalready public, so it never waits for the npm flip.\n\nPublic handoff validation:\n\n```bash\ngh workflow run macos-release.yml --repo openclaw\u002Fopenclaw \\\n  --ref release\u002FYYYY.M.PATCH \\\n  -f tag=vYYYY.M.PATCH \\\n  -f preflight_only=true \\\n  -f public_release_branch=release\u002FYYYY.M.PATCH\n```\n\n- Use the public release branch as the workflow ref so the Actions list displays\n  `release\u002FYYYY.M.PATCH`, matching prior stable macOS handoff runs.\n- Do not use `--ref main` or `--ref vYYYY.M.PATCH` for this public handoff\n  validation. The workflow checks out the tag from the `tag` input internally.\n\nRelease-ops preflight:\n\n```bash\ngh workflow run openclaw-macos-publish.yml --repo openclaw\u002Freleases --ref main \\\n  -f tag=vYYYY.M.PATCH \\\n  -f source_ref=release\u002FYYYY.M.PATCH \\\n  -f preflight_only=true \\\n  -f smoke_test_only=false \\\n  -f allow_late_calver_recovery=false \\\n  -f public_release_branch=release\u002FYYYY.M.PATCH\n```\n\nFollow the run through signing and notarization under the configured environment\npolicy. Record the successful preflight run id; an approval pause is not a\nsuccessful preflight.\n\nResume is the default. Re-dispatching the same preflight command after a\nfailure (notary outage, DMG packaging, collector) resumes every variant from\nthe newest checkpoint left by a failed or cancelled `main` dispatch for the same\ntag and source SHA; only variants without a checkpoint rebuild. The run log\nprints `Resuming \u003Cvariant> from run \u003Cid> attempt \u003Cn>` or `Building \u003Cvariant>`.\n`ignore_checkpoints=true` forces fresh builds. Pass `resume_notarization_run_id`,\n`resume_notarization_run_attempt`, and `resume_notarization_variant` only to pin\none specific run, or for checkpoints made before the resume index existed\n(`macos-resume-\u003Ctag>-\u003Cvariant>-\u003Csha>` artifacts). Prefer\n`gh run rerun \u003Crun-id> --failed --repo openclaw\u002Freleases` when the failed job is\nstill in the current run.\n\nRelease-ops validation for a branch-variation preflight:\n\n```bash\ngh workflow run openclaw-macos-validate.yml --repo openclaw\u002Freleases --ref main \\\n  -f tag=vYYYY.M.PATCH \\\n  -f source_ref=release\u002FYYYY.M.PATCH\n```\n\nRecord the successful validation run id.\n\nReal publish:\n\n```bash\ngh workflow run openclaw-macos-publish.yml --repo openclaw\u002Freleases --ref main \\\n  -f tag=vYYYY.M.PATCH \\\n  -f preflight_only=false \\\n  -f smoke_test_only=false \\\n  -f preflight_run_id=\u003Csuccessful-preflight-run> \\\n  -f validate_run_id=\u003Csuccessful-validation-run> \\\n  -f allow_late_calver_recovery=false \\\n  -f public_release_branch=release\u002FYYYY.M.PATCH\n```\n\nFollow promotion through asset upload and appcast publication under the same\nrelease authorization and current environment policy.\n\n- Release-ops `openclaw\u002Freleases` publish\u002Fvalidate workflows run from their own\n  trusted `main` workflow ref. Real publish has a guard that rejects any other\n  workflow ref. That displayed `main` ref is expected; the public OpenClaw\n  source is selected by `tag` and optional `source_ref`.\n\n## Verify\n\n- `gh release view vYYYY.M.PATCH --repo openclaw\u002Fopenclaw` shows zip, dmg, dSYM zip; once the npm publisher has flipped it: not draft, not prerelease.\n- Public `main` `appcast.xml` points at `OpenClaw-YYYY.M.PATCH.zip`.\n- Appcast entry has `sparkle:version`, `sparkle:shortVersionString`, length, and `sparkle:edSignature`.\n",{"name":5,"description":7},"main","f1c93577085244aa96aa87b53a2df9b59d293bd7",".agents\u002Fskills\u002Frelease-openclaw-mac",82861,"https:\u002F\u002Fgithub.com\u002Fopenclaw\u002Fopenclaw","https:\u002F\u002Fopenclaw.ai","https:\u002F\u002Fgithub.com\u002Fopenclaw","Your personal, open source AI assistant.","2026-11-12 03:01:25",{"source":8,"skillName":5,"commands":41,"prompt":51,"zipAvailable":52},[42,45,48],{"tool":43,"command":44},"npx","npx skills add openclaw\u002Fopenclaw --skill release-openclaw-mac",{"tool":46,"command":47},"bunx","bunx skills add openclaw\u002Fopenclaw --skill release-openclaw-mac",{"tool":49,"command":50},"pnpm","pnpm dlx skills add openclaw\u002Fopenclaw --skill release-openclaw-mac","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fopenclaw\u002Fopenclaw\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Frelease-openclaw-mac\u002FSKILL.md",true,[],[55,61,84,102,124,148],{"skillNo":56,"name":57,"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":58,"categories":59,"keywords":60,"publishedAt":26},"01M698VP84FNM6G9MR1HPX7MF7","lobster","https:\u002F\u002Fgithub.com\u002Fopenclaw\u002Fopenclaw\u002Fblob\u002Fmain\u002Fextensions\u002Flobster\u002FSKILL.md",[],[57],{"skillNo":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":65,"categories":66,"keywords":67,"publishedAt":26},"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",[],[63,68,69,70,71,72,73,74,75,76,77,78,79,80,81,82,83],"for","api","calls","replies","posts","upload","tap","install","brew","node","Media","search","npm","status","auth","cli",{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":26},"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",[],[86,91,92,75,93,76,94,95,96,97,98,99,68,100,101],"travel planning","travel","fetch","curl","https","help","planning","web","back","temperature","with",{"skillNo":103,"name":104,"nameZh":6,"description":105,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":106,"categories":107,"keywords":113,"publishedAt":26},"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",[108],{"categoryNo":109,"categoryName":110,"taxonomyType":111,"taxonomyTypeDesc":112},"01JBSEEDCAT000000000000033","数据分析师","PROFESSION","适用职业",[104,114,115,116,117,68,101,118,119,120,121,122,9,123],"widgets","openclaw dashboard","author","inline","show","code","create","visuals","dashboard","widget",{"skillNo":125,"name":126,"nameZh":6,"description":127,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":128,"categories":129,"keywords":138,"publishedAt":26},"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",[130,135],{"categoryNo":131,"categoryName":132,"taxonomyType":133,"taxonomyTypeDesc":134},"01JBSEEDCAT000000000000010","后端与接口","SCENARIO","使用场景",{"categoryNo":136,"categoryName":137,"taxonomyType":111,"taxonomyTypeDesc":112},"01JBSEEDCAT000000000000030","开发工程师",[126,95,139,140,141,142,143,144,75,76,145,94,69,146,147],"cloud","manage","via","rest api","token","atlassian","jq","REST","developer",{"skillNo":149,"name":150,"nameZh":6,"description":151,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":152,"categories":153,"keywords":154,"publishedAt":26},"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",[],[150,75,155,156,68,157,158,159,160,161,162,163,76,164,165,166,167,168,169],"send","darwin","keys","paste","output","control","prompts","interactive","list","capture","panes","text","monitor","sessions","linux"]