[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7A3BHX6DD4ZFGF0HDXCE4SW":3,"skill-same:01M7A3BHX6DD4ZFGF0HDXCE4SW":47},{"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":25,"commitSha":26,"skillDirectory":27,"forksCount":28,"repositoryHtmlUrl":29,"repositoryHomepageUrl":6,"ownerHtmlUrl":30,"ownerBlogUrl":6,"ownerDescription":31,"updatedAt":32,"install":33,"resources":46},"01M7A3BHX6DD4ZFGF0HDXCE4SW","create-release-tag",null,"Create and push a signed, annotated NeMo Fabric stable release tag, then prepare unpublished GitHub Release and team announcement drafts for review. Use when cutting a stable release tag; not for beta or release-candidate tags.","leemiracle\u002Fwork4ai","leemiracle","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F10385913?v=4","01M79YCHARF56CHMGGTECMZN8Z","lee","01M79YCHBY9VH2CJW4P65D3DHR",4,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fleemiracle\u002Fwork4ai\u002Fblob\u002Fmain\u002F讲透宇宙\u002F05-侦\u002F讲透NVIDIA\u002FNeMo-Fabric\u002Frepo-docs\u002F.agents\u002Fskills\u002Fcreate-release-tag\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: create-release-tag\ndescription: Create and push a signed, annotated NeMo Fabric stable release tag, then prepare unpublished GitHub Release and team announcement drafts for review. Use when cutting a stable release tag; not for beta or release-candidate tags.\nauthor: NVIDIA Corporation and Affiliates\nlicense: Apache-2.0\n---\n\n# Create a Release Tag\n\nRequire the user to provide the stable release version in exact\n`\u003Cmajor>.\u003Cminor>.\u003Cpatch>` form. Do not infer it from package metadata or a\nbranch name, and do not edit package metadata while creating the tag.\n\n```bash\nRELEASE_VERSION=\"\u003Cuser-provided-major.minor.patch>\"\nif [[ ! \"${RELEASE_VERSION}\" =~ ^[0-9]+\\.[0-9]+\\.[0-9]+$ ]]; then\n  echo \"Error: release version must be \u003Cmajor>.\u003Cminor>.\u003Cpatch>\" >&2\n  exit 1\nfi\nRELEASE_BRANCH=\"release\u002F$(printf '%s' \"${RELEASE_VERSION}\" | cut -d. -f1,2)\"\nRELEASE_TAG=\"v${RELEASE_VERSION}\"\n\nif ! git ls-remote --exit-code --heads upstream \"refs\u002Fheads\u002F${RELEASE_BRANCH}\" >\u002Fdev\u002Fnull; then\n  echo \"Error: remote release branch ${RELEASE_BRANCH} does not exist on upstream\" >&2\n  exit 1\nfi\n\ngit fetch upstream \"${RELEASE_BRANCH}\" --tags\n```\n\n## Create and Verify the Tag\n\nAssume `upstream` is the NVIDIA repository remote. Preserve user changes: do\nnot stash, discard, or switch away from a dirty worktree. The remote release\nbranch check must succeed before switching to the release branch.\n\nRun the remaining commands in one noninteractive Bash session. Record the\nuser's original checkout and install this exit trap before switching branches.\nThe trap returns to the original named branch (or detached commit) after the\nworkflow succeeds or encounters an error, but only if this workflow changed the\ncheckout.\n\n```bash\nset -euo pipefail\nORIGINAL_BRANCH=\"$(git branch --show-current)\"\nORIGINAL_HEAD=\"$(git rev-parse --verify HEAD)\"\nCHECKOUT_CHANGED=false\n\nrestore_checkout() {\n  local outcome=$?\n  trap - EXIT\n  if [[ \"${CHECKOUT_CHANGED}\" == true ]]; then\n    if [[ -n \"${ORIGINAL_BRANCH}\" ]]; then\n      git switch \"${ORIGINAL_BRANCH}\" || outcome=1\n    else\n      git switch --detach \"${ORIGINAL_HEAD}\" || outcome=1\n    fi\n  fi\n  exit \"${outcome}\"\n}\ntrap restore_checkout EXIT\n```\n\nRequire the selected release commit and package version to match upstream. Do\nnot create the tag when either the local or upstream repository already has a\ntag with the exact release name.\n\n```bash\nif [[ \"${ORIGINAL_BRANCH}\" != \"${RELEASE_BRANCH}\" ]]; then\n  git switch \"${RELEASE_BRANCH}\"\n  CHECKOUT_CHANGED=true\nfi\ngit pull --ff-only upstream \"${RELEASE_BRANCH}\"\n\ntest -z \"$(git status --porcelain)\"\nRELEASE_SHA=\"$(git rev-parse HEAD)\"\nREMOTE_RELEASE_SHA=\"$(git rev-parse \"upstream\u002F${RELEASE_BRANCH}^{commit}\")\"\ntest \"${RELEASE_SHA}\" = \"${REMOTE_RELEASE_SHA}\"\ntest \"$(just normalize-release-tag \"${RELEASE_TAG}\")\" = \"${RELEASE_VERSION}\"\nCURRENT_VERSION=\"$(python -c \"import tomllib; print(tomllib.load(open('Cargo.toml', 'rb'))['workspace']['package']['version'])\")\"\ntest \"${CURRENT_VERSION}\" = \"${RELEASE_VERSION}\"\n\nif git rev-parse --verify --quiet \"refs\u002Ftags\u002F${RELEASE_TAG}\" >\u002Fdev\u002Fnull; then\n  echo \"Error: local tag ${RELEASE_TAG} already exists\" >&2\n  exit 1\nfi\nif git ls-remote --exit-code --tags upstream \"refs\u002Ftags\u002F${RELEASE_TAG}\" >\u002Fdev\u002Fnull; then\n  echo \"Error: remote tag ${RELEASE_TAG} already exists\" >&2\n  exit 1\nfi\n\ngit tag -s -a \\\n  -m \"NVIDIA NeMo Fabric ${RELEASE_VERSION}\" \\\n  \"${RELEASE_TAG}\" \\\n  \"${RELEASE_SHA}\"\n\ngit tag -v \"${RELEASE_TAG}\"\ngit show \"${RELEASE_TAG}\"\ntest \"$(git rev-parse \"${RELEASE_TAG}^{commit}\")\" = \"${RELEASE_SHA}\"\n\ngit push upstream \"refs\u002Ftags\u002F${RELEASE_TAG}\"\n```\n\nStop on any failed check. Do not force-update, replace, or delete an existing\nlocal or remote tag.\n\n## Draft the GitHub Release\n\nAfter the tag push succeeds, create a draft GitHub Release for that exact tag.\nDo not publish the release. Determine the previous release tag from GitHub's\nlatest published, non-draft, non-prerelease release. Do not infer it from local\ntag ordering.\n\n```bash\nGITHUB_REPOSITORY=\"NVIDIA\u002FNeMo-Fabric\"\nPREVIOUS_RELEASE_TAG=\"$(\n  gh api \"repos\u002F${GITHUB_REPOSITORY}\u002Freleases\u002Flatest\" --jq '.tag_name'\n)\"\ntest -n \"${PREVIOUS_RELEASE_TAG}\"\ntest \"${PREVIOUS_RELEASE_TAG}\" != \"${RELEASE_TAG}\"\n\nif ! git rev-parse --verify --quiet \"refs\u002Ftags\u002F${PREVIOUS_RELEASE_TAG}\" >\u002Fdev\u002Fnull; then\n  git fetch upstream \"refs\u002Ftags\u002F${PREVIOUS_RELEASE_TAG}:refs\u002Ftags\u002F${PREVIOUS_RELEASE_TAG}\"\nfi\n\nRELEASE_NOTES_URL=\"https:\u002F\u002Fdocs.nvidia.com\u002Fnemo\u002Ffabric\u002Fabout-nemo-fabric\u002Frelease-notes\"\nCOMPARISON_URL=\"https:\u002F\u002Fgithub.com\u002F${GITHUB_REPOSITORY}\u002Fcompare\u002F${PREVIOUS_RELEASE_TAG}...${RELEASE_TAG}\"\n```\n\nRead the tagged release-notes page so the draft describes the content that was\nactually released, not later working-tree edits:\n\n```bash\ngit show \\\n  \"${RELEASE_TAG}:docs\u002Fabout-nemo-fabric\u002Frelease-notes.mdx\"\n```\n\nAlso gather the comparison evidence with the existing read-only helper:\n\n```bash\npython3 .agents\u002Fskills\u002Fdraft-release-notes\u002Fscripts\u002Fcollect_release_evidence.py \\\n  --previous \"${PREVIOUS_RELEASE_TAG}\" \\\n  --current \"${RELEASE_TAG}\" \\\n  --version \"${RELEASE_VERSION}\"\n```\n\nUse GitHub's generated notes only to identify included pull requests and\npotential new contributors. Verify that evidence before including it; do not\nsubstitute the generated text for the curated release-notes page.\n\n```bash\ngh api --method POST \\\n  \"repos\u002F${GITHUB_REPOSITORY}\u002Freleases\u002Fgenerate-notes\" \\\n  -f \"tag_name=${RELEASE_TAG}\" \\\n  -f \"previous_tag_name=${PREVIOUS_RELEASE_TAG}\"\n```\n\nDraft a condensed release body rather than reproducing the full release-notes\npage. Include only the highest-impact user-facing changes, keep each bullet\nbrief, and use the detailed release-notes link for supporting context. Do not\ncopy full paragraphs or exhaustive lists from the source page.\n\nUse a temporary Markdown file with this exact structure:\n\n```markdown\n# NVIDIA NeMo Fabric \u003Cversion>\n\n\u003COne or two sentences summarizing the release.>\n\n## At a Glance\n\n### New\n\n- \u003CNotable new capability>\n\n### Changed\n\n- \u003CNotable behavior or experience change>\n\n### Breaking Changes\n\n- **\u003CAffected area>:** \u003CWhat changed and what users must do.>\n  [Migration details](\u003Cabsolute-documentation-url>)\n\n## Learn More\n\n- [Detailed release notes](\u003Cabsolute-documentation-url>)\n- [Full changelog](\u003Ccomparison-url>)\n\n## New Contributors\n\n- \u003CContributor and contribution>\n\n```\n\nReplace `\u003Cversion>` with `${RELEASE_VERSION}`, without the leading `v`. Derive\nthe summary, `New`, `Changed`, and `Breaking Changes` content from the tagged\n`docs\u002Fabout-nemo-fabric\u002Frelease-notes.mdx`. Link migration items to the most\nspecific absolute documentation URL available. Use `${RELEASE_NOTES_URL}` for\nthe detailed release-notes link and `${COMPARISON_URL}` for both changelog\nlinks. List only verified first-time contributors from the comparison. Use\n`- None.` under any category with no applicable entries so every heading in the\ntemplate remains present.\n\nReview the completed body for unsupported claims, unresolved placeholders, and\nrelative URLs. Then create and verify the draft. `--verify-tag` is required so\nGitHub cannot create a different tag implicitly. The title must be the exact tag\nname.\n\n```bash\nRELEASE_BODY_PATH=\"\u003Ctemporary-markdown-file>\"\n\nif gh release view \"${RELEASE_TAG}\" \\\n  --repo \"${GITHUB_REPOSITORY}\" >\u002Fdev\u002Fnull 2>&1; then\n  echo \"Error: a GitHub Release for ${RELEASE_TAG} already exists\" >&2\n  exit 1\nfi\n\ngh release create \"${RELEASE_TAG}\" \\\n  --repo \"${GITHUB_REPOSITORY}\" \\\n  --draft \\\n  --title \"${RELEASE_TAG}\" \\\n  --notes-file \"${RELEASE_BODY_PATH}\" \\\n  --verify-tag\n\ntest \"$(gh release view \"${RELEASE_TAG}\" \\\n  --repo \"${GITHUB_REPOSITORY}\" \\\n  --json isDraft \\\n  --jq '.isDraft')\" = \"true\"\ntest \"$(gh release view \"${RELEASE_TAG}\" \\\n  --repo \"${GITHUB_REPOSITORY}\" \\\n  --json name \\\n  --jq '.name')\" = \"${RELEASE_TAG}\"\n\nDRAFT_EDIT_URL=\"https:\u002F\u002Fgithub.com\u002F${GITHUB_REPOSITORY}\u002Freleases\u002Fedit\u002F${RELEASE_TAG}\"\nprintf 'Review the draft release before publishing: %s\\n' \"${DRAFT_EDIT_URL}\"\n```\n\nPresent `${DRAFT_EDIT_URL}` to the user as a clickable link. Tell the user to\nreview the title and body before clicking **Publish release**. Do not run\n`gh release edit --draft=false`, call the publish API, or otherwise publish the\nrelease as part of this skill.\n\n## Draft the Team Release Announcement\n\nDraft an announcement suitable for a team communication platform. Make it shorter and more condensed than the GitHub Release body: use a one-line description and include only the most important features. Do not copy paragraphs, exhaustive lists, contributor details, or changelog details from the release notes.\n\nCreate the `.tmp` directory if needed and save the announcement at the exact\npath `.tmp\u002Fdraft-${RELEASE_VERSION}release-announce.md`:\n\n```bash\nmkdir -p .tmp\nANNOUNCEMENT_PATH=\".tmp\u002Fdraft-${RELEASE_VERSION}release-announce.md\"\nTAGGED_RELEASE_NOTES_URL=\"https:\u002F\u002Fgithub.com\u002F${GITHUB_REPOSITORY}\u002Fblob\u002F${RELEASE_TAG}\u002Fdocs\u002Fabout-nemo-fabric\u002Frelease-notes.mdx\"\n```\n\nUse this structure:\n\n```markdown\n:mega: NVIDIA NeMo Fabric \u003Cversion> is here! :mega:\n\n\u003Cshort one-line description>\n\nWhat’s new in \u003Cversion>?\n\u003C!-- List the most important features here there should be 3-4 bullet points -->\n* \u003Cemoji> \u003Ckey feature>\n\n\u003Cif there are breaking changes>\n:warning: Breaking change: \u003Cchange>\n:warning: Breaking change: \u003Cchange>\n\u003C\u002Fif there are breaking changes>\n\nLearn more and get started:\n\n:book: Release Notes: \u003Clink to tagged release-notes.mdx file in GitHub>\n:computer: GitHub: https:\u002F\u002Fgithub.com\u002FNVIDIA\u002FNeMo-Fabric\n```\n\nReplace `\u003Cversion>` with `${RELEASE_VERSION}`, without the leading `v`, and use\n`${TAGGED_RELEASE_NOTES_URL}` for the release-notes link. Select only the\nhighest-impact features from the tagged release-notes page and give each a\nrelevant emoji. Include one `:warning:` line per verified breaking change;\nomit the entire breaking-change block when there are none. Remove every\nplaceholder before saving the file.\n\nPresent `${ANNOUNCEMENT_PATH}` to the user together with `${DRAFT_EDIT_URL}`.\nDo not post or send the announcement as part of this skill.\n","# Create a Release Tag\n\nRequire the user to provide the stable release version in exact\n`\u003Cmajor>.\u003Cminor>.\u003Cpatch>` form. Do not infer it from package metadata or a\nbranch name, and do not edit package metadata while creating the tag.\n\n```bash\nRELEASE_VERSION=\"\u003Cuser-provided-major.minor.patch>\"\nif [[ ! \"${RELEASE_VERSION}\" =~ ^[0-9]+\\.[0-9]+\\.[0-9]+$ ]]; then\n  echo \"Error: release version must be \u003Cmajor>.\u003Cminor>.\u003Cpatch>\" >&2\n  exit 1\nfi\nRELEASE_BRANCH=\"release\u002F$(printf '%s' \"${RELEASE_VERSION}\" | cut -d. -f1,2)\"\nRELEASE_TAG=\"v${RELEASE_VERSION}\"\n\nif ! git ls-remote --exit-code --heads upstream \"refs\u002Fheads\u002F${RELEASE_BRANCH}\" >\u002Fdev\u002Fnull; then\n  echo \"Error: remote release branch ${RELEASE_BRANCH} does not exist on upstream\" >&2\n  exit 1\nfi\n\ngit fetch upstream \"${RELEASE_BRANCH}\" --tags\n```\n\n## Create and Verify the Tag\n\nAssume `upstream` is the NVIDIA repository remote. Preserve user changes: do\nnot stash, discard, or switch away from a dirty worktree. The remote release\nbranch check must succeed before switching to the release branch.\n\nRun the remaining commands in one noninteractive Bash session. Record the\nuser's original checkout and install this exit trap before switching branches.\nThe trap returns to the original named branch (or detached commit) after the\nworkflow succeeds or encounters an error, but only if this workflow changed the\ncheckout.\n\n```bash\nset -euo pipefail\nORIGINAL_BRANCH=\"$(git branch --show-current)\"\nORIGINAL_HEAD=\"$(git rev-parse --verify HEAD)\"\nCHECKOUT_CHANGED=false\n\nrestore_checkout() {\n  local outcome=$?\n  trap - EXIT\n  if [[ \"${CHECKOUT_CHANGED}\" == true ]]; then\n    if [[ -n \"${ORIGINAL_BRANCH}\" ]]; then\n      git switch \"${ORIGINAL_BRANCH}\" || outcome=1\n    else\n      git switch --detach \"${ORIGINAL_HEAD}\" || outcome=1\n    fi\n  fi\n  exit \"${outcome}\"\n}\ntrap restore_checkout EXIT\n```\n\nRequire the selected release commit and package version to match upstream. Do\nnot create the tag when either the local or upstream repository already has a\ntag with the exact release name.\n\n```bash\nif [[ \"${ORIGINAL_BRANCH}\" != \"${RELEASE_BRANCH}\" ]]; then\n  git switch \"${RELEASE_BRANCH}\"\n  CHECKOUT_CHANGED=true\nfi\ngit pull --ff-only upstream \"${RELEASE_BRANCH}\"\n\ntest -z \"$(git status --porcelain)\"\nRELEASE_SHA=\"$(git rev-parse HEAD)\"\nREMOTE_RELEASE_SHA=\"$(git rev-parse \"upstream\u002F${RELEASE_BRANCH}^{commit}\")\"\ntest \"${RELEASE_SHA}\" = \"${REMOTE_RELEASE_SHA}\"\ntest \"$(just normalize-release-tag \"${RELEASE_TAG}\")\" = \"${RELEASE_VERSION}\"\nCURRENT_VERSION=\"$(python -c \"import tomllib; print(tomllib.load(open('Cargo.toml', 'rb'))['workspace']['package']['version'])\")\"\ntest \"${CURRENT_VERSION}\" = \"${RELEASE_VERSION}\"\n\nif git rev-parse --verify --quiet \"refs\u002Ftags\u002F${RELEASE_TAG}\" >\u002Fdev\u002Fnull; then\n  echo \"Error: local tag ${RELEASE_TAG} already exists\" >&2\n  exit 1\nfi\nif git ls-remote --exit-code --tags upstream \"refs\u002Ftags\u002F${RELEASE_TAG}\" >\u002Fdev\u002Fnull; then\n  echo \"Error: remote tag ${RELEASE_TAG} already exists\" >&2\n  exit 1\nfi\n\ngit tag -s -a \\\n  -m \"NVIDIA NeMo Fabric ${RELEASE_VERSION}\" \\\n  \"${RELEASE_TAG}\" \\\n  \"${RELEASE_SHA}\"\n\ngit tag -v \"${RELEASE_TAG}\"\ngit show \"${RELEASE_TAG}\"\ntest \"$(git rev-parse \"${RELEASE_TAG}^{commit}\")\" = \"${RELEASE_SHA}\"\n\ngit push upstream \"refs\u002Ftags\u002F${RELEASE_TAG}\"\n```\n\nStop on any failed check. Do not force-update, replace, or delete an existing\nlocal or remote tag.\n\n## Draft the GitHub Release\n\nAfter the tag push succeeds, create a draft GitHub Release for that exact tag.\nDo not publish the release. Determine the previous release tag from GitHub's\nlatest published, non-draft, non-prerelease release. Do not infer it from local\ntag ordering.\n\n```bash\nGITHUB_REPOSITORY=\"NVIDIA\u002FNeMo-Fabric\"\nPREVIOUS_RELEASE_TAG=\"$(\n  gh api \"repos\u002F${GITHUB_REPOSITORY}\u002Freleases\u002Flatest\" --jq '.tag_name'\n)\"\ntest -n \"${PREVIOUS_RELEASE_TAG}\"\ntest \"${PREVIOUS_RELEASE_TAG}\" != \"${RELEASE_TAG}\"\n\nif ! git rev-parse --verify --quiet \"refs\u002Ftags\u002F${PREVIOUS_RELEASE_TAG}\" >\u002Fdev\u002Fnull; then\n  git fetch upstream \"refs\u002Ftags\u002F${PREVIOUS_RELEASE_TAG}:refs\u002Ftags\u002F${PREVIOUS_RELEASE_TAG}\"\nfi\n\nRELEASE_NOTES_URL=\"https:\u002F\u002Fdocs.nvidia.com\u002Fnemo\u002Ffabric\u002Fabout-nemo-fabric\u002Frelease-notes\"\nCOMPARISON_URL=\"https:\u002F\u002Fgithub.com\u002F${GITHUB_REPOSITORY}\u002Fcompare\u002F${PREVIOUS_RELEASE_TAG}...${RELEASE_TAG}\"\n```\n\nRead the tagged release-notes page so the draft describes the content that was\nactually released, not later working-tree edits:\n\n```bash\ngit show \\\n  \"${RELEASE_TAG}:docs\u002Fabout-nemo-fabric\u002Frelease-notes.mdx\"\n```\n\nAlso gather the comparison evidence with the existing read-only helper:\n\n```bash\npython3 .agents\u002Fskills\u002Fdraft-release-notes\u002Fscripts\u002Fcollect_release_evidence.py \\\n  --previous \"${PREVIOUS_RELEASE_TAG}\" \\\n  --current \"${RELEASE_TAG}\" \\\n  --version \"${RELEASE_VERSION}\"\n```\n\nUse GitHub's generated notes only to identify included pull requests and\npotential new contributors. Verify that evidence before including it; do not\nsubstitute the generated text for the curated release-notes page.\n\n```bash\ngh api --method POST \\\n  \"repos\u002F${GITHUB_REPOSITORY}\u002Freleases\u002Fgenerate-notes\" \\\n  -f \"tag_name=${RELEASE_TAG}\" \\\n  -f \"previous_tag_name=${PREVIOUS_RELEASE_TAG}\"\n```\n\nDraft a condensed release body rather than reproducing the full release-notes\npage. Include only the highest-impact user-facing changes, keep each bullet\nbrief, and use the detailed release-notes link for supporting context. Do not\ncopy full paragraphs or exhaustive lists from the source page.\n\nUse a temporary Markdown file with this exact structure:\n\n```markdown\n# NVIDIA NeMo Fabric \u003Cversion>\n\n\u003COne or two sentences summarizing the release.>\n\n## At a Glance\n\n### New\n\n- \u003CNotable new capability>\n\n### Changed\n\n- \u003CNotable behavior or experience change>\n\n### Breaking Changes\n\n- **\u003CAffected area>:** \u003CWhat changed and what users must do.>\n  [Migration details](\u003Cabsolute-documentation-url>)\n\n## Learn More\n\n- [Detailed release notes](\u003Cabsolute-documentation-url>)\n- [Full changelog](\u003Ccomparison-url>)\n\n## New Contributors\n\n- \u003CContributor and contribution>\n\n```\n\nReplace `\u003Cversion>` with `${RELEASE_VERSION}`, without the leading `v`. Derive\nthe summary, `New`, `Changed`, and `Breaking Changes` content from the tagged\n`docs\u002Fabout-nemo-fabric\u002Frelease-notes.mdx`. Link migration items to the most\nspecific absolute documentation URL available. Use `${RELEASE_NOTES_URL}` for\nthe detailed release-notes link and `${COMPARISON_URL}` for both changelog\nlinks. List only verified first-time contributors from the comparison. Use\n`- None.` under any category with no applicable entries so every heading in the\ntemplate remains present.\n\nReview the completed body for unsupported claims, unresolved placeholders, and\nrelative URLs. Then create and verify the draft. `--verify-tag` is required so\nGitHub cannot create a different tag implicitly. The title must be the exact tag\nname.\n\n```bash\nRELEASE_BODY_PATH=\"\u003Ctemporary-markdown-file>\"\n\nif gh release view \"${RELEASE_TAG}\" \\\n  --repo \"${GITHUB_REPOSITORY}\" >\u002Fdev\u002Fnull 2>&1; then\n  echo \"Error: a GitHub Release for ${RELEASE_TAG} already exists\" >&2\n  exit 1\nfi\n\ngh release create \"${RELEASE_TAG}\" \\\n  --repo \"${GITHUB_REPOSITORY}\" \\\n  --draft \\\n  --title \"${RELEASE_TAG}\" \\\n  --notes-file \"${RELEASE_BODY_PATH}\" \\\n  --verify-tag\n\ntest \"$(gh release view \"${RELEASE_TAG}\" \\\n  --repo \"${GITHUB_REPOSITORY}\" \\\n  --json isDraft \\\n  --jq '.isDraft')\" = \"true\"\ntest \"$(gh release view \"${RELEASE_TAG}\" \\\n  --repo \"${GITHUB_REPOSITORY}\" \\\n  --json name \\\n  --jq '.name')\" = \"${RELEASE_TAG}\"\n\nDRAFT_EDIT_URL=\"https:\u002F\u002Fgithub.com\u002F${GITHUB_REPOSITORY}\u002Freleases\u002Fedit\u002F${RELEASE_TAG}\"\nprintf 'Review the draft release before publishing: %s\\n' \"${DRAFT_EDIT_URL}\"\n```\n\nPresent `${DRAFT_EDIT_URL}` to the user as a clickable link. Tell the user to\nreview the title and body before clicking **Publish release**. Do not run\n`gh release edit --draft=false`, call the publish API, or otherwise publish the\nrelease as part of this skill.\n\n## Draft the Team Release Announcement\n\nDraft an announcement suitable for a team communication platform. Make it shorter and more condensed than the GitHub Release body: use a one-line description and include only the most important features. Do not copy paragraphs, exhaustive lists, contributor details, or changelog details from the release notes.\n\nCreate the `.tmp` directory if needed and save the announcement at the exact\npath `.tmp\u002Fdraft-${RELEASE_VERSION}release-announce.md`:\n\n```bash\nmkdir -p .tmp\nANNOUNCEMENT_PATH=\".tmp\u002Fdraft-${RELEASE_VERSION}release-announce.md\"\nTAGGED_RELEASE_NOTES_URL=\"https:\u002F\u002Fgithub.com\u002F${GITHUB_REPOSITORY}\u002Fblob\u002F${RELEASE_TAG}\u002Fdocs\u002Fabout-nemo-fabric\u002Frelease-notes.mdx\"\n```\n\nUse this structure:\n\n```markdown\n:mega: NVIDIA NeMo Fabric \u003Cversion> is here! :mega:\n\n\u003Cshort one-line description>\n\nWhat’s new in \u003Cversion>?\n\u003C!-- List the most important features here there should be 3-4 bullet points -->\n* \u003Cemoji> \u003Ckey feature>\n\n\u003Cif there are breaking changes>\n:warning: Breaking change: \u003Cchange>\n:warning: Breaking change: \u003Cchange>\n\u003C\u002Fif there are breaking changes>\n\nLearn more and get started:\n\n:book: Release Notes: \u003Clink to tagged release-notes.mdx file in GitHub>\n:computer: GitHub: https:\u002F\u002Fgithub.com\u002FNVIDIA\u002FNeMo-Fabric\n```\n\nReplace `\u003Cversion>` with `${RELEASE_VERSION}`, without the leading `v`, and use\n`${TAGGED_RELEASE_NOTES_URL}` for the release-notes link. Select only the\nhighest-impact features from the tagged release-notes page and give each a\nrelevant emoji. Include one `:warning:` line per verified breaking change;\nomit the entire breaking-change block when there are none. Remove every\nplaceholder before saving the file.\n\nPresent `${ANNOUNCEMENT_PATH}` to the user together with `${DRAFT_EDIT_URL}`.\nDo not post or send the announcement as part of this skill.\n",{"name":5,"author":24,"license":15,"description":7},"NVIDIA Corporation and Affiliates","main","ffa016d3c9a8d32821f71f6d9d916c30e04fcb67","讲透宇宙\u002F05-侦\u002F讲透NVIDIA\u002FNeMo-Fabric\u002Frepo-docs\u002F.agents\u002Fskills\u002Fcreate-release-tag",0,"https:\u002F\u002Fgithub.com\u002Fleemiracle\u002Fwork4ai","https:\u002F\u002Fgithub.com\u002Fleemiracle","i have some experience that make me better, so i want more. follow and star me would be a good choice.","2026-11-12 17:16:40",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add leemiracle\u002Fwork4ai --skill create-release-tag",{"tool":39,"command":40},"bunx","bunx skills add leemiracle\u002Fwork4ai --skill create-release-tag",{"tool":42,"command":43},"pnpm","pnpm dlx skills add leemiracle\u002Fwork4ai --skill create-release-tag","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fleemiracle\u002Fwork4ai\u002Fblob\u002Fmain\u002F讲透宇宙\u002F05-侦\u002F讲透NVIDIA\u002FNeMo-Fabric\u002Frepo-docs\u002F.agents\u002Fskills\u002Fcreate-release-tag\u002FSKILL.md",true,[],[48,55,62,69,76,83],{"skillNo":49,"name":50,"nameZh":6,"description":51,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":52,"categories":53,"keywords":54,"publishedAt":19},"01M7A57J4E78QJZS8MA72P82DV","agentic-ecology-ui","Guidelines and templates for creating a generic web UI to visualize, rank, filter, and annotate vector databases. The UI has a hierarchical structure covering database selection, label selection\u002Fdefinition, ranking\u002Ffiltering configuration, and row visualization\u002Fannotation. Use when building, serving, or adapting an interactive web UI for Hoplite vector databases.","https:\u002F\u002Fgithub.com\u002Fleemiracle\u002Fwork4ai\u002Fblob\u002Fmain\u002F讲透宇宙\u002F05-侦\u002F讲透google-deepmind\u002Fagentic_ecology\u002Frepo-docs\u002Fskills\u002Fagentic-ecology-ui\u002FSKILL.md",[],[],{"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":61,"publishedAt":19},"01M7A57C4RGS1A7VM6CNPNQDBH","agentic-ecology-init","Initializes a local uv-managed project directory for agentic ecology workloads. Sets up Python dependencies using reference pyproject.toml and uv.lock, configures workspace rules, and ensures Agentic Ecology skills are discoverable. Use when initializing a new project workspace or bootstrapping a clean environment.","https:\u002F\u002Fgithub.com\u002Fleemiracle\u002Fwork4ai\u002Fblob\u002Fmain\u002F讲透宇宙\u002F05-侦\u002F讲透google-deepmind\u002Fagentic_ecology\u002Frepo-docs\u002Fskills\u002Fagentic-ecology-init\u002FSKILL.md",[],[],{"skillNo":63,"name":64,"nameZh":6,"description":65,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":66,"categories":67,"keywords":68,"publishedAt":19},"01M7A576Q1GYF5GAQCWGPPDQWZ","agentic-ecology-camera-traps","Provides capabilities to run SpeciesNet detector and classifier on camera trap images, extract crop-level feature embeddings, and populate a Hoplite vector database for downstream search and agile modeling. Use when ingesting camera trap images, classifying wildlife photos, or indexing camera trap data.","https:\u002F\u002Fgithub.com\u002Fleemiracle\u002Fwork4ai\u002Fblob\u002Fmain\u002F讲透宇宙\u002F05-侦\u002F讲透google-deepmind\u002Fagentic_ecology\u002Frepo-docs\u002Fskills\u002Fagentic-ecology-camera-traps\u002FSKILL.md",[],[],{"skillNo":70,"name":71,"nameZh":6,"description":72,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":73,"categories":74,"keywords":75,"publishedAt":19},"01M7A5708M54MMTKXQARDCJQMW","agentic-ecology-bioacoustics","Provides bioacoustic analysis capabilities for ecologists and researchers using the perch-hoplite Python package. A typical use case is to use agile modeling to bootstrap the creation and deployment of a bespoke detector for targeted species on an existing collection of passive acoustic monitoring recordings. Use when processing and annotating audio recordings for bioacoustic applications.","https:\u002F\u002Fgithub.com\u002Fleemiracle\u002Fwork4ai\u002Fblob\u002Fmain\u002F讲透宇宙\u002F05-侦\u002F讲透google-deepmind\u002Fagentic_ecology\u002Frepo-docs\u002Fskills\u002Fagentic-ecology-bioacoustics\u002FSKILL.md",[],[],{"skillNo":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":82,"publishedAt":19},"01M7A53GYCZY3AT9C2FR44TC35","sample-skill","Sample skill used by agent-env integration tests. Exercises SKILL.md parsing plus supporting scripts and references.","https:\u002F\u002Fgithub.com\u002Fleemiracle\u002Fwork4ai\u002Fblob\u002Fmain\u002F讲透宇宙\u002F05-侦\u002F讲透browser-use\u002Fagentenv-framework\u002Frepo-docs\u002Ftst\u002Fdata\u002Fskills\u002Fsample_skill\u002FSKILL.md",[],[],{"skillNo":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":89,"publishedAt":19},"01M7A4KD50DHSNH1SCNKP1J6S1","simready-foundation-validate-foundation-change","Use for auditing SimReady requirement, validator, feature, profile, adapter, test, and skill consistency.","https:\u002F\u002Fgithub.com\u002Fleemiracle\u002Fwork4ai\u002Fblob\u002Fmain\u002F讲透宇宙\u002F05-侦\u002F讲透NVIDIA\u002Fsimready-foundation\u002Frepo-docs\u002F.codex\u002Fskills\u002Fsimready-foundation-validate-foundation-change\u002FSKILL.md",[],[]]