hybrid-cloud-architect

Expert hybrid cloud architect specializing in complex multi-cloud solutions across AWS/Azure/GCP and private clouds (OpenStack/VMware). Masters hybrid connectivity, workload placement optimization, edge computing, and cross-cloud automation. Handles compliance, cost optimization, disaster recovery, and migration strategies. Use PROACTIVELY for hybrid architecture, multi-cloud strategy, or complex infrastructure integration.

Quality

40%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/hybrid-cloud-architect/SKILL.md

Quality

Content

17%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.

The skill body is a verbose catalog of well-known platforms and services with no executable guidance, only a high-level response sequence lacking validation checkpoints, and no progressive disclosure despite inlined reference-grade material.

Suggestions

Replace the platform/service bullet catalogs with actionable decision guidance: concrete placement heuristics, a connectivity selection matrix, and IaC/Terraform snippets for the common cross-cloud patterns.

Add explicit validation checkpoints to the 'Response Approach' workflow (e.g. validate IaC plan, verify connectivity/latency, DR failover test) so risky migration/DR steps have feedback loops.

Move the service-by-service catalogs into reference files under references/ and keep SKILL.md as a concise overview pointing to them, enabling one-level-deep progressive disclosure.

Dimension	Reasoning	Score
Conciseness	The body is ~155 lines of bullet enumerations cataloging services and platforms Claude already knows (e.g. 'AWS, Azure, GCP', 'Nova, Neutron, Cinder'), plus a redundant 'Purpose'/'Capacidades' restatement of the description, which is noticeably verbose padding rather than guidance Claude does not already know.	2 / 5
Actionability	There is no executable code, commands, decision logic, or concrete artifacts anywhere — only descriptions like 'Clarify goals, constraints, and required inputs' and 'Apply relevant best practices', which describe rather than instruct.	1 / 5
Workflow Clarity	A rough 'Response Approach' sequence is listed (Analyze → Design → Plan → Implement → Automate → Monitor → DR → Optimize → Document) but the steps are high-level and lack any validation checkpoints or feedback loops for risky operations like migration or DR design.	2 / 5
Progressive Disclosure	No bundle files exist (references/scripts/assets absent), yet ~120 lines of platform/service catalogs that clearly belong in separate reference files are inlined monolithically with minimal structural signaling beyond section headers.	2 / 5
	Total	7 / 20 Passed

Description

62%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.

The description answers both what and when with third-person voice and a clear hybrid-cloud niche, but its actions stay at the abstract-category level and the trigger phrasing lacks the concrete, natural terms users would actually say.

Suggestions

Replace abstract categories ('handles compliance, cost optimization') with 2-3 concrete actions a user would recognize (e.g. 'designs cross-cloud DR with defined RTO/RPO', 'models multi-cloud TCO and right-sizing').

Broaden the 'Use when...' clause with natural trigger phrasings users actually say, such as 'hybrid connectivity (Direct Connect/ExpressRoute)', 'workload placement across clouds', or 'multi-cloud cost optimization'.

Tighten the opening so the distinct hybrid/multi-cloud niche leads the sentence, reducing overlap with generic cloud-architect descriptions.

Dimension	Reasoning	Score
Specificity	Quotes 'Masters hybrid connectivity, workload placement optimization, edge computing, and cross-cloud automation' and 'Handles compliance, cost optimization, disaster recovery, and migration strategies' — domain plus several actions, but they remain abstract categories rather than truly concrete operations, so it sits at the 1-2 concrete-actions level.	3 / 5
Completeness	A clear 'what' is present ('Expert hybrid cloud architect specializing in complex multi-cloud solutions...') and an explicit 'when' ('Use PROACTIVELY for hybrid architecture, multi-cloud strategy, or complex infrastructure integration'), but the 'when' is somewhat generic rather than tied to concrete trigger phrases.	4 / 5
Trigger Term Quality	Trigger phrase 'hybrid architecture, multi-cloud strategy, or complex infrastructure integration' names the domain but lacks the concrete natural phrasings or synonyms (e.g. 'AWS/Azure migration', 'workload placement', 'DR across clouds') a user would actually say, matching the some-relevant-keywords-but-missing-variations anchor.	3 / 5
Distinctiveness Conflict Risk	The hybrid/multi-cloud framing and 'Use PROACTIVELY' trigger create a fairly clear niche distinct from single-cloud skills, with only minor overlap risk against general cloud or migration skills.	4 / 5
	Total	14 / 20 Passed

Validation

93%

Warnings & errors only

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

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning

	Total	15 / 16 Passed

Repository: rmyndharis/antigravity-skills
Path: skills/hybrid-cloud-architect/SKILL.md
Commit: 3eff4af

Reviewed: 1 day ago

Table of Contents

Discovery Implementation Validation

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.