aiskillstore/marketplace / skills/89jobrien/cloud-infrastructure
cloud-infrastructure
VerifiedCloud infrastructure design and deployment patterns for AWS, Azure, and GCP. Use when designing cloud architectures, implementing IaC with Terraform, optimizing costs, or setting up multi-region deployments.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 5.0 KB |
| skill-report.json | config | 12.0 KB |
skill-report.json
View on GitHub{
"schema_version": "2.0",
"meta": {
"generated_at": "2026-07-05T11:17:11.923Z",
"slug": "89jobrien-cloud-infrastructure",
"source_url": "https://github.com/89jobrien/steve/tree/main/steve/skills/cloud-infrastructure",
"source_ref": "main",
"model": "codex",
"analysis_version": "3.0.0",
"source_type": "community",
"content_hash": "c5890bbf4069b01833d8d229cd353ae71a35793bc026951df4ac3bda1edee25b",
"tree_hash": "56dfcea1b0d9db4f8e75aa5097cbdd227c80551a1d5ff27690a05566b6f47ac3",
"provenance": {
"model_effective": "codex",
"fallback_chain": [
{
"agent": "codex",
"outcome": "success"
}
],
"analysis_version": "3.0.0"
}
},
"skill": {
"name": "cloud-infrastructure",
"description": "Cloud infrastructure design and deployment guidance for AWS, Azure, and GCP, including Terraform patterns, cost controls, and resilient deployments.",
"summary": "Plan multi-cloud infrastructure, Terraform patterns, high availability, security controls, and cost optimization across AWS, Azure, and GCP.",
"icon": "📦",
"version": "1.0.2",
"author": "Joseph OBrien",
"license": "MIT",
"category": "devops",
"tags": [
"cloud-architecture",
"terraform",
"multi-cloud",
"cost-optimization",
"high-availability"
],
"supported_tools": [
"claude",
"codex",
"claude-code"
],
"risk_factors": [
"external_commands"
]
},
"security_audit": {
"risk_level": "safe",
"is_blocked": false,
"safe_to_publish": true,
"analysis_status": "ok",
"summary": "All five static findings are false positives from markdown formatting or cloud infrastructure guidance. No prompt injection, command execution intent, or reconnaissance intent was found in SKILL.md.",
"remediation": [],
"risk_factor_evidence": [
{
"factor": "external_commands",
"evidence": [
{
"file": "SKILL.md",
"line_start": 63,
"line_end": 77
},
{
"file": "SKILL.md",
"line_start": 77,
"line_end": 180
},
{
"file": "SKILL.md",
"line_start": 180,
"line_end": 181
}
]
}
],
"static_findings": [
{
"id": "external_commands:SKILL.md:63:ruby-shell-backtick-execution",
"category": "external_commands",
"severity": "medium",
"pattern": "Ruby/shell backtick execution",
"file": "SKILL.md",
"line_start": 63,
"line_end": 77,
"snippet": "```"
},
{
"id": "external_commands:SKILL.md:77:ruby-shell-backtick-execution",
"category": "external_commands",
"severity": "medium",
"pattern": "Ruby/shell backtick execution",
"file": "SKILL.md",
"line_start": 77,
"line_end": 180,
"snippet": "```"
},
{
"id": "external_commands:SKILL.md:180:ruby-shell-backtick-execution",
"category": "external_commands",
"severity": "medium",
"pattern": "Ruby/shell backtick execution",
"file": "SKILL.md",
"line_start": 180,
"line_end": 181,
"snippet": "- **`references/terraform_patterns.md`** - IaC patterns and examples"
},
{
"id": "blocker:SKILL.md:153:system-reconnaissance",
"category": "blocker",
"severity": "low",
"pattern": "System reconnaissance",
"file": "SKILL.md",
"line_start": 153,
"line_end": 155,
"snippet": "- VPN/Direct Connect for hybrid"
},
{
"id": "blocker:SKILL.md:141:network-reconnaissance",
"category": "blocker",
"severity": "low",
"pattern": "Network reconnaissance",
"file": "SKILL.md",
"line_start": 141,
"line_end": 143,
"snippet": "### Identity & Access"
}
],
"finding_verdicts": [
{
"id": "external_commands:SKILL.md:63:ruby-shell-backtick-execution",
"verdict": "false_positive",
"confidence": 0.97,
"reason": "Lines 63-77 are a fenced project tree for Terraform folders, not executable Ruby or shell syntax. The backticks only mark markdown formatting."
},
{
"id": "external_commands:SKILL.md:77:ruby-shell-backtick-execution",
"verdict": "false_positive",
"confidence": 0.97,
"reason": "Line 77 closes the same markdown code fence and the following text is prose guidance. No command invocation or user-controlled execution path is present."
},
{
"id": "external_commands:SKILL.md:180:ruby-shell-backtick-execution",
"verdict": "false_positive",
"confidence": 0.96,
"reason": "Line 180 references another markdown file using inline code ticks. It is documentation text, not a shell command or runtime execution."
},
{
"id": "blocker:SKILL.md:153:system-reconnaissance",
"verdict": "false_positive",
"confidence": 0.94,
"reason": "Line 153 recommends VPN or Direct Connect for hybrid cloud networking. This is architecture guidance, not host enumeration or system reconnaissance."
},
{
"id": "blocker:SKILL.md:141:network-reconnaissance",
"verdict": "false_positive",
"confidence": 0.94,
"reason": "Lines 141-143 introduce identity and access security practices. The text does not request network scanning, discovery, or enumeration."
}
],
"semantic_findings": [],
"critical_findings": [],
"high_findings": [],
"medium_findings": [],
"low_findings": [],
"dangerous_patterns": [],
"files_scanned": 1,
"total_lines": 189,
"audit_model": "codex",
"audited_at": "2026-07-05T11:17:11.923Z",
"agent_auto_install_policy": "allowed",
"manual_install_policy": "allowed"
},
"content": {
"user_title": "Design Cloud Infrastructure",
"value_statement": "Cloud teams need consistent patterns for secure, resilient, and cost-aware infrastructure. This skill guides architecture choices, Terraform organization, availability planning, and operational controls.",
"seo_keywords": [
"Claude",
"Codex",
"Claude Code",
"cloud infrastructure",
"Terraform patterns",
"AWS architecture",
"Azure architecture",
"GCP architecture",
"cost optimization",
"multi-region deployment"
],
"actual_capabilities": [
"Maps compute, storage, and database patterns across AWS, Azure, and GCP.",
"Explains Terraform project structure, remote state, module design, and versioning practices.",
"Provides cost optimization tactics for compute, storage, and network usage.",
"Outlines multi-AZ and multi-region availability patterns for production systems.",
"Summarizes cloud security controls for identity, networks, encryption, and backups."
],
"limitations": [
"Does not include executable Terraform modules or provider-specific deployment scripts.",
"Does not verify live cloud account configuration or resource inventory.",
"Does not replace cloud security review, compliance review, or cost forecasting tools.",
"Referenced supplemental files are listed but not included in this package."
],
"use_cases": [
{
"title": "Plan a New Platform",
"description": "Design a first production cloud architecture with clear compute, storage, database, and network choices.",
"target_user": "Startup engineering lead"
},
{
"title": "Improve Existing Infrastructure",
"description": "Review Terraform structure, high availability choices, and cloud cost drivers before a scaling milestone.",
"target_user": "DevOps engineer"
},
{
"title": "Compare Multi-Cloud Options",
"description": "Translate architecture needs across AWS, Azure, and GCP services during vendor selection.",
"target_user": "Cloud architect"
}
],
"prompt_templates": [
{
"title": "Plan a Basic Cloud Architecture",
"prompt": "Design a cloud architecture for a small web application with a database, static assets, and basic monitoring.",
"scenario": "Beginner planning for a first production deployment"
},
{
"title": "Compare Cloud Services",
"prompt": "Compare AWS, Azure, and GCP service choices for containers, relational databases, object storage, and caching.",
"scenario": "Selecting a cloud provider or translating an architecture"
},
{
"title": "Optimize Terraform and Costs",
"prompt": "Review my Terraform organization and suggest cost optimization steps for compute, storage, and network usage.",
"scenario": "Improving infrastructure management and spending control"
},
{
"title": "Design Multi-Region Resilience",
"prompt": "Create a multi-region architecture plan with failover, data replication, security controls, observability, and recovery procedures.",
"scenario": "Advanced design for high availability and disaster recovery"
}
],
"output_examples": [
{
"input": "Need a production architecture for a web application on AWS.",
"output": [
"Use managed containers behind a load balancer across two availability zones.",
"Store relational data in a managed database with automated backups.",
"Place static assets in object storage behind a CDN.",
"Add monitoring for latency, errors, saturation, and monthly cost."
]
},
{
"input": "Need to reduce cloud costs without hurting reliability.",
"output": [
"Right-size compute based on measured utilization.",
"Use reserved capacity for steady workloads and spot capacity for interruptible jobs.",
"Move cold data to cheaper storage tiers with lifecycle policies.",
"Track cost by service and team through tags or labels."
]
}
],
"best_practices": [
"Start with workload requirements, then choose cloud services that match availability, latency, and operations needs.",
"Keep Terraform modules small, versioned, documented, and separated by environment state.",
"Review identity, network boundaries, encryption, backup tests, and monitoring before production launch."
],
"anti_patterns": [
"Do not copy a reference architecture without checking workload requirements and team operations capacity.",
"Do not store Terraform state files, secrets, or long-term credentials in source control.",
"Do not design multi-region systems before defining recovery objectives and data consistency needs."
],
"faq": [
{
"question": "Does this skill generate Terraform code?",
"answer": "It gives Terraform structure and design guidance. It does not include ready-made Terraform modules."
},
{
"question": "Which cloud providers are covered?",
"answer": "It covers AWS, Azure, and GCP service patterns for compute, storage, databases, networking, and resilience."
},
{
"question": "Can this skill inspect my cloud account?",
"answer": "No. It provides planning guidance and cannot access live accounts, billing data, or deployed resources."
},
{
"question": "Is this useful for cost optimization?",
"answer": "Yes. It lists compute, storage, and network savings tactics that support a cost review."
},
{
"question": "Can I use it with Claude Code or Codex?",
"answer": "Yes. The report declares support for Claude, Codex, and Claude Code."
},
{
"question": "Does it replace a security architecture review?",
"answer": "No. It highlights common cloud controls, but specialist review is still needed for regulated systems."
}
]
},
"file_structure": [
{
"name": "SKILL.md",
"type": "file",
"path": "SKILL.md",
"lines": 189
}
]
}
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deployment | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy. | Stars: 119k | Updated | Claude CodeCodex | Verified | Install |
| childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release. | Stars: 118k | Updated | Claude CodeCodex | Verified | Install |