capacity-and-cost-engineering
Model technical capacity, unit cost, and budget constraints connected to demand, performance, and reliability decisions. Use when projecting capacity from growth forecasts, sizing for peak events, designing cost-aware scaling policies, defining budget thresholds or quota/rate-limit enforcement, running or planning load/soak tests as capacity evidence, resolving SLO-cost tradeoffs, or modeling multi-tenant demand distributions, hot-tenant skew, pooled or siloed headroom, fairness evidence, and tenant-variable unit cost. Do NOT use for financial P&L statements, fundraising scenarios, or SaaS metrics (route to financial-modeling); for infrastructure implementation or cloud-resource provisioning (route to platform-engineering); or for generic cloud-cost tips and universal utilization targets — this skill does not prescribe fixed savings rates or one-size-fits-all thresholds.
magnus919 · 已有静态检查记录
安装与使用
运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。
npx skills add magnus919/agent-skills --skill capacity-and-cost-engineering技能说明
name: capacity-and-cost-engineering description: >- Model technical capacity, unit cost, and budget constraints connected to demand, performance, and reliability decisions. Use when projecting capacity from growth forecasts, sizing for peak events, designing cost-aware scaling policies, defining budget thresholds or quota/rate-limit enforcement, running or planning load/soak tests as capacity evidence, resolving SLO-cost tradeoffs, or modeling multi-tenant demand distributions, hot-tenant skew, pooled or siloed headroom, fairness evidence, and tenant-variable unit cost. Do NOT use for financial P&L statements, fundraising scenarios, or SaaS metrics (route to financial-modeling); for infrastructure implementation or cloud-resource provisioning (route to platform-engineering); or for generic cloud-cost tips and universal utilization targets — this skill does not prescribe fixed savings rates or one-size-fits-all thresholds. license: MIT compatibility: Platform-agnostic methodology. No runtime dependency. metadata: tags: capacity-engineering, cost-engineering, unit-economics, load-testing, capacity-planning, budget-controls, quota-management, rate-limiting, cost-performance-tradeoffs, scaling-models, utilization-modeling, multi-tenant-capacity, tenant-unit-cost
Capacity and Cost Engineering
Connect demand, performance, reliability, and spend into defensible capacity and cost decisions. This skill models technical capacity, calculates unit cost at the infrastructure level, defines budget and quota controls, requires load/soak evidence for capacity claims, and makes cost-performance tradeoffs explicit — producing evidence that feeds production-readiness launch decisions and constrains or supports site-reliability-engineering SLO choices.
Connected dimensions
Demand (traffic and growth), performance (latency and throughput), reliability (SLOs and error budgets), and spend (cost) are treated as connected dimensions — a change in any one dimension affects the others. The skill's core method is tracing the connection:
| Dimension | Capacity impact | Cost impact |
|---|---|---|
| Demand (traffic, growth rate) | Drives compute, storage, network requirements | Drives baseline and projected spend |
| Performance (latency, throughput target) | Constrains resource headroom per request | Tighter targets increase unit cost |
| Reliability (SLO, error budget) | Requires redundancy, over-provisioning, or isolation | Higher SLOs increase cost non-linearly |
| Spend (budget, cost constraint) | Caps capacity; may force degraded-mode operation | Limits what SLO/performance targets are achievable |
A capacity decision that changes one dimension without modeling the others is incomplete. Every capacity model, unit-cost calculation, and budget decision in this skill must name at least one connection to another dimension with evidence or an explicit assumption.
Loading Guide
Load this skill when the task involves any of:
| Trigger | What to load |
|---|---|
| Project capacity from a growth forecast | SKILL.md + templates/capacity-model.md |
| Size capacity for a peak event (launch, Black Friday, seasonal) | SKILL.md + templates/capacity-model.md + templates/load-soak-test-plan.md |
| Calculate unit cost and connect to SLO or demand decisions | SKILL.md + templates/unit-economics-record.md |
| Define a budget threshold, spending alert, or hard cap | SKILL.md + templates/budget-quota-decision.md |
| Design quota or rate-limit enforcement in operational context | SKILL.md + templates/budget-quota-decision.md |
| Plan or review a load/soak test as capacity evidence | SKILL.md + templates/load-soak-test-plan.md |
| Resolve an SLO-cost tradeoff or cost-constrained reliability decision | SKILL.md + templates/slo-cost-tradeoff-record.md |
| Review a cost anomaly or attribute cost to services/teams | SKILL.md + templates/unit-economics-record.md |
| Model multi-tenant demand, skew, fairness, or tenant-variable unit cost | SKILL.md + references/multi-tenant-capacity-and-unit-cost.md + templates/tenant-capacity-model.md |
| Understand ownership boundaries with adjacent skills | SKILL.md + references/discovery-brief.md |
Working method
1. Model demand and capacity
Start with the demand signal: current traffic, growth rate, and any known peak events. Translate demand into capacity requirements using a capacity model that connects:
- Demand units (requests/second, concurrent users, GB ingested, messages/second) to
- Capacity units (vCPUs, memory GB, storage GB, IOPS, network throughput, provisioned throughput units) through
- Utilization targets (maximum sustainable utilization per resource, stated with rationale — never a universal percentage without context).
A capacity model is incomplete without a stated utilization target, the evidence for that target (why 70% and not 85%?), and the scaling trigger that fires when utilization approaches the target.
Use the capacity model template (templates/capacity-model.md) which captures demand assumptions, capacity-unit mapping, utilization targets with rationale, scaling triggers, and a projection over the relevant horizon. The template requires fields for assumptions, evidence source, ownership, and tradeoffs.
2. Calculate unit cost
Unit cost is the cost of serving one unit of demand — cost per request, cost per user per month, cost per GB stored, cost per provisioned capacity unit. Unit cost connects infrastructure spend to product and reliability decisions.
Calculate unit cost as:
unit cost = total cost of capacity / number of demand units served
Both numerator and denominator must be measured over the same period, with the same scope (service, team, or platform), and with the same allocation method s
阅读完整来源 ↗