azure-artifacts

Enforce structured H2 heading order and styling for Azure artifact documentation.

Updated Mar 27, 2026
One-click install
npx skills add https://github.com/crytlig/azure-agentic-infraops --skill azure-artifacts-crytlig
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: azure-artifacts
Source: https://github.com/crytlig/azure-agentic-infraops/tree/main/.github/skills/azure-artifacts
Command: npx skills add https://github.com/crytlig/azure-agentic-infraops --skill azure-artifacts-crytlig

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill enforces consistent structure and styling for Azure artifact documentation, reducing drift and improving clarity.

Core Features & Use Cases

  • Template Enforcement: Ensures all documentation follows a strict H2 heading order and style.
  • Styling Consistency: Applies a standardized visual format for callouts, badges, and sections.
  • Use Case: Teams deploying multi-step Azure workloads can generate uniform, high-quality documentation automatically, facilitating reviews and audits.

Quick Start

Generate a new artifact document by following the linked template standards and ensure all required H2 sections are present before publishing.

Frequently Asked Questions about azure-artifacts

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I enforce consistent documentation standards for Azure resources?

To enforce consistent documentation standards for Azure resources, you apply a strict H2 heading order and standardized visual styling to ensure all architecture and operation artifacts remain uniform and clear.

What is the best way to standardize visual styling in Azure artifact documentation?

Standardizing visual styling in Azure artifact documentation involves applying a consistent format for callouts, badges, and sections, which reduces drift and improves clarity across multi-step workload reviews.

Can I automate template enforcement for Azure operation and compliance artifacts?

You can automate template enforcement by requiring adherence to specific H2 heading orders and visual styling rules, which automatically validates Azure operation and compliance artifacts before publication.

Does this documentation standardization approach require specific heading orders for Azure workloads?

Yes, this documentation standardization approach requires adherence to a specific H2 heading order for Azure workloads, ensuring all generated architecture and process documents meet strict structural validation.

Why does my Azure artifact documentation fail style consistency checks?

Azure artifact documentation fails style consistency checks when it does not adhere to the required H2 heading order or lacks the standardized visual format for callouts, badges, and sections.