Per-section density is lean (severity/requirement headers, bullet rules, tight HCL examples), but the intro sentence, the Summary Statistics counts, and the closing footer restate information already conveyed by the requirement list. Not 1 because it avoids explaining concepts Claude already knows and is not padded with generic context; not 3 because not every token earns its place and the ~600-line monolith could be tightened.

Provides fully executable HCL examples (required_providers blocks, for_each maps, dynamic blocks, outputs, feature-toggle variables), specific tool lists ('terraform validate/fmt/test', 'terafmt', 'checkov', 'tflint'), and a copy-paste-ready compliance checklist. Not 2 because the examples are real, complete code rather than pseudocode with missing details.

The Compliance Checklist and Testing tool list provide some structure, but there is no ordered module-development workflow with explicit validate→fix→retry checkpoints; per the feedback_loops note, missing feedback loops for batch/destructive Terraform operations caps this at 2. Not 1 because a verification checklist and named validation tools do exist; not 3 because no sequenced workflow with feedback loops is present.

The body is well-organized (Table of Contents, clear section headers) but is a ~600-line monolith with all per-category requirements inline and no bundle files to split content one level deep. Not 1 because it is well-sectioned with a TOC rather than a disorganized wall and references are not deeply nested; not 3 because content that belongs in separate reference files is entirely inline, and the under-50-lines exception does not apply.

Names the domain and actions ('developing certified Azure Terraform modules', 'creating or reviewing Azure modules') but the phrase 'requirements and best practices' is abstract rather than a list of multiple concrete actions. Not 1 because it is far from vague ('Helps with documents'); not 3 because it does not enumerate several specific concrete actions like the score-3 anchor.

Explicitly states what ('AVM requirements and best practices for developing certified Azure Terraform modules') and when ('Use when creating or reviewing Azure modules that need AVM certification'), matching the score-3 anchor pattern with an explicit 'Use when' trigger. Not 2 because the 'when' is explicit, not merely implied.

Covers the niche's natural vocabulary with 'Azure Verified Modules (AVM)', 'Azure Terraform modules', and 'AVM certification' — terms a user would actually say when needing this skill. Not 2 because it provides multiple natural phrasings plus the acronym rather than a single bare keyword.

The 'AVM certification' / 'Azure Verified Modules' niche is tightly scoped with distinct triggers, making accidental triggering for unrelated skills unlikely. Not 2 because it is far more specific than a generic 'Works with document files' phrasing.