[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7A5QPS1HHTBFQRB5Y5CD7N2":3,"skill-same:01M7A5QPS1HHTBFQRB5Y5CD7N2":51},{"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":14,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":29,"ownerDescription":6,"updatedAt":30,"install":31,"resources":44},"01M7A5QPS1HHTBFQRB5Y5CD7N2","sdk-release",null,"This skill should be used when the user asks to \"release the SDK\", \"prepare a release\", \"publish a new version\", \"cut a release\", \"do a release\", or mentions the SDK release checklist or release process. Guides through the full software-agent-sdk release workflow from version bump to PyPI publication, emphasizing human checkpoints.","shivajid\u002Fgke-vibebench","shivajid","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F7957968?v=4","01M7A5PFAQSD8DZ60CT676GSSC","Shivaji Dutta","01M7A5PFBSBPTPT0ZJGZEWYEG7",0,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fshivajid\u002Fgke-vibebench\u002Fblob\u002Fmain\u002F_harness\u002Fopenhands-sdk\u002F.agents\u002Fskills\u002Fsdk-release\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: sdk-release\ndescription: >-\n  This skill should be used when the user asks to \"release the SDK\",\n  \"prepare a release\", \"publish a new version\", \"cut a release\",\n  \"do a release\", or mentions the SDK release checklist or release process.\n  Guides through the full software-agent-sdk release workflow\n  from version bump to PyPI publication, emphasizing human checkpoints.\n---\n\n# SDK Release Guide\n\nThis skill walks through the software-agent-sdk release process step by step.\n\n> **🚨 CRITICAL**: NEVER merge the release PR or create\u002Fpublish a GitHub\n> release without the human's explicit approval. Release is the last line\n> of human defense. Always present the current status and ask for\n> confirmation before performing any irreversible action.\n\n## Phase 1: Trigger the Prepare-Release Workflow\n\nDetermine the target version (SemVer `X.Y.Z`). Then trigger the\n`prepare-release.yml` workflow, which creates a release branch and PR\nautomatically.\n\n### Via GitHub UI\n\nNavigate to\n\u003Chttps:\u002F\u002Fgithub.com\u002FOpenHands\u002Fsoftware-agent-sdk\u002Factions\u002Fworkflows\u002Fprepare-release.yml>,\nclick **Run workflow**, enter the version (e.g. `1.16.0`), and run it.\n\n### Via GitHub API\n\n```bash\ncurl -X POST \\\n  -H \"Authorization: token $GITHUB_TOKEN\" \\\n  -H \"Accept: application\u002Fvnd.github+json\" \\\n  \"https:\u002F\u002Fapi.github.com\u002Frepos\u002FOpenHands\u002Fsoftware-agent-sdk\u002Factions\u002Fworkflows\u002Fprepare-release.yml\u002Fdispatches\" \\\n  -d '{\n    \"ref\": \"main\",\n    \"inputs\": {\n      \"version\": \"1.16.0\"\n    }\n  }'\n```\n\nThe workflow will:\n1. Validate version format\n2. Create branch `rel-\u003Cversion>`\n3. Run `make set-package-version version=\u003Cversion>` across all packages\n4. Update the `sdk_ref` default in the eval workflow\n5. Open a PR titled **\"Release v\\\u003Cversion\\>\"** with labels\n   `integration-test`, `behavior-test`, and `test-examples`\n\n### ⏸ Checkpoint — Confirm PR Created\n\nVerify the PR exists and the version changes look correct before continuing.\n\n```bash\ngh pr list --repo OpenHands\u002Fsoftware-agent-sdk \\\n  --head \"rel-\u003Cversion>\" --json number,title,url\n```\n\n## Phase 2: Address Deprecation Deadlines\n\nThe `deprecation-check` CI job runs on every PR. If the release version\ncrosses any deprecation deadline declared in the codebase, the check will\nfail.\n\nReview the failing check output and either:\n- Remove the deprecated code if the deadline has passed, **or**\n- Extend the deadline with justification.\n\nPush fixes to the release branch. The check must pass before merging.\n\n## Phase 3: Wait for CI — Tests Must Pass\n\nThe release PR triggers three labeled test suites. **All three must pass.**\n\n| Label | Suite | What it covers |\n|-------|-------|----------------|\n| `integration-test` | Integration tests | End-to-end agent scenarios |\n| `behavior-test` | Behavior tests | Agent behavioral guardrails |\n| `test-examples` | Example tests | All runnable examples in `examples\u002F` |\n\nMonitor status:\n\n```bash\ngh pr checks \u003CPR_NUMBER> --repo OpenHands\u002Fsoftware-agent-sdk\n```\n\n### ⏸ Checkpoint — Human Judgment on Failures\n\nSome test failures may be pre-existing or flaky. Decide with the team\nwhether each failure is:\n- **Blocking** — must fix before release\n- **Known \u002F pre-existing** — acceptable to release with a follow-up issue\n- **Flaky** — re-run the workflow\n\nRe-run failed jobs:\n\n```bash\n# Find the run ID\ngh run list --repo OpenHands\u002Fsoftware-agent-sdk \\\n  --branch \"rel-\u003Cversion>\" --limit 5\n\n# Re-run failed jobs\ngh run rerun \u003CRUN_ID> --repo OpenHands\u002Fsoftware-agent-sdk --failed\n```\n\n## Phase 4: Run Evaluation (Optional but Recommended)\n\nTrigger an evaluation run on SWE-bench (or another benchmark) against the\nrelease branch to catch regressions. See the `run-eval` skill for full\ndetails.\n\n```bash\ncurl -X POST \\\n  -H \"Authorization: token $GITHUB_TOKEN\" \\\n  -H \"Accept: application\u002Fvnd.github+json\" \\\n  \"https:\u002F\u002Fapi.github.com\u002Frepos\u002FOpenHands\u002Fsoftware-agent-sdk\u002Factions\u002Fworkflows\u002Frun-eval.yml\u002Fdispatches\" \\\n  -d '{\n    \"ref\": \"main\",\n    \"inputs\": {\n      \"benchmark\": \"swebench\",\n      \"sdk_ref\": \"v\u003Cversion>\",\n      \"eval_limit\": \"50\",\n      \"reason\": \"Pre-release eval for v\u003Cversion>\",\n      \"allow_unreleased_branches\": \"true\"\n    }\n  }'\n```\n\n### ⏸ Checkpoint — Evaluate Results\n\nCompare the eval results against the previous release. Significant score\ndrops should block the release.\n\n## Phase 5: Merge the Release PR\n\n> **🚨 STOP — Do NOT merge without explicit human approval.**\n> Present the CI status summary and ask the human to confirm before merging.\n\nOnce the human approves:\n\n```bash\ngh pr merge \u003CPR_NUMBER> --repo OpenHands\u002Fsoftware-agent-sdk --merge\n```\n\n## Phase 6: Create and Publish the GitHub Release\n\n> **🚨 STOP — Do NOT create or publish a release without explicit human\n> approval.** Publishing is irreversible — it triggers PyPI publication.\n> Present the release details and ask the human to confirm.\n\nNavigate to \u003Chttps:\u002F\u002Fgithub.com\u002FOpenHands\u002Fsoftware-agent-sdk\u002Freleases\u002Fnew>\nand:\n\n1. **Tag**: `v\u003Cversion>` (create new tag)\n2. **Target branch**: `rel-\u003Cversion>` (or `main` after merge)\n3. Click **Auto-generate release notes**\n4. Review the notes, then click **Publish release**\n\nPublishing the release automatically triggers the `pypi-release.yml`\nworkflow, which builds and publishes all four packages to PyPI:\n- `openhands-sdk`\n- `openhands-tools`\n- `openhands-workspace`\n- `openhands-agent-server`\n\n### ⏸ Checkpoint — Verify PyPI Publication\n\n```bash\n# Check each package is available\nfor pkg in openhands-sdk openhands-tools openhands-workspace openhands-agent-server; do\n  curl -s -o \u002Fdev\u002Fnull -w \"$pkg: %{http_code}\\n\" \\\n    \"https:\u002F\u002Fpypi.org\u002Fpypi\u002F$pkg\u002F\u003Cversion>\u002Fjson\"\ndone\n```\n\nAll should return `200`. Allow a few minutes for PyPI indexing.\n\n## Phase 7: Post-Release — Notify the Team\n\nAfter PyPI publication, the `version-bump-prs.yml` workflow automatically\ncreates downstream version bump PRs. Compose a Slack message for the human\nto post, including links to those PRs:\n\n```\n🚀 *SDK v\u003Cversion> published to PyPI!*\n\nVersion bump PRs:\n• \u003Chttps:\u002F\u002Fgithub.com\u002FAll-Hands-AI\u002FOpenHands\u002Fpulls?q=is%3Apr+bump-sdk-\u003Cversion>|OpenHands>\n• \u003Chttps:\u002F\u002Fgithub.com\u002FOpenHands\u002Fopenhands-cli\u002Fpulls?q=is%3Apr+bump-sdk-\u003Cversion>|OpenHands-CLI>\n\nRelease: \u003Chttps:\u002F\u002Fgithub.com\u002FOpenHands\u002Fsoftware-agent-sdk\u002Freleases\u002Ftag\u002Fv\u003Cversion>|v\u003Cversion>>\n```\n\nSee `references\u002Fpost-release-checklist.md` for details on reviewing\ndownstream PRs and handling any issues.\n\n## Quick Reference — Full Checklist\n\n- [ ] Trigger `prepare-release.yml` with target version\n- [ ] Verify release PR is created\n- [ ] Fix deprecation deadline failures (if any)\n- [ ] Integration tests pass\n- [ ] Behavior tests pass\n- [ ] Example tests pass\n- [ ] (Optional) Evaluation run shows no regressions\n- [ ] **🚨 Get human approval**, then merge the release PR\n- [ ] **🚨 Get human approval**, then create GitHub release with tag `v\u003Cversion>`\n- [ ] Auto-generate release notes and publish\n- [ ] Verify packages appear on PyPI\n- [ ] Send Slack message with downstream version bump PR links\n","# SDK Release Guide\n\nThis skill walks through the software-agent-sdk release process step by step.\n\n> **🚨 CRITICAL**: NEVER merge the release PR or create\u002Fpublish a GitHub\n> release without the human's explicit approval. Release is the last line\n> of human defense. Always present the current status and ask for\n> confirmation before performing any irreversible action.\n\n## Phase 1: Trigger the Prepare-Release Workflow\n\nDetermine the target version (SemVer `X.Y.Z`). Then trigger the\n`prepare-release.yml` workflow, which creates a release branch and PR\nautomatically.\n\n### Via GitHub UI\n\nNavigate to\n\u003Chttps:\u002F\u002Fgithub.com\u002FOpenHands\u002Fsoftware-agent-sdk\u002Factions\u002Fworkflows\u002Fprepare-release.yml>,\nclick **Run workflow**, enter the version (e.g. `1.16.0`), and run it.\n\n### Via GitHub API\n\n```bash\ncurl -X POST \\\n  -H \"Authorization: token $GITHUB_TOKEN\" \\\n  -H \"Accept: application\u002Fvnd.github+json\" \\\n  \"https:\u002F\u002Fapi.github.com\u002Frepos\u002FOpenHands\u002Fsoftware-agent-sdk\u002Factions\u002Fworkflows\u002Fprepare-release.yml\u002Fdispatches\" \\\n  -d '{\n    \"ref\": \"main\",\n    \"inputs\": {\n      \"version\": \"1.16.0\"\n    }\n  }'\n```\n\nThe workflow will:\n1. Validate version format\n2. Create branch `rel-\u003Cversion>`\n3. Run `make set-package-version version=\u003Cversion>` across all packages\n4. Update the `sdk_ref` default in the eval workflow\n5. Open a PR titled **\"Release v\\\u003Cversion\\>\"** with labels\n   `integration-test`, `behavior-test`, and `test-examples`\n\n### ⏸ Checkpoint — Confirm PR Created\n\nVerify the PR exists and the version changes look correct before continuing.\n\n```bash\ngh pr list --repo OpenHands\u002Fsoftware-agent-sdk \\\n  --head \"rel-\u003Cversion>\" --json number,title,url\n```\n\n## Phase 2: Address Deprecation Deadlines\n\nThe `deprecation-check` CI job runs on every PR. If the release version\ncrosses any deprecation deadline declared in the codebase, the check will\nfail.\n\nReview the failing check output and either:\n- Remove the deprecated code if the deadline has passed, **or**\n- Extend the deadline with justification.\n\nPush fixes to the release branch. The check must pass before merging.\n\n## Phase 3: Wait for CI — Tests Must Pass\n\nThe release PR triggers three labeled test suites. **All three must pass.**\n\n| Label | Suite | What it covers |\n|-------|-------|----------------|\n| `integration-test` | Integration tests | End-to-end agent scenarios |\n| `behavior-test` | Behavior tests | Agent behavioral guardrails |\n| `test-examples` | Example tests | All runnable examples in `examples\u002F` |\n\nMonitor status:\n\n```bash\ngh pr checks \u003CPR_NUMBER> --repo OpenHands\u002Fsoftware-agent-sdk\n```\n\n### ⏸ Checkpoint — Human Judgment on Failures\n\nSome test failures may be pre-existing or flaky. Decide with the team\nwhether each failure is:\n- **Blocking** — must fix before release\n- **Known \u002F pre-existing** — acceptable to release with a follow-up issue\n- **Flaky** — re-run the workflow\n\nRe-run failed jobs:\n\n```bash\n# Find the run ID\ngh run list --repo OpenHands\u002Fsoftware-agent-sdk \\\n  --branch \"rel-\u003Cversion>\" --limit 5\n\n# Re-run failed jobs\ngh run rerun \u003CRUN_ID> --repo OpenHands\u002Fsoftware-agent-sdk --failed\n```\n\n## Phase 4: Run Evaluation (Optional but Recommended)\n\nTrigger an evaluation run on SWE-bench (or another benchmark) against the\nrelease branch to catch regressions. See the `run-eval` skill for full\ndetails.\n\n```bash\ncurl -X POST \\\n  -H \"Authorization: token $GITHUB_TOKEN\" \\\n  -H \"Accept: application\u002Fvnd.github+json\" \\\n  \"https:\u002F\u002Fapi.github.com\u002Frepos\u002FOpenHands\u002Fsoftware-agent-sdk\u002Factions\u002Fworkflows\u002Frun-eval.yml\u002Fdispatches\" \\\n  -d '{\n    \"ref\": \"main\",\n    \"inputs\": {\n      \"benchmark\": \"swebench\",\n      \"sdk_ref\": \"v\u003Cversion>\",\n      \"eval_limit\": \"50\",\n      \"reason\": \"Pre-release eval for v\u003Cversion>\",\n      \"allow_unreleased_branches\": \"true\"\n    }\n  }'\n```\n\n### ⏸ Checkpoint — Evaluate Results\n\nCompare the eval results against the previous release. Significant score\ndrops should block the release.\n\n## Phase 5: Merge the Release PR\n\n> **🚨 STOP — Do NOT merge without explicit human approval.**\n> Present the CI status summary and ask the human to confirm before merging.\n\nOnce the human approves:\n\n```bash\ngh pr merge \u003CPR_NUMBER> --repo OpenHands\u002Fsoftware-agent-sdk --merge\n```\n\n## Phase 6: Create and Publish the GitHub Release\n\n> **🚨 STOP — Do NOT create or publish a release without explicit human\n> approval.** Publishing is irreversible — it triggers PyPI publication.\n> Present the release details and ask the human to confirm.\n\nNavigate to \u003Chttps:\u002F\u002Fgithub.com\u002FOpenHands\u002Fsoftware-agent-sdk\u002Freleases\u002Fnew>\nand:\n\n1. **Tag**: `v\u003Cversion>` (create new tag)\n2. **Target branch**: `rel-\u003Cversion>` (or `main` after merge)\n3. Click **Auto-generate release notes**\n4. Review the notes, then click **Publish release**\n\nPublishing the release automatically triggers the `pypi-release.yml`\nworkflow, which builds and publishes all four packages to PyPI:\n- `openhands-sdk`\n- `openhands-tools`\n- `openhands-workspace`\n- `openhands-agent-server`\n\n### ⏸ Checkpoint — Verify PyPI Publication\n\n```bash\n# Check each package is available\nfor pkg in openhands-sdk openhands-tools openhands-workspace openhands-agent-server; do\n  curl -s -o \u002Fdev\u002Fnull -w \"$pkg: %{http_code}\\n\" \\\n    \"https:\u002F\u002Fpypi.org\u002Fpypi\u002F$pkg\u002F\u003Cversion>\u002Fjson\"\ndone\n```\n\nAll should return `200`. Allow a few minutes for PyPI indexing.\n\n## Phase 7: Post-Release — Notify the Team\n\nAfter PyPI publication, the `version-bump-prs.yml` workflow automatically\ncreates downstream version bump PRs. Compose a Slack message for the human\nto post, including links to those PRs:\n\n```\n🚀 *SDK v\u003Cversion> published to PyPI!*\n\nVersion bump PRs:\n• \u003Chttps:\u002F\u002Fgithub.com\u002FAll-Hands-AI\u002FOpenHands\u002Fpulls?q=is%3Apr+bump-sdk-\u003Cversion>|OpenHands>\n• \u003Chttps:\u002F\u002Fgithub.com\u002FOpenHands\u002Fopenhands-cli\u002Fpulls?q=is%3Apr+bump-sdk-\u003Cversion>|OpenHands-CLI>\n\nRelease: \u003Chttps:\u002F\u002Fgithub.com\u002FOpenHands\u002Fsoftware-agent-sdk\u002Freleases\u002Ftag\u002Fv\u003Cversion>|v\u003Cversion>>\n```\n\nSee `references\u002Fpost-release-checklist.md` for details on reviewing\ndownstream PRs and handling any issues.\n\n## Quick Reference — Full Checklist\n\n- [ ] Trigger `prepare-release.yml` with target version\n- [ ] Verify release PR is created\n- [ ] Fix deprecation deadline failures (if any)\n- [ ] Integration tests pass\n- [ ] Behavior tests pass\n- [ ] Example tests pass\n- [ ] (Optional) Evaluation run shows no regressions\n- [ ] **🚨 Get human approval**, then merge the release PR\n- [ ] **🚨 Get human approval**, then create GitHub release with tag `v\u003Cversion>`\n- [ ] Auto-generate release notes and publish\n- [ ] Verify packages appear on PyPI\n- [ ] Send Slack message with downstream version bump PR links\n",{"name":5,"description":7},"main","3fa52d6d1177f038c17dcfa872588821003aeedc","_harness\u002Fopenhands-sdk\u002F.agents\u002Fskills\u002Fsdk-release","https:\u002F\u002Fgithub.com\u002Fshivajid\u002Fgke-vibebench","https:\u002F\u002Fgithub.com\u002Fshivajid","https:\u002F\u002Fwww.linkedin.com\u002Fin\u002Fshivajidutta","2026-08-05 14:15:26",{"source":8,"skillName":5,"commands":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add shivajid\u002Fgke-vibebench --skill sdk-release",{"tool":37,"command":38},"bunx","bunx skills add shivajid\u002Fgke-vibebench --skill sdk-release",{"tool":40,"command":41},"pnpm","pnpm dlx skills add shivajid\u002Fgke-vibebench --skill sdk-release","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fshivajid\u002Fgke-vibebench\u002Fblob\u002Fmain\u002F_harness\u002Fopenhands-sdk\u002F.agents\u002Fskills\u002Fsdk-release\u002FSKILL.md",true,[45],{"path":46,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":49,"sourceHtmlUrl":50},"references\u002Fpost-release-checklist.md","REFERENCE","参考文档",3016,"https:\u002F\u002Fgithub.com\u002Fshivajid\u002Fgke-vibebench\u002Fblob\u002Fmain\u002F_harness\u002Fopenhands-sdk\u002F.agents\u002Fskills\u002Fsdk-release\u002Freferences\u002Fpost-release-checklist.md",[52,60,67,74,80,87],{"skillNo":53,"name":54,"nameZh":6,"description":55,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":56,"licenseFileUrl":6,"sourceHtmlUrl":57,"categories":58,"keywords":59,"publishedAt":19},"01M7A5R3AZ38530PRBYF0RBKDY","python-linting","This skill helps lint Python code using ruff. Use when the user asks to \"lint\", \"check code quality\", or \"fix style issues\".","MIT","https:\u002F\u002Fgithub.com\u002Fshivajid\u002Fgke-vibebench\u002Fblob\u002Fmain\u002F_harness\u002Fopenhands-sdk\u002Fexamples\u002F05_skills_and_plugins\u002F02_loading_plugins\u002Fexample_plugins\u002Fcode-quality\u002Fskills\u002Flinting\u002FSKILL.md",[],[],{"skillNo":61,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":56,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":66,"publishedAt":19},"01M7A5R0QGE6BPPFKV5KGC9PT8","rot13-encryption","This skill helps encrypt and decrypt messages using ROT13 cipher. Use when the user asks to \"encrypt\" or \"decrypt\" a message.","https:\u002F\u002Fgithub.com\u002Fshivajid\u002Fgke-vibebench\u002Fblob\u002Fmain\u002F_harness\u002Fopenhands-sdk\u002Fexamples\u002F05_skills_and_plugins\u002F01_loading_agentskills\u002Fexample_skills\u002Frot13-encryption\u002FSKILL.md",[],[],{"skillNo":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":56,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":19},"01M7A5QYCZ6606SQ3H200Y1KWP","code-style-guide","Project coding standards and style guidelines. Always follow these conventions when writing or reviewing code.","https:\u002F\u002Fgithub.com\u002Fshivajid\u002Fgke-vibebench\u002Fblob\u002Fmain\u002F_harness\u002Fopenhands-sdk\u002Fexamples\u002F05_skills_and_plugins\u002F01_loading_agentskills\u002Fexample_skills\u002Fcode-style-guide\u002FSKILL.md",[],[],{"skillNo":75,"name":76,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":79,"publishedAt":19},"01M7A5QX5C3JV45TAX5BEEZKK2","greeting-helper","https:\u002F\u002Fgithub.com\u002Fshivajid\u002Fgke-vibebench\u002Fblob\u002Fmain\u002F_harness\u002Fopenhands-sdk\u002Fexamples\u002F01_standalone_sdk\u002F43_mixed_marketplace_skills\u002Fskills\u002Fgreeting-helper\u002FSKILL.md",[],[],{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":19},"01M7A5QF2G37DWY2DGZJ6NQXFA","manage-evals","This skill should be used when the user asks to \"trigger an eval\", \"run evaluation\", \"run swebench\", \"run gaia\", \"run benchmark\", \"compare eval runs\", \"compare evaluation results\", \"check eval regression\", \"compare benchmark results\", \"what changed in the eval\", \"diff eval runs\", or mentions triggering, comparing, or reporting on SWE-bench, GAIA, or other benchmark evaluation results. Provides workflow for triggering evaluations on different benchmarks, finding and comparing runs, and reporting performance differences.","https:\u002F\u002Fgithub.com\u002Fshivajid\u002Fgke-vibebench\u002Fblob\u002Fmain\u002F_harness\u002Fopenhands-sdk\u002F.agents\u002Fskills\u002Fmanage-evals\u002FSKILL.md",[],[],{"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":93,"publishedAt":19},"01M7A5Q93KM1G9FNT0KKVN7HKW","feature-release-rollout","This skill should be used when the user asks to \"rollout a feature\", \"complete feature release\", \"propagate SDK feature\", \"track feature support\", \"what's missing for feature X\", or mentions checking CLI\u002FGUI\u002Fdocs\u002Fblog support for SDK features. Guides agents through the multi-repository feature release workflow from SDK to docs to marketing.","https:\u002F\u002Fgithub.com\u002Fshivajid\u002Fgke-vibebench\u002Fblob\u002Fmain\u002F_harness\u002Fopenhands-sdk\u002F.agents\u002Fskills\u002Ffeature-release-rollout\u002FSKILL.md",[],[]]