Official agent skill

Architecture Decision

by Azure in Azure/agent-app-orchestrator

Conducts and records a verifiable Agent Landing Zone Orchestrator architectural decision.

OfficialMITAuto-check passedDevOps & Cloud

Install Architecture Decision

skills CLI
$ npx skills add Azure/agent-app-orchestrator --skill architecture-decision -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install Azure/agent-app-orchestrator architecture-decision --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/Azure/agent-app-orchestrator.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.github/skills/architecture-decision .claude/skills/architecture-decision && rm -rf skills-src

Use ~/.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/

Facts

Skill name
architecture-decision
GitHub stars
103
Token cost
~319 tokens
SKILL.md length
126 words
Files
2 (incl. references)
Skills in repo
5
Repo updated
First seen
Licence
MIT

At a glance

Conducts and records a verifiable Agent Landing Zone Orchestrator architectural decision.

  • Works in 6 steps: Load the relevant engineering-principles… → Define the user or operator outcome,… → Compare at least two viable alternatives… → …
  • A choice alters runtime strategy boundaries
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
  • Operation with meaningful reversal cost

What it does

Architecture Decision is an agent skill from Azure/agent-app-orchestrator, published by the product's own GitHub organization. Conducts and records a verifiable Agent Landing Zone Orchestrator architectural decision. Use when a choice alters runtime strategy boundaries, contracts, identity, data, deployment, or operation with meaningful reversal cost.

Its SKILL.md is about 320 tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including reference files (for example `references/adr-template.md`).

It sits in DevOps & Cloud, covering Cloud architecture. It works with 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

  • A choice alters runtime strategy boundaries
  • Operation with meaningful reversal cost

Example prompts

  • “Use the architecture-decision skill to conduct and records a verifiable Agent Landing Zone Orchestrator architectural decision”
  • “/architecture-decision”

Workflow steps

6 steps, taken from the first numbered list in SKILL.md.

  1. Load the relevant engineering-principles references.
  2. Define the user or operator outcome, constraints, affected repositories,
  3. Compare at least two viable alternatives and the option of not changing.
  4. Evaluate FastAPI and runtime strategy boundaries, identity, authorization,
  5. Record the decision using
  6. Define fitness functions, adoption order, rollback or roll-forward, and a

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

Architecture Decision loads about 319 tokens when it runs, and up to ~662 if it reads all its reference files. Until then it costs about 62 tokens; SKILL.md has 126 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~62
When it runs · the whole SKILL.md, loaded when a task matches
~319
With references · SKILL.md plus every file in references/, read only if the agent opens them
~662

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). 126 words, ~319 tokens.

Download SKILL.mdSave it as .claude/skills/architecture-decision/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
architecture-decision
description
Conducts and records a verifiable Agent Landing Zone Orchestrator architectural decision. Use when a choice alters runtime strategy boundaries, contracts, identity, data, deployment, or operation with meaningful reversal cost.

Agent Landing Zone Orchestrator architectural decision

  1. Load the relevant engineering-principles references.
  2. Define the user or operator outcome, constraints, affected repositories, and up to five prioritized characteristics with measurable thresholds.
  3. Compare at least two viable alternatives and the option of not changing.
  4. Evaluate FastAPI and runtime strategy boundaries, identity, authorization, data and conversation compatibility, retrieval and MCP trust, deployment, cost, operation, migration, and reversibility.
  5. Record the decision using the ADR template.
  6. Define fitness functions, adoption order, rollback or roll-forward, and a review trigger.

Do not turn a framework, model, or Azure service preference into an architectural requirement. GitHub Copilot engineering agents are not runtime agent dependencies. When evidence is missing, record a time-bounded investigation and its decision criterion instead of guessing.

© 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

SKILL.md and 1 other file (references) in .github/skills/architecture-decision of Azure/agent-app-orchestrator.

  • SKILL.md
  • references/adr-template.md

Open the folder on GitHubat commit 0e67231

Compare with similar skills

Architecture Decision 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.

Architecture Decision compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Architecture Decision this skillAzure/agent-app-orchestrator103—~319Automated safety check: PassMIT
Cloud Cost Optimizationwshobson/agents40k14 repos~1.7kAutomated safety check: PassMIT
Thesvgglincker/thesvg2.8k—~1.5kAutomated safety check: PassMIT
Azure Architecture Autopilotgithub/awesome-copilot40k1 repos~1.9kAutomated safety check: PassMIT
Dangling DNS Finderanirudhbiyani/findmytakeover180—~1.8kAutomated safety check: PassGPL-3.0
Azure Bicep Skilltimothywarner-org/claude-code224—~2.9kAutomated safety check: PassMIT

Similar skills

  • Cuts cloud spend across AWS, Azure, GCP and OCI with cost tagging, rightsizing, commitment and spot pricing models, and architecture changes.

    40k GitHub starsUsed in 14 repos~1.7k tokens
    DevOps & CloudAuto-check passed
  • Thesvg

    glincker/thesvg

    Fetch brand SVG logos and cloud architecture icons (AWS, Azure, GCP) from theSVG.

    2.8k GitHub stars~1.5k tokensUpdated today
    DevOps & CloudAuto-check passed
  • Azure Architecture Autopilot

    github/awesome-copilot

    Official

    Designs Azure infrastructure from a natural-language description, or diagrams an existing resource group, then refines the design through conversation and deploys it with Bicep.

    40k GitHub starsUsed in 1 repo~1.9k tokens
    DevOps & CloudAuto-check passed
  • Dangling DNS Finder

    anirudhbiyani/findmytakeover

    Detect dangling DNS records and subdomain-takeover risks across a multi-cloud environment by running the bundled findmytakeover tool.

    180 GitHub stars~1.8k tokensUpdated 1 mo ago
    DevOps & CloudAuto-check passed
  • Azure Bicep Skill

    timothywarner-org/claude-code

    A skill your agent uses when authoring, reviewing, or refactoring Azure Bicep code.

    224 GitHub stars~2.9k tokensUpdated 2 mo ago
    DevOps & CloudAuto-check passed
  • Configure secure, high-performance connectivity between on-premises infrastructure and cloud platforms using VPN and dedicated connections.

    40k GitHub starsUsed in 11 repos~1.5k tokens
    DevOps & CloudAuto-check passed

More from Azure/agent-app-orchestrator

  • Release

    Azure/agent-app-orchestrator

    Official

    Prepare and reconcile Agent Landing Zone Orchestrator releases, including authoritative version discovery, semantic version selection, release branches, VERSION and CHANGELOG updates, release notes…

    103 GitHub stars~2.5k tokensUpdated yesterday
    Auto-check passed
  • Engineering Principles

    Azure/agent-app-orchestrator

    Official

    Agent Landing Zone Orchestrator architecture and implementation principles.

    103 GitHub stars~282 tokensUpdated yesterday
    Auto-check passed
  • Documentation Consistency

    Azure/agent-app-orchestrator

    Official

    Keeps Agent Landing Zone Orchestrator user and operator documentation aligned with shipped behavior.

    103 GitHub stars~351 tokensUpdated yesterday
    Auto-check passed
  • Orchestrator Release

    Azure/agent-app-orchestrator

    Official

    Prepares and validates Agent Landing Zone Orchestrator releases.

    103 GitHub stars~426 tokensUpdated yesterday
    Auto-check passed

Works with

Categories

Questions about Architecture Decision

What does Architecture Decision do?

Conducts and records a verifiable Agent Landing Zone Orchestrator architectural decision. Architecture Decision is an agent skill from Azure/agent-app-orchestrator, published by the product's own GitHub organization. Conducts and records a verifiable Agent Landing Zone Orchestrator architectural decision.

When should I use Architecture Decision?

Architecture Decision fits situations like: A choice alters runtime strategy boundaries; operation with meaningful reversal cost.

How do I install Architecture Decision in Claude Code?

Run `npx skills add Azure/agent-app-orchestrator --skill architecture-decision -a claude-code`. Or copy the skill folder (.github/skills/architecture-decision in Azure/agent-app-orchestrator) into .claude/skills/architecture-decision in your project. Claude Code loads it when a task matches its description.

How do I install Architecture Decision in Codex?

Run `npx skills add Azure/agent-app-orchestrator --skill architecture-decision -a codex`. Or copy the skill folder (.github/skills/architecture-decision in Azure/agent-app-orchestrator) into .agents/skills/architecture-decision in your project. Codex loads it when a task matches its description.

Can I use Architecture Decision 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 architecture-decision -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/architecture-decision, .gemini/skills/architecture-decision, .github/skills/architecture-decision and .opencode/skills/architecture-decision in your project.

What does Architecture Decision need to run?

SKILL.md names no scripts, command-line tools or credentials: Architecture Decision is instructions for the agent only.

Does Architecture Decision 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 Architecture Decision 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 Architecture Decision use?

Architecture Decision 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 Architecture Decision use?

About 319 tokens (SKILL.md is roughly 1.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 343 tokens, read only when the agent opens those files.

What are the alternatives to Architecture Decision?

Skills that share tags, products or a category with Architecture Decision: Cloud Cost Optimization (wshobson/agents, 40k stars), Thesvg (glincker/thesvg, 2.8k stars), Azure Architecture Autopilot (github/awesome-copilot, 40k stars) and Dangling DNS Finder (anirudhbiyani/findmytakeover, 180 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Architecture Decision?

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.