New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Official agent skill

Avm Tf Lifecycle

by Azure in Azure/terraform-azurerm-avm-ptn-alz

A skill your agent uses whenever an Azure Verified Module (AVM) is being proposed, approved, published, handed over to a new owner, orphaned, or deprecated — and whenever a contributor is choosing a…

OfficialMITAuto-check passedDevOps & Cloud

Install Avm Tf Lifecycle

skills CLI
$ npx skills add Azure/terraform-azurerm-avm-ptn-alz --skill avm-tf-lifecycle -a claude-code

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

GitHub CLI
$ gh skill install Azure/terraform-azurerm-avm-ptn-alz avm-tf-lifecycle --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/terraform-azurerm-avm-ptn-alz.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.github/skills/avm-tf-lifecycle .claude/skills/avm-tf-lifecycle && 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
avm-tf-lifecycle
GitHub stars
135
Token cost
~1.9k tokens
SKILL.md length
801 words
Files
1
Skills in repo
13
Repo updated
First seen
Licence
MIT

At a glance

A skill your agent uses whenever an Azure Verified Module (AVM) is being proposed, approved, published, handed over to a new owner, orphaned, or deprecated — and whenever a contributor is choosing a…

  • Works in 4 steps: Proposed → Available → Orphaned → …
  • An Azure Verified Module (AVM) is being proposed
  • SKILL.md covers The four stages, The 0.x.y versioning rule, Common pitfalls and Handover checklist for a…
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Avm Tf Lifecycle is an agent skill from Azure/terraform-azurerm-avm-ptn-alz, published by the product's own GitHub organization. Use this skill whenever an Azure Verified Module (AVM) is being proposed, approved, published, handed over to a new owner, orphaned, or deprecated — and whenever a contributor is choosing a version number for a Terraform AVM module release. Covers the four lifecycle stages (Proposed, Available, Orphaned, Deprecated), the 0.x.y pre-GA versioning rule that applies to ALL AVM modules right now, and the support obligations that come with module ownership. Trigger this skill on phrases like "propose an AVM module"…

Its SKILL.md is about 1.9k 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 DevOps & Cloud, covering Infrastructure as code and Changelog and release notes. It works with Microsoft Azure and Terraform. The repository describes itself as: Terraform Azure Verified Pattern Module for Azure Landing Zone Management Groups and Policy. The licence is MIT.

When your agent uses it

  • An Azure Verified Module (AVM) is being proposed
  • Handed over to a new owner
  • Deprecated — and whenever a contributor is choosing a version number for a Terraform AVM module release
  • This skill on phrases like propose an AVM module

Example prompts

  • “propose an AVM module”
  • “what version should I publish”
  • “deprecate this module”
  • “/avm-tf-lifecycle”

Workflow steps

4 steps, taken from the step headings in SKILL.md.

  1. Proposed
  2. Available
  3. Orphaned
  4. Deprecated

What it can do on your machine

Read from SKILL.md and the folder at commit e2a318c. 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

    Links to these hosts (documentation or services it may open):

    • raw.githubusercontent.com
    • github.com
    • aka.ms

    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

Avm Tf Lifecycle loads about 1.9k tokens when it runs. Until then it costs about 171 tokens; SKILL.md has 801 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~171
When it runs · the whole SKILL.md, loaded when a task matches
~1.9k

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/terraform-azurerm-avm-ptn-alz at commit e2a318c, republished under its MIT licence (© Azure). 801 words, ~1,855 tokens.

Download SKILL.mdSave it as .claude/skills/avm-tf-lifecycle/SKILL.md (or your agent's skills folder).
name
avm-tf-lifecycle
description
Use this skill whenever an Azure Verified Module (AVM) is being proposed, approved, published, handed over to a new owner, orphaned, or deprecated — and whenever a contributor is choosing a version number for a Terraform AVM module release. Covers the four lifecycle stages (Proposed, Available, Orphaned, Deprecated), the 0.x.y pre-GA versioning rule that applies to ALL AVM modules right now, and the support obligations that come with module ownership. Trigger this skill on phrases like "propose an AVM module", "what version should I publish", "1.0.0", "GA", "deprecate this module", "module orphaned", "new owner", "handover", "release notes", "AVM lifecycle".

AVM module lifecycle (Terraform)

Every Azure Verified Module moves through four lifecycle stages. This skill teaches what each stage means, what the contributor's obligations are at each stage, and the version-numbering rule that constrains releases at every stage.

Authoritative source: https://raw.githubusercontent.com/Azure/Azure-Verified-Modules/refs/heads/main/docs/content/specs-defs/module-lifecycle.md

The four stages

   Proposed ──✅──► Available ──orphaned──► Orphaned ──end of life──► Deprecated
       │                  ▲                      │
       │                  └──── new owner ───────┘
       ❌
   Rejected
1. Proposed

The starting point for every new module. A contributor (anyone — Microsoft FTE or community) submits a module proposal issue in the central AVM repository using https://aka.ms/AVM/ModuleProposal.

The proposal MUST include:

  • module name (following the naming convention — see avm-tf-classifications)
  • language (Terraform)
  • module class (resource, pattern, or utility — see avm-tf-classifications)
  • module description
  • module owner(s), if known (must be a Microsoft FTE — see avm-tf-process)

Lifecycle approval does not relax the managed authoring rule: a new resource-deploying module repository uses AzAPI for every control-plane and supported direct Azure operation. Each permitted azurerm_* resource or data-source block must independently implement one specific unsupported data-plane/non-ARM operation, document the exact block and AzAPI gap with an upstream AzAPI issue or pull request, and be replaced when support ships. One valid block does not authorize another.

The AVM core team reviews the proposal. If accepted → Available. If rejected → the issue is closed and the lifecycle ends.

2. Available

The module has been developed, tested, published in the main branch and to the Terraform Registry. Consumers can use it in any environment. The module owner is responsible for ongoing maintenance and for responding to issues within the timescales in the Module Support page.

Publishing a new version of an Available module does NOT require a new proposal issue. Just submit a PR in the module's own repository. PR approval logic depends on owner count — see avm-tf-process.

3. Orphaned

A module is orphaned when its owner can no longer maintain it and no replacement has been found.

While orphaned:

  • The AVM core team provides essential maintenance only (critical bug and security fixes).
  • No new feature development until a new owner is found.
  • An issue is opened on the central AVM repo to track ownership re-assignment.
  • The module receives the Status: Module Orphaned 🟡 label.

The owner is responsible for finding a replacement before leaving, and must give the AVM core team warning. If a new owner is identified the module returns to Available.

4. Deprecated

End of life. Either because:

  • An orphaned module's deprecation window has elapsed, OR
  • The owner has chosen to deprecate (e.g. Azure has retired the underlying resource).

Deprecated modules receive the Status: Module Deprecated 🔴 label and are removed from active support.

Show full SKILL.md (391 more words)Show less

The 0.x.y versioning rule

This rule applies to every Available AVM module today. It is not a choice.

The AVM framework is not GA (generally available). The CI framework, test automation and specification validation are not fully implemented across all supported languages yet. Hence modules MUST NOT be published at version 1.0.0 or higher at this time.

All modules MUST be published as a 0.x.y pre-release version (e.g. 0.1.0, 0.1.1, 0.2.0) until the AVM team provides guidance that publishing v1.0.0 is allowed.

Source: https://raw.githubusercontent.com/Azure/Azure-Verified-Modules/refs/heads/main/docs/content/contributing/process.md and SNFR12.

Practical implications:

  • The first release of a new module is 0.1.0, not 1.0.0.
  • Breaking changes bump the minor segment (0.1.0 → 0.2.0), not the major segment.
  • Bug fixes and non-breaking features bump the patch segment (0.1.0 → 0.1.1).
  • Only the latest released version of a module is supported (SNFR12). If a consumer hits a bug on 0.3.0, the first triage step is "upgrade to the latest version".
  • Release notes MUST call out breaking changes clearly — consumers rely on these to decide whether to upgrade.

Do not propose a 1.0.0 release. If a user asks for one, explain that the AVM framework itself is not GA and point at the contributing/process page. The 0.x.y constraint is lifted only when the AVM core team explicitly publishes guidance allowing it.

Common pitfalls

  • Promising long-term support for an old minor version. SNFR12 forbids this — owners aren't expected to maintain multiple major release lines.
  • Skipping the proposal issue and publishing a new module repo. Without an approved proposal the module isn't an AVM module, even if the repo name follows the convention. Pattern modules in particular need the corresponding resource modules to also be proposed/available (PMNFR4).
  • Treating "Orphaned" as a soft state. It blocks all feature work until a new owner takes over — be explicit about this when planning a contribution to an orphaned module.

Handover checklist for a departing owner

  1. Identify a replacement owner (Microsoft FTE — see avm-tf-process).
  2. Hand over context: open issues, in-flight PRs, known consumer pain points, release plans.
  3. Update the avm-module-owners-terraform Core Identity entitlement.
  4. Update the CODEOWNERS file in the module's repo (Terraform) and add the new owner to the -module-owners- GitHub team (Bicep equivalent — not applicable here, but worth knowing).
  5. Notify the AVM core team via the central AVM repo.

If no replacement is found, the module enters Orphaned status — see above.

© 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/avm-tf-lifecycle of Azure/terraform-azurerm-avm-ptn-alz.

Open the folder on GitHubat commit e2a318c

Compare with similar skills

Avm Tf Lifecycle 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.

Avm Tf Lifecycle compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Avm Tf Lifecycle this skillAzure/terraform-azurerm-avm-ptn-alz135—~1.9kAutomated safety check: PassMIT
Terravision Cloud Diagramspatrickchugh/terravision1.6k—~5.6kAutomated safety check: NotesAGPL-3.0-only
Apex GitHub Operationsjonathan-vella/apex217—~1.5kAutomated safety check: PassMIT
Azure CopilotMicrosoftDocs/Agent-Skills777—~1.4kAutomated safety check: PassCC-BY-4.0
TerrasharkLukasNiessen/terrashark714—~843Automated safety check: PassMIT
Azure Diagramscmb211087/azure-diagrams-skill150—~4kAutomated safety check: NotesMIT

Similar skills

  • Terravision Cloud Diagrams

    patrickchugh/terravision

    Draw cloud architecture diagrams for AWS, Azure or GCP with the official provider icon sets, using TerraVision.

    1.6k GitHub stars~5.6k tokensUpdated 2 days ago
    DevOps & CloudAuto-check: notes

  • Apex GitHub Operations

    jonathan-vella/apex

    WORKFLOW SKILL — Full GitHub contribution lifecycle: branches, conventional commits, issues, PRs, Actions, releases.

    217 GitHub stars~1.5k tokensUpdated 2 days ago
    DevOps & CloudAuto-check passed

  • Azure Copilot

    MicrosoftDocs/Agent-Skills

    Official

    Expert knowledge for Azure Copilot development including troubleshooting, decision making, architecture & design patterns, security, configuration, and integrations & coding patterns.

    777 GitHub stars~1.4k tokensUpdated 3 days ago
    DevOps & CloudAuto-check passed

  • Terrashark

    LukasNiessen/terrashark

    Prevent Terraform/OpenTofu hallucinations by diagnosing and fixing failure modes: identity churn, secret exposure, blast-radius mistakes, CI drift, and compliance gate gaps.

    714 GitHub stars~843 tokensUpdated 6 days ago
    DevOps & CloudAuto-check passed

  • Azure Diagrams

    cmb211087/azure-diagrams-skill

    Comprehensive technical diagramming toolkit for solutions architects, presales, and developers.

    150 GitHub stars~4k tokensUpdated 3 mo ago
    DevOps & CloudAuto-check: notes

  • Provider Verification

    mondoohq/mql

    Verify mql provider resource/field changes against real cloud infrastructure.

    411 GitHub stars~3.7k tokensUpdated today
    DevOps & CloudAuto-check passed

More from Azure/terraform-azurerm-avm-ptn-alz

All 13 skills in this repo

  • Avm Tf Azapi

    Azure/terraform-azurerm-avm-ptn-alz

    Official

    A skill your agent uses for AVM Terraform AzAPI resources, provider constraints, ARM schemas, parent IDs, resource types, retries, timeouts, response exports, replacement triggers, and…

    135 GitHub stars~2.9k tokensUpdated 2 days ago
    Auto-check passed

  • Avm Tf Testing

    Azure/terraform-azurerm-avm-ptn-alz

    Official

    A skill your agent uses for AVM Terraform validation, provider-mocked unit tests, real-Azure integration tests, E2E example tests, PowerShell hooks, OIDC, policy checks, and Avm.Authoring CI behavior.

    135 GitHub stars~1.8k tokensUpdated 2 days ago
    Auto-check passed

  • Avm Tf Classifications

    Azure/terraform-azurerm-avm-ptn-alz

    Official

    A skill your agent uses whenever a contributor is deciding what KIND of Azure Verified Module to build in Terraform — resource module, pattern module, or utility module — or is naming a module /…

    135 GitHub stars~2.9k tokensUpdated 2 days ago
    Auto-check passed

  • Avm Tf Codestyle

    Azure/terraform-azurerm-avm-ptn-alz

    Official

    A skill your agent uses for AVM Terraform file layout, HCL style, variables, outputs, validation, lifecycle syntax, provider requirements, and Avm.Authoring formatting.

    135 GitHub stars~1.6k tokensUpdated 2 days ago
    Auto-check passed

  • Avm Tf Conftest

    Azure/terraform-azurerm-avm-ptn-alz

    Official

    A skill your agent uses whenever an AVM Terraform task involves Conftest, OPA, Rego, APRL, AVMSEC, policy findings, policy exceptions, or files under an example exceptions directory.

    135 GitHub stars~1.1k tokensUpdated 2 days ago
    Auto-check passed

  • Avm Tf Documentation

    Azure/terraform-azurerm-avm-ptn-alz

    Official

    A skill your agent uses for AVM Terraform generated README content, header.md, footer.md, examples documentation, terraform-docs inputs, and Avm.Authoring documentation checks.

    135 GitHub stars~1.1k tokensUpdated 2 days ago
    Auto-check passed

Works with

Categories

Questions about Avm Tf Lifecycle

What does Avm Tf Lifecycle do?

A skill your agent uses whenever an Azure Verified Module (AVM) is being proposed, approved, published, handed over to a new owner, orphaned, or deprecated — and whenever a contributor is choosing a…. Avm Tf Lifecycle is an agent skill from Azure/terraform-azurerm-avm-ptn-alz, published by the product's own GitHub organization. Use this skill whenever an Azure Verified Module (AVM) is being proposed, approved, published, handed over to a new owner, orphaned, or deprecated — and whenever a contributor is choosing a version number for a Terraform AVM module release.

When should I use Avm Tf Lifecycle?

Avm Tf Lifecycle fits situations like: an Azure Verified Module (AVM) is being proposed; handed over to a new owner; deprecated — and whenever a contributor is choosing a version number for a Terraform AVM module release; this skill on phrases like propose an AVM module.

How do I install Avm Tf Lifecycle in Claude Code?

Run `npx skills add Azure/terraform-azurerm-avm-ptn-alz --skill avm-tf-lifecycle -a claude-code`. Or copy the skill folder (.github/skills/avm-tf-lifecycle in Azure/terraform-azurerm-avm-ptn-alz) into .claude/skills/avm-tf-lifecycle in your project. Claude Code loads it when a task matches its description.

How do I install Avm Tf Lifecycle in Codex?

Run `npx skills add Azure/terraform-azurerm-avm-ptn-alz --skill avm-tf-lifecycle -a codex`. Or copy the skill folder (.github/skills/avm-tf-lifecycle in Azure/terraform-azurerm-avm-ptn-alz) into .agents/skills/avm-tf-lifecycle in your project. Codex loads it when a task matches its description.

Can I use Avm Tf Lifecycle 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/terraform-azurerm-avm-ptn-alz --skill avm-tf-lifecycle -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/avm-tf-lifecycle, .gemini/skills/avm-tf-lifecycle, .github/skills/avm-tf-lifecycle and .opencode/skills/avm-tf-lifecycle in your project.

What does Avm Tf Lifecycle need to run?

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

Does Avm Tf Lifecycle access the network?

SKILL.md names 3 domains. As links in the text: raw.githubusercontent.com, github.com and aka.ms. This is read from the text; nothing was executed.

Is Avm Tf Lifecycle 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 Avm Tf Lifecycle use?

Avm Tf Lifecycle 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 Avm Tf Lifecycle use?

About 1.9k tokens (SKILL.md is roughly 7.4k 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 Avm Tf Lifecycle?

Skills that share tags, products or a category with Avm Tf Lifecycle: Terravision Cloud Diagrams (patrickchugh/terravision, 1.6k stars), Apex GitHub Operations (jonathan-vella/apex, 217 stars), Azure Copilot (MicrosoftDocs/Agent-Skills, 777 stars) and Terrashark (LukasNiessen/terrashark, 714 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Avm Tf Lifecycle?

Azure (a GitHub organization, an official publisher) maintains it in Azure/terraform-azurerm-avm-ptn-alz, which has 135 GitHub stars. The repository holds 13 skills in this directory. The repository was last updated on October 6, 2026.

Source: Azure/terraform-azurerm-avm-ptn-alz on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.