Version Release
NG-ZORRO/ng-zorro-antd
NG-ZORRO/ng-zorro-antd repository release workflow. An agent skill from NG-ZORRO/ng-zorro-antd.
Prepares and validates Agent Landing Zone Orchestrator releases.
Install Orchestrator Release
$ npx skills add Azure/agent-app-orchestrator --skill orchestrator-release -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install Azure/agent-app-orchestrator orchestrator-release --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/Azure/agent-app-orchestrator.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.github/skills/orchestrator-release .claude/skills/orchestrator-release && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "orchestrator-release" agent skill from https://github.com/Azure/agent-app-orchestrator/tree/main/.github/skills/orchestrator-release into .claude/skills/orchestrator-release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "orchestrator-release", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/Azure/agent-app-orchestrator/tree/main/.github/skills/orchestrator-releaseType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add Azure/agent-app-orchestrator --skill orchestrator-release -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install Azure/agent-app-orchestrator orchestrator-release --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Azure/agent-app-orchestrator.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.github/skills/orchestrator-release .agents/skills/orchestrator-release && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "orchestrator-release" agent skill from https://github.com/Azure/agent-app-orchestrator/tree/main/.github/skills/orchestrator-release into .agents/skills/orchestrator-release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "orchestrator-release", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add Azure/agent-app-orchestrator --skill orchestrator-release -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install Azure/agent-app-orchestrator orchestrator-release --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Azure/agent-app-orchestrator.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.github/skills/orchestrator-release .cursor/skills/orchestrator-release && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "orchestrator-release" agent skill from https://github.com/Azure/agent-app-orchestrator/tree/main/.github/skills/orchestrator-release into .cursor/skills/orchestrator-release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "orchestrator-release", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/Azure/agent-app-orchestrator.git --path .github/skills/orchestrator-release--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add Azure/agent-app-orchestrator --skill orchestrator-release -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install Azure/agent-app-orchestrator orchestrator-release --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Azure/agent-app-orchestrator.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.github/skills/orchestrator-release .gemini/skills/orchestrator-release && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "orchestrator-release" agent skill from https://github.com/Azure/agent-app-orchestrator/tree/main/.github/skills/orchestrator-release into .gemini/skills/orchestrator-release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "orchestrator-release", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install Azure/agent-app-orchestrator orchestrator-releaseInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add Azure/agent-app-orchestrator --skill orchestrator-release -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/Azure/agent-app-orchestrator.git skills-src && mkdir -p .github/skills && cp -r skills-src/.github/skills/orchestrator-release .github/skills/orchestrator-release && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "orchestrator-release" agent skill from https://github.com/Azure/agent-app-orchestrator/tree/main/.github/skills/orchestrator-release into .github/skills/orchestrator-release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "orchestrator-release", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add Azure/agent-app-orchestrator --skill orchestrator-release -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install Azure/agent-app-orchestrator orchestrator-release --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Azure/agent-app-orchestrator.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.github/skills/orchestrator-release .opencode/skills/orchestrator-release && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "orchestrator-release" agent skill from https://github.com/Azure/agent-app-orchestrator/tree/main/.github/skills/orchestrator-release into .opencode/skills/orchestrator-release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "orchestrator-release", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
orchestrator-release- GitHub stars
- 103
- Token cost
- ~426 tokens
- SKILL.md length
- 200 words
- Files
- 1
- Skills in repo
- 5
- Repo updated
- First seen
- Licence
- MIT
At a glance
Prepares and validates Agent Landing Zone Orchestrator releases.
- Works in 10 steps: Determine the intended semantic version… → Set root VERSION to X.Y.Z without a v… → Replace the single [Unreleased] heading… → …
- Changelog entries
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Release branches
What it does
Orchestrator Release is an agent skill from Azure/agent-app-orchestrator, published by the product's own GitHub organization. Prepares and validates Agent Landing Zone Orchestrator releases. Use for VERSION, changelog entries, release branches, tags, GitHub Release notes, and synchronized develop follow-up.
Its SKILL.md is about 430 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Development, covering Changelog and release notes, Cloud architecture and Multi-agent orchestration. It works with GitHub and Microsoft Azure. The repository describes itself as: Agent orchestration service for the Agent Landing Zone, built on Microsoft Foundry Agent Service and Microsoft Agent Framework. Coordinates specialized agents for conversational… The licence is MIT.
When your agent uses it
- Changelog entries
- Release branches
- GitHub Release notes
- Synchronized develop follow-up
Example prompts
- “Use the orchestrator-release skill to prepare and validates Agent Landing Zone Orchestrator releases”
- “/orchestrator-release”
Workflow steps
10 steps, taken from the first numbered list in SKILL.md.
- Determine the intended semantic version and create release/X.Y.Z from
- Set root VERSION to X.Y.Z without a v prefix.
- Replace the single [Unreleased] heading with
- Verify the branch, VERSION, changelog, intended tag, and GitHub Release
- Keep only release preparation on the branch and target the pull request to
- Validate the exact commit with the relevant pytest, frontend, deployment,
- Keep changelog, release notes, and published operator documentation
- Use exactly vX.Y.Z for both the Git tag and GitHub Release title.
- After pushing the release branch, restore one empty [Unreleased] section
- Re-fetch published release notes and verify headings, lists, tables, and
What it can do on your machine
Read from SKILL.md and the folder at commit 0e67231. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Orchestrator Release loads about 426 tokens when it runs. Until then it costs about 51 tokens; SKILL.md has 200 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from Azure/agent-app-orchestrator at commit 0e67231, republished under its MIT licence (© Azure). 200 words, ~426 tokens.
Download SKILL.mdSave it as
.claude/skills/orchestrator-release/SKILL.md (or your agent's skills folder).- name
- orchestrator-release
- description
- Prepares and validates Agent Landing Zone Orchestrator releases. Use for VERSION, changelog entries, release branches, tags, GitHub Release notes, and synchronized develop follow-up.
Agent Landing Zone Orchestrator release
Read .github/copilot-instructions.md and
.github/instructions/release.instructions.md completely before changing a
release artifact.
- Determine the intended semantic version and create
release/X.Y.Zfromdevelop. - Set root
VERSIONtoX.Y.Zwithout avprefix. - Replace the single
[Unreleased]heading with## [vX.Y.Z] - YYYY-MM-DD; do not leave[Unreleased]on the release branch. - Verify the branch,
VERSION, changelog, intended tag, and GitHub Release title are synchronized, accounting for their required prefix differences. - Keep only release preparation on the branch and target the pull request to
main. - Validate the exact commit with the relevant pytest, frontend, deployment, contract, and Copilot asset checks.
- Keep changelog, release notes, and published operator documentation consistent and free of secrets or private Azure environment names.
- Use exactly
vX.Y.Zfor both the Git tag and GitHub Release title. - After pushing the release branch, restore one empty
[Unreleased]section at the top ofdevelop, commit it, and pushdevelop. - Re-fetch published release notes and verify headings, lists, tables, and sanitized content.
Do not publish a tag, release, package, image, or production deployment without explicit human approval. Report failed validation or version drift as a blocker rather than filling gaps by assumption.
© Azure, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in .github/skills/orchestrator-release of Azure/agent-app-orchestrator.
Open the folder on GitHubat commit 0e67231
Compare with similar skills
Orchestrator Release next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Orchestrator Release this skillAzure/agent-app-orchestrator | 103 | — | ~426 | Automated safety check: Pass | MIT | |
| Version ReleaseNG-ZORRO/ng-zorro-antd | 9.2k | — | ~3.1k | Automated safety check: Pass | MIT | |
| Azv Diagram Azure SyncAzure/AZVerify | 101 | — | ~3.7k | Automated safety check: Pass | MIT | |
| Azv Diagram Azure Sync DeepAzure/AZVerify | 101 | — | ~3.9k | Automated safety check: Pass | MIT | |
| Azv Sketch To DiagramAzure/AZVerify | 101 | — | ~3.5k | Automated safety check: Pass | MIT | |
| Recon Osinthypnguyen1209/offensive-claude | 388 | — | ~2.2k | Automated safety check: Pass | MIT |
Similar skills
- Official
Azv Diagram Azure Sync
Azure/AZVerify
Compare a Draw.io Azure architecture diagram against a live Azure environment to detect drift.
- Official
Azv Diagram Azure Sync Deep
Azure/AZVerify
Deep-compare a Draw.io Azure architecture diagram against a live Azure environment — checks both resource existence AND every tracked configuration property (SKU, size, settings, etc.) against…
- Official
Azv Sketch To Diagram
Azure/AZVerify
Convert a rough sketch or drawing of an Azure architecture into a professional Draw.io diagram using Azure-specific shapes.
Recon Osint
hypnguyen1209/offensive-claude
A skill your agent uses when mapping a target's external attack surface or gathering OSINT — subdomain enumeration, attack-surface mapping (httpx/katana/JS secrets), subdomain takeover…
- Official
Azv Diagram To Bicep
Azure/AZVerify
Generate deployment-ready Bicep templates and PowerShell scripts from an approved Draw.io Azure architecture diagram.
More from Azure/agent-app-orchestrator
- Official
Release
Azure/agent-app-orchestrator
Prepare and reconcile Agent Landing Zone Orchestrator releases, including authoritative version discovery, semantic version selection, release branches, VERSION and CHANGELOG updates, release notes…
- Official
Architecture Decision
Azure/agent-app-orchestrator
Conducts and records a verifiable Agent Landing Zone Orchestrator architectural decision.
- Official
Engineering Principles
Azure/agent-app-orchestrator
Agent Landing Zone Orchestrator architecture and implementation principles.
- Official
Documentation Consistency
Azure/agent-app-orchestrator
Keeps Agent Landing Zone Orchestrator user and operator documentation aligned with shipped behavior.
Related
Works with
Categories
Questions about Orchestrator Release
What does Orchestrator Release do?
Prepares and validates Agent Landing Zone Orchestrator releases. Orchestrator Release is an agent skill from Azure/agent-app-orchestrator, published by the product's own GitHub organization. Prepares and validates Agent Landing Zone Orchestrator releases.
When should I use Orchestrator Release?
Orchestrator Release fits situations like: changelog entries; release branches; GitHub Release notes; synchronized develop follow-up.
How do I install Orchestrator Release in Claude Code?
Run `npx skills add Azure/agent-app-orchestrator --skill orchestrator-release -a claude-code`. Or copy the skill folder (.github/skills/orchestrator-release in Azure/agent-app-orchestrator) into .claude/skills/orchestrator-release in your project. Claude Code loads it when a task matches its description.
How do I install Orchestrator Release in Codex?
Run `npx skills add Azure/agent-app-orchestrator --skill orchestrator-release -a codex`. Or copy the skill folder (.github/skills/orchestrator-release in Azure/agent-app-orchestrator) into .agents/skills/orchestrator-release in your project. Codex loads it when a task matches its description.
Can I use Orchestrator Release in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add Azure/agent-app-orchestrator --skill orchestrator-release -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/orchestrator-release, .gemini/skills/orchestrator-release, .github/skills/orchestrator-release and .opencode/skills/orchestrator-release in your project.
What does Orchestrator Release need to run?
SKILL.md names no scripts, command-line tools or credentials: Orchestrator Release is instructions for the agent only.
Does Orchestrator Release access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Orchestrator Release safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Orchestrator Release use?
Orchestrator Release is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Orchestrator Release use?
About 426 tokens (SKILL.md is roughly 1.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Orchestrator Release?
Skills that share tags, products or a category with Orchestrator Release: Version Release (NG-ZORRO/ng-zorro-antd, 9.2k stars), Azv Diagram Azure Sync (Azure/AZVerify, 101 stars), Azv Diagram Azure Sync Deep (Azure/AZVerify, 101 stars) and Azv Sketch To Diagram (Azure/AZVerify, 101 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Orchestrator Release?
Azure (a GitHub organization, an official publisher) maintains it in Azure/agent-app-orchestrator, which has 103 GitHub stars. The repository holds 5 skills in this directory. The repository was last updated on October 8, 2026.
Source: Azure/agent-app-orchestrator on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.