Assesses cloud and infrastructure costs — current spend, projected spend, cost-per-unit (request/user/feature), top line items driving the bill, optimisation opportunities with ROI, and lock-in risks. Use this skill PROACTIVELY whenever the user mentions infrastructure costs, cloud bills, vendor pricing, scaling cost, "our bill is too high", "we're burning cash on infra", "is this expensive at scale", or shares a bill, an architecture with cost implications, or a pricing page. Common trigger phrases include "our AWS bill is X", "we're spending Y on Z", "how much will this cost at scale", "is this cheaper than Y", "what's the cost of running this", "should we be on a different plan", "how can we cut our cloud bill", "what does this scale to financially", "is Datadog worth the cost". Also triggers when the user describes an architecture with non-trivial cost shape (large databases, high-throughput compute, video/AI inference, observability vendors, data egress). Especially important to trigger when the user is non-technical and may not see hidden cost drivers (egress, observability ingestion, idle reserved capacity, per-seat vendor pricing). Produces a structured assessment covering cost decomposition, unit economics, top three line items with optimisation ROI, vendor lock-in risk, and a verified-against-current-pricing recommendation.
Install with
Claude CodeCodexCursorGitHub CopilotGemini CLI
Supported by the Atlas install prompt. Skill-specific requirements vary.
Skill stats
Skills1CategoryEngineeringStars0
About this skill
Assesses cloud and infrastructure costs — current spend, projected spend, cost-per-unit (request/user/feature), top line items driving the bill, optimisation opportunities with ROI, and lock-in risks. Use this skill PROACTIVELY whenever the user mentions infrastructure costs, cloud bills, vendor pricing, scaling cost, "our bill is too high", "we're burning cash on infra", "is this expensive at scale", or shares a bill, an architecture with cost implications, or a pricing page. Common trigger phrases include "our AWS bill is X", "we're spending Y on Z", "how much will this cost at scale", "is this cheaper than Y", "what's the cost of running this", "should we be on a different plan", "how can we cut our cloud bill", "what does this scale to financially", "is Datadog worth the cost". Also triggers when the user describes an architecture with non-trivial cost shape (large databases, high-throughput compute, video/AI inference, observability vendors, data egress). Especially important to trigger when the user is non-technical and may not see hidden cost drivers (egress, observability ingestion, idle reserved capacity, per-seat vendor pricing). Produces a structured assessment covering cost decomposition, unit economics, top three line items with optimisation ROI, vendor lock-in risk, and a verified-against-current-pricing recommendation.
Quick start
Copy the install prompt. Use the green button above this README.
Send it to your agent. Paste it into your coding agent’s chat and send.
Review the setup. Your agent checks the skill’s instructions, requirements, and installation scope.
Assesses cloud and infrastructure costs — current spend, projected spend, cost-per-unit (request/user/feature), top line items driving the bill, optimisation opportunities with ROI, and lock-in risks. Use this skill PROACTIVELY whenever the user mentions infrastructure costs, cloud bills, vendor pricing, scaling cost, "our bill is too high", "we're burning cash on infra", "is this expensive at scale", or shares a bill, an architecture with cost implications, or a pricing page. Common trigger phrases include "our AWS bill is X", "we're spending Y on Z", "how much will this cost at scale", "is this cheaper than Y", "what's the cost of running this", "should we be on a different plan", "how can we cut our cloud bill", "what does this scale to financially", "is Datadog worth the cost". Also triggers when the user describes an architecture with non-trivial cost shape (large databases, high-throughput compute, video/AI inference, observability vendors, data egress). Especially important to trigger when the user is non-technical and may not see hidden cost drivers (egress, observability ingestion, idle reserved capacity, per-seat vendor pricing). Produces a structured assessment covering cost decomposition, unit economics, top three line items with optimisation ROI, vendor lock-in risk, and a verified-against-current-pricing recommendation.
About this listing
Category
Engineering
Reported license
MIT
Listing language (estimated)
English
Review status
Not individually reviewed
Agent compatibility
Atlas installation supports Claude Code, Codex, and Cursor. Skill-specific dependencies and features are checked during setup.
Claude Code
Codex
Cursor
GitHub Copilot
Gemini CLI