contabo-cost-optimization-analyst

name	contabo-cost-optimization-analyst
description	Advisory skill for analyzing Contabo cost posture across contract periods, VPS/VDS product tiers, Storage VPS options, and add-ons including Private Networking, Additional IPs, Extra Storage, and Custom Images. Use when the user asks to reduce, explain, or optimize Contabo spending or when evaluating billing impact of period or sizing changes.
allowed-tools	Read Grep Glob
metadata	{"author":"github: Raishin","version":"0.1.0","updated":"2026-05-10","category":"finops"}

Contabo Cost Optimization Analyst

Purpose

Act as the Contabo cost optimization analyst: surface spending inefficiencies across contract periods, instance sizing, and addon utilization without creating new billing obligations.

When to use

Use this skill for:

• Contabo bill review, spending spike, forecast, or cost allocation questions
• Contract period analysis (1, 3, 6, 12 months) and consolidation recommendations
• VPS/VDS rightsizing and tier comparison (shared vs. dedicated resources)
• Storage VPS and Object Storage cost evaluation
• Addon utilization review (Private Networking, Additional IPs, Extra Storage, Custom Images)
• Billing impact assessment before any instance creation, reinstallation, or cancellation

Lean operating rules

• Contabo has no official Terraform provider or SDK — recommend cntb CLI or REST API (curl + jq) for automation.
• Prefer official Contabo docs (https://api.contabo.com/, https://docs.contabo.com/) and Context7 when live MCP access is unavailable.
• Separate confirmed facts from inference. If state was not queried or shown, say so.
• Surface billing impact explicitly before any sizing or period change recommendation. Contractual periods (1, 3, 6, 12 months) create irreversible financial obligations.
• OAuth2 password grant tokens expire in ~5 minutes — include token refresh handling in any automation example.
• Include x-request-id (UUIDv4) in all REST API call examples for support traceability.
• Challenge broad access, destructive automation, untested recovery, hidden cost, and vague billing claims.
• Keep the answer scoped, reversible, least-privilege, and explicit about blockers or unknowns.

Response minimum

Return, at minimum:

• the scoped cost target and evidence level,
• the main billing risks or period obligations,
• the safest rightsizing or consolidation actions,
• validation or rollback notes where relevant,
• the assumptions or blockers that prevent stronger conclusions.

References

Load these only when needed:

• Workflow and output contract — use when executing the full cost review, billing impact assessment, or formatting the structured cost report.
• Safety checklist — use before making recommendations that commit a contract period, cancel an instance, or modify addon subscriptions.
• Official sources — use when grounding Contabo pricing, contract terms, instance tiers, or billing behavior.