Agent skill

Apex Azure Artifacts

by jonathan-vella in jonathan-vella/apex

UTILITY SKILL — Artifact template structures, H2 compliance rules, and documentation styling for agent outputs (Steps 1-7).

MITAuto-check passedDevOps & Cloud

Install Apex Azure Artifacts

skills CLI
$ npx skills add jonathan-vella/apex --skill apex-azure-artifacts -a claude-code

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

GitHub CLI
$ gh skill install jonathan-vella/apex apex-azure-artifacts --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/jonathan-vella/apex.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.github/skills/apex-azure-artifacts .claude/skills/apex-azure-artifacts && 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
apex-azure-artifacts
GitHub stars
217
Token cost
~2.3k tokens
SKILL.md length
792 words
Files
36 (incl. references)
Skills in repo
39
Repo updated
First seen
Licence
MIT

At a glance

UTILITY SKILL — Artifact template structures, H2 compliance rules, and documentation styling for agent outputs (Steps 1-7).

  • Works in 3 steps: Reflect verified graph/session status in… → Add artifact files to ## 📄 Generated… → Update Last Updated and derive progress…
  • : generating any agent artifact
  • SKILL.md covers Rules, Mandatory: Project README, Steps and Post-write validation, plus 4 more sections
  • Calls npm, node and terraform

What it does

Apex Azure Artifacts is an agent skill from jonathan-vella/apex. UTILITY SKILL — Artifact template structures, H2 compliance rules, and documentation styling for agent outputs (Steps 1-7). WHEN: "generate artifact", "check H2 structure", "artifact template", "step 7 as-built". USE FOR: generating any agent artifact, checking H2 structure compliance. DO NOT USE FOR: Azure resource configuration (use apex-azure-defaults), Bicep/Terraform patterns (use apex-azure-bicep-patterns or apex-terraform-patterns).

Its SKILL.md is about 2.3k tokens, which your agent loads only when the skill is triggered. The skill folder holds 37 other files, including reference files (for example `references/01-requirements-template.md`, `references/02-architecture-template.md` and `references/04-plan-template.md`). Compatibility notes: Works with Claude Code, GitHub Copilot, VS Code, and any Agent Skills compatible tool.

It sits in DevOps & Cloud, covering Infrastructure as code. It works with Microsoft Azure, Bicep and Terraform. The repository describes itself as: APEX turns Azure platform engineering requirements into verified, deploy-ready IaC — powered by GitHub Copilot agents, real-time pricing, and built-in compliance. The licence is MIT.

When your agent uses it

  • : generating any agent artifact
  • Checking H2 structure compliance
  • : Azure resource configuration (use apex-azure-defaults)
  • Bicep/Terraform patterns (use apex-azure-bicep-patterns

Example prompts

  • “generate artifact”
  • “check H2 structure”
  • “artifact template”
  • “/apex-azure-artifacts”

Requirements

  • Python 3
  • Compatibility (from SKILL.md): Works with Claude Code, GitHub Copilot, VS Code, and any Agent Skills compatible tool.

Workflow steps

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

  1. Reflect verified graph/session status in ## ✅ Workflow Progress; a write alone is not completion
  2. Add artifact files to ## 📄 Generated Artifacts
  3. Update Last Updated and derive progress from current required/optional graph nodes,

What it can do on your machine

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

    Shell commands in SKILL.md call:

    • npm
    • node
    • terraform
    • python

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use npm, which can reach the network depending on how they are called.

    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.

  • Compatibility

    Works with Claude Code, GitHub Copilot, VS Code, and any Agent Skills compatible tool.

    From compatibility in the SKILL.md frontmatter.

Context cost

Apex Azure Artifacts loads about 2.3k tokens when it runs, and up to ~9.9k if it reads all its reference files. Until then it costs about 117 tokens; SKILL.md has 792 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~117
When it runs · the whole SKILL.md, loaded when a task matches
~2.3k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~9.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 jonathan-vella/apex at commit b8e5908, republished under its MIT licence (© jonathan-vella). 792 words, ~2,336 tokens.

Download SKILL.mdSave it as .claude/skills/apex-azure-artifacts/SKILL.md (or your agent's skills folder). This skill also uses 35 other files; get the full folder from GitHub.
name
apex-azure-artifacts
description
**UTILITY SKILL** — Artifact template structures, H2 compliance rules, and documentation styling for agent outputs (Steps 1-7). WHEN: "generate artifact", "check H2 structure", "artifact template", "step 7 as-built". USE FOR: generating any agent artifact, checking H2 structure compliance. DO NOT USE FOR: Azure resource configuration (use apex-azure-defaults), Bicep/Terraform patterns (use apex-azure-bicep-patterns or apex-terraform-patterns).
compatibility
Works with Claude Code, GitHub Copilot, VS Code, and any Agent Skills compatible tool.
user-invocable
false
disable-model-invocation
false
license
MIT
metadata.author
jonathan-vella
metadata.version
2.0
metadata.category
workflow-automation

Azure Artifacts Skill

Owns artifact structures and styling, not workflow decisions. Required H2s come from the heading registry; full templates live in templates/ and references/ provide navigation summaries. Read the full template for current writes. The workflow graph, role contract, current reviews and human approval own routing and completion; templates never advance a step or authorize an operation.

Rules

Mandatory Compliance
RuleRequirement
Template skeletonRead the full step template from templates/; summaries are navigation
Exact textUse H2 text from templates verbatim
Exact orderRequired H2s appear in the order listed
Anchor ruleExtra sections allowed ONLY after last required H2
No omissionsEvery H2 listed must appear in output
Attribution> Generated by {agent} agent | {YYYY-MM-DD}
DO / DON'T
  • DO: Read the step-specific template before generating
  • DO: Copy H2 text character-for-character (including emoji)
  • DO: Save all output to agent-output/{project}/
  • DON'T: Reorder H2 headings from the listed sequence
  • DON'T: Use placeholder text like "TBD" or "Insert here"
  • DON'T: Add custom H2 sections BEFORE the last required H2

Mandatory: Project README

Every project in agent-output/{project}/ MUST have a README.md.

After saving step artifact(s), update the README:

  1. Reflect verified graph/session status in ## ✅ Workflow Progress; a write alone is not completion
  2. Add artifact files to ## 📄 Generated Artifacts
  3. Update Last Updated and derive progress from current required/optional graph nodes, including Governance. Partial output, pending reviews and approval remain incomplete.

Steps

Artifact generation flow (per Step N):

  1. Read template — use the matching reference to locate the full templates/*.template.md
  2. Copy H2 skeleton — replicate every required H2 in the listed order, character-for-character
  3. Fill content — replace {placeholder} tokens; never use "TBD" or "Insert here"
  4. Add attribution — > Generated by {agent} agent | {YYYY-MM-DD}
  5. Save to agent-output/{project}/ with the prescribed filename
  6. Update README — list validated artifacts and actual status; never mark complete before required checks, reviews and approval
  7. Delegate validation — do not invoke npm run lint:artifact-templates, npm run lint:h2-sync, or markdownlint-cli2 directly against agent-output/**. The lefthook artifact-validation pre-commit hook (which wraps these scripts) and the 10-Challenger review own the artifact contract. See agent-authoring.instructions.md.

For revisions (challenger findings, user decisions, approval-gate fixes), follow references/revision-workflow.md. Use available targeted editing tools, preserve user work, and validate before dependent follow-up edits.

Post-write validation

Run a one-line shape check immediately after writing any non-markdown artifact, before moving to the next step. Catches malformed output at source instead of at deploy time. Markdown artifacts are owned by the lefthook artifact-validation hook — do not duplicate that check here.

Artifact typeValidation command (run after write)
*.jsonpython -m json.tool <file> >/dev/null
*.bicepbicep build --stdout <file> >/dev/null
*.tfterraform fmt -check <file> + terraform validate (in module dir)
challenge-findings-*.json (sidecar JSON)node tools/scripts/validate-challenger-findings.mjs <file>
challenge-findings-*-decisions.json (per-finding sidecar)node tools/scripts/validate-challenge-findings-decisions.mjs <file>
*.mddelegated to lefthook artifact-validation — do not run inline

Fail closed: if the validator exits non-zero, fix the artifact and re-validate before continuing. Do not record the artifact in the project README or hand off to the next step until it passes.

For incremental IaC, apply the readiness-aware build checkpoints in codegen-shared-workflow.md. An incomplete scaffold has deferred checks, not successful validation; all deferred checks must pass before completion or handoff. Use bounded validated batches under the shared workflow; no routine per-file approval is required.

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

Placeholder Syntax

All templates use single-brace {placeholder-name} syntax:

  • Lowercase, hyphen-separated: {project-name}, {monthly-cost}
  • No Mustache/Handlebars {{double-braces}}

Automated Validation

These npm scripts are invoked by the lefthook artifact-validation pre-commit hook and by CI — not by agents directly (see agent-authoring.instructions.md).

bash
npm run lint:artifact-templates   # H2 order and required headings (pre-commit + CI only)
npm run lint:h2-sync              # Template ↔ artifact sync (pre-commit + CI only)
npm run validate:all              # All validators together (humans / CI only)
Fast H2-order sanity check (agent-safe)

When an agent needs a quick "did I get the H2 structure right?" check before invoking the challenger, use the dedicated helper instead of improvising node -e '…' one-liners (which trip shell quoting and waste context on retries):

bash
npm run check:h2-order -- <project>                       # defaults to 01-requirements.md
npm run check:h2-order -- <project> 04-implementation-plan.md
node tools/scripts/check-h2-order.mjs agent-output/<project>/02-architecture-assessment.md

Exit 0 = match (prints OK: …). Exit 1 = mismatch (prints structured JSON with expected/got/missingAt). Exit 2 = bad arguments or unknown artifact filename. The helper reads the canonical heading registry from tools/scripts/_lib/artifact-headings.mjs so it never drifts from the template source of truth.

Quality Checklist

Critical (always check):

  • H2 headings match template exactly (text + order)
  • Attribution header present with agent name and date
  • No placeholder text (e.g. "TBD", "Insert here", task markers)
  • File saved to agent-output/{project}/ with correct name

For the full structural / styling checklist (TOC, cross-nav table, traffic lights, Mermaid, collapsible blocks) read references/styling-standards.md.

Reference Index

When generating a Step N artifact, read the corresponding template:

ReferenceWhen to Load
references/01-requirements-template.mdGenerating Step 1 requirements
references/02-architecture-template.mdGenerating Step 2 assessment or Step 3 cost estimate
references/04-plan-template.mdGenerating Step 4 plan, governance, or preflight
references/05-code-template.mdGenerating Step 5 implementation reference
references/06-deploy-template.mdGenerating Step 6 deployment summary
references/07-docs-template.mdGenerating Step 7 workload documentation
references/styling-standards.mdApplying callouts, badges, emoji, navigation
references/cost-estimate-sections.mdCost estimate H2 structure and formatting rules
references/revision-workflow.mdDetailed targeted-edit revision procedure (Step 7+)
references/sku-manifest-details.mdSKU manifest coverage, projection, TTL and sync tooling

© jonathan-vella, 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 35 other files (references) in .github/skills/apex-azure-artifacts of jonathan-vella/apex.

  • SKILL.md
  • references/01-requirements-template.md
  • references/02-architecture-template.md
  • references/04-plan-template.md
  • references/05-code-template.md
  • references/06-deploy-template.md
  • references/07-docs-template.md
  • references/cost-estimate-sections.md
  • references/revision-workflow.md
  • references/sku-manifest-details.md
  • references/styling-standards.md
  • templates/00-session-state.template.json
  • templates/01-requirements.template.md
  • templates/02-architecture-assessment.template.md
  • templates/03-des-cost-estimate.template.md
  • templates/04-environment-manifest.template.json
  • templates/04-governance-constraints.template.md
  • templates/04-iac-contract.template.json
  • templates/04-implementation-plan.template.md
  • … and 17 more

Open the folder on GitHubat commit b8e5908

Compare with similar skills

Apex Azure Artifacts 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.

Apex Azure Artifacts compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Apex Azure Artifacts this skilljonathan-vella/apex217—~2.3kAutomated safety check: PassMIT
Iac Securityhardw00t/ai-security-arsenal105—~2.4kAutomated safety check: PassNone
Azure Deploymicrosoft/GitHub-Copilot-for-Azure2551 repos~1.6kAutomated safety check: PassMIT
Azure Preparemicrosoft/GitHub-Copilot-for-Azure2551 repos~3.2kAutomated safety check: PassMIT
Azure Validatemicrosoft/GitHub-Copilot-for-Azure2551 repos~880Automated safety check: PassMIT
Azure To AWSaws/agent-toolkit-for-aws2.8k—~5.5kAutomated safety check: PassApache-2.0

Similar skills

  • Iac Security

    hardw00t/ai-security-arsenal

    Infrastructure-as-Code security scanning router for Terraform, CloudFormation, Kubernetes manifests, Helm, ARM/Bicep.

    105 GitHub stars~2.4k tokensUpdated 5 mo ago
    DevOps & CloudAuto-check passed
  • Azure Deploy

    microsoft/GitHub-Copilot-for-Azure

    Official

    Execute Azure deployments for ALREADY-PREPARED applications that have existing .azure/deployment-plan.md and infrastructure files.

    255 GitHub starsUsed in 1 repo~1.6k tokens
    DevOps & CloudAuto-check passed
  • Azure Prepare

    microsoft/GitHub-Copilot-for-Azure

    Official

    Prepare azd-based Azure projects for deployment: generates azure.yaml, infrastructure (Bicep/Terraform), and Dockerfiles for the Azure Developer CLI (azd) workflow.

    255 GitHub starsUsed in 1 repo~3.2k tokens
    DevOps & CloudAuto-check passed
  • Azure Validate

    microsoft/GitHub-Copilot-for-Azure

    Official

    Pre-deployment validation for Azure readiness. An agent skill from microsoft/GitHub-Copilot-for-Azure.

    255 GitHub starsUsed in 1 repo~880 tokens
    DevOps & CloudAuto-check passed
  • Azure To AWS

    aws/agent-toolkit-for-aws

    Official

    Migrate workloads from Microsoft Azure to AWS. An agent skill from aws/agent-toolkit-for-aws.

    2.8k GitHub stars~5.5k tokensUpdated yesterday
    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.

    776 GitHub stars~1.4k tokensUpdated 5 days ago
    DevOps & CloudAuto-check passed

More from jonathan-vella/apex

All 39 skills in this repo
  • Apex Azure Diagnostics

    jonathan-vella/apex

    WORKFLOW SKILL — Debug Azure production issues: Container Apps, Functions, App Service, AKS, VMs and messaging, with KQL log analysis.

    217 GitHub stars~2.1k tokensUpdated yesterday
    Auto-check passed
  • ANALYSIS SKILL — Azure Policy discovery: effective assignments (incl.

    217 GitHub stars~2.1k tokensUpdated yesterday
    Auto-check passed
  • Apex Context Management

    jonathan-vella/apex

    UTILITY SKILL — Two-mode context-window management. An agent skill from jonathan-vella/apex.

    217 GitHub stars~1.8k tokensUpdated yesterday
    Auto-check passed
  • Apex Python Diagrams

    jonathan-vella/apex

    UTILITY SKILL — Python diagram generation for Azure architectures, WAF/cost/compliance charts, ERDs, swimlanes, timelines, and wireframes.

    217 GitHub stars~2k tokensUpdated yesterday
    Auto-check passed
  • Apex Terraform Search Import

    jonathan-vella/apex

    WORKFLOW SKILL — Manual-only discovery and import of existing Azure resources into Terraform management.

    217 GitHub stars~1.4k tokensUpdated yesterday
    Auto-check passed
  • Apex Vendor Prompting

    jonathan-vella/apex

    ANALYSIS SKILL — Manual-only audit of Anthropic Claude Opus 5.5 / Sonnet 5.5 and OpenAI GPT-6 / GPT-5.6 prompting guidance and APEX conventions.

    217 GitHub stars~2.7k tokensUpdated yesterday
    Auto-check passed

Categories

Questions about Apex Azure Artifacts

What does Apex Azure Artifacts do?

UTILITY SKILL — Artifact template structures, H2 compliance rules, and documentation styling for agent outputs (Steps 1-7). Apex Azure Artifacts is an agent skill from jonathan-vella/apex. UTILITY SKILL — Artifact template structures, H2 compliance rules, and documentation styling for agent outputs (Steps 1-7).

When should I use Apex Azure Artifacts?

Apex Azure Artifacts fits situations like: : generating any agent artifact; checking H2 structure compliance; : Azure resource configuration (use apex-azure-defaults); bicep/Terraform patterns (use apex-azure-bicep-patterns.

How do I install Apex Azure Artifacts in Claude Code?

Run `npx skills add jonathan-vella/apex --skill apex-azure-artifacts -a claude-code`. Or copy the skill folder (.github/skills/apex-azure-artifacts in jonathan-vella/apex) into .claude/skills/apex-azure-artifacts in your project. Claude Code loads it when a task matches its description.

How do I install Apex Azure Artifacts in Codex?

Run `npx skills add jonathan-vella/apex --skill apex-azure-artifacts -a codex`. Or copy the skill folder (.github/skills/apex-azure-artifacts in jonathan-vella/apex) into .agents/skills/apex-azure-artifacts in your project. Codex loads it when a task matches its description.

Can I use Apex Azure Artifacts 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 jonathan-vella/apex --skill apex-azure-artifacts -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/apex-azure-artifacts, .gemini/skills/apex-azure-artifacts, .github/skills/apex-azure-artifacts and .opencode/skills/apex-azure-artifacts in your project.

What does Apex Azure Artifacts need to run?

Going by SKILL.md and its folder, Apex Azure Artifacts needs the command-line tools its instructions call (npm, node, terraform and python). Our summary lists: Python 3. Compatibility (from SKILL.md): Works with Claude Code, GitHub Copilot, VS Code, and any Agent Skills compatible tool..

Does Apex Azure Artifacts access the network?

SKILL.md contains no URLs. Its commands use npm, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Apex Azure Artifacts 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 Apex Azure Artifacts use?

Apex Azure Artifacts is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Apex Azure Artifacts use?

About 2.3k tokens (SKILL.md is roughly 9.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 7.6k tokens, read only when the agent opens those files.

What are the alternatives to Apex Azure Artifacts?

Skills that share tags, products or a category with Apex Azure Artifacts: Iac Security (hardw00t/ai-security-arsenal, 105 stars), Azure Deploy (microsoft/GitHub-Copilot-for-Azure, 255 stars), Azure Prepare (microsoft/GitHub-Copilot-for-Azure, 255 stars) and Azure Validate (microsoft/GitHub-Copilot-for-Azure, 255 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Apex Azure Artifacts?

jonathan-vella (a GitHub user) maintains it in jonathan-vella/apex, which has 217 GitHub stars. The repository holds 39 skills in this directory. The repository was last updated on October 10, 2026.

Source: jonathan-vella/apex on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.