CtrlK
BlogDocsLog inGet started
Tessl Logo

azure-cloud-architect

Design Azure architectures for startups and enterprises. Use when asked to design Azure infrastructure, create Bicep/ARM templates, optimize Azure costs, set up Azure DevOps pipelines, or migrate to Azure. Covers AKS, App Service, Azure Functions, Cosmos DB, and cost optimization.

70

Quality

86%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

The canonical home for this skill is azure-cloud-architect in alirezarezvani/claude-skills

SKILL.md
Quality
Evals
Security

Quality

Content

85%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A highly actionable, well-sequenced body with concrete code, validation checkpoints, and an error-recovery feedback loop. Its main weakness is progressive disclosure: the referenced references/*.md and scripts/*.py files are signalled but do not exist in the bundle, and a large Bicep block is inlined.

Suggestions

Create the missing bundle files referenced in the body (references/architecture_patterns.md, references/service_selection.md, references/best_practices.md and scripts/architecture_designer.py, cost_optimizer.py, bicep_generator.py) so the signposted progressive-disclosure structure is real and navigable.

Move the large inline Bicep template in Step 3 into references/architecture_patterns.md (or a dedicated bicep reference), keeping only a minimal example inline with a clear pointer.

Trim redundancy between the Quick Start scenarios and the Workflow/Tools sections — for example, fold the Quick Start example results into the existing pattern list rather than restating service stacks twice.

DimensionReasoningScore

Conciseness

Largely efficient with executable code and terse tables, but the ~460-line body has redundancy — the Quick Start scenarios overlap the Workflow/Tools sections and a sizeable Bicep block is inlined — so it sits at 'efficient; minor instances of over-explanation that could be trimmed' rather than the fully lean 5.

4 / 5

Actionability

Fully actionable: concrete `python scripts/*.py` invocations with example JSON/Bicep/YAML outputs, copy-paste CI/CD pipelines, and a specific anti-patterns table map directly to the 'copy-paste ready code... covers common cases' anchor; not lower because nearly every section gives executable specifics.

5 / 5

Workflow Clarity

A clear 6-step sequence with an explicit validation checkpoint in Step 2 and a validate->review->re-validate feedback loop in the Step 6 failure recovery block, matching the 'explicit validation steps; feedback loops for error recovery' anchor; not lower because both checkpoint and retry loop are present.

5 / 5

Progressive Disclosure

Sections are well-organized and references are signalled (Reference Documentation table, inline 'See references/...' calls), but the referenced files — references/architecture_patterns.md, service_selection.md, best_practices.md — and scripts/*.py do not exist in the bundle, so the structure is signalled rather than real and large content (Bicep) is inlined; matches the 'some structure... references present but not clearly... content that should be separate is inline' anchor and is not a 4 because the bundle backing the references is absent.

3 / 5

Total

17

/

20

Passed

Description

87%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, third-person description that pairs concrete capabilities with an explicit 'Use when' trigger clause and Azure-specific service anchors, giving it high completeness and distinctiveness. Minor room to add synonyms and file extensions to push trigger-term coverage to the top level.

DimensionReasoningScore

Specificity

Names the domain plus several concrete actions — 'design Azure architectures', 'create Bicep/ARM templates', 'optimize Azure costs', 'set up Azure DevOps pipelines, or migrate to Azure' — with a named service list, matching the 'several specific actions; minor gaps' anchor; not a 5 because coverage of outputs (e.g. diagrams, cost reports) is implied rather than enumerated.

4 / 5

Completeness

Explicitly answers both 'what' (design Azure architectures for startups and enterprises) and 'when' with a concrete 'Use when asked to design Azure infrastructure, create Bicep/ARM templates...' trigger clause, matching the 5-anchor exactly; not lower because both elements are present and concrete.

5 / 5

Trigger Term Quality

Includes natural phrases users actually say ('design Azure infrastructure', 'Bicep/ARM templates', 'optimize Azure costs', 'migrate to Azure') plus service names (AKS, App Service, Azure Functions, Cosmos DB); falls short of 5 because it omits common synonyms/extensions like 'infra-as-code', 'landing zone', or .bicep/.json file mentions.

4 / 5

Distinctiveness Conflict Risk

Clear Azure-specific niche with service-level triggers (AKS, App Service, Cosmos DB) that distinguish it from generic infra or AWS/GCP skills, matching the 'clear niche with distinct triggers; minimal conflict risk' anchor; not lower because the trigger set is unambiguous.

5 / 5

Total

18

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

referenced_paths_exist

Referenced path issues: 11 missing

Warning

Total

15

/

16

Passed

Repository
alirezarezvani/claude-skills
Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.