Financial Operations para cloud — visibilidad de costos, optimización, gobernanza, y cultura de responsabilidad financiera. Usar cuando el usuario pida "optimizar costos cloud", "implementar FinOps", "gobernanza de costos", "cost allocation", "showback/chargeback", o mencione FinOps, cloud cost management, reserved instances, savings plans, right-sizing, cost anomaly detection, o unit economics para cloud. [EXPLICIT]
From jm-adknpx claudepluginhub javimontano/jm-adk-alfaThis skill is limited to using the following tools:
agents/guardian.mdagents/lead.mdagents/specialist.mdagents/support.mdevals/evals.jsonknowledge/body-of-knowledge.mdknowledge/knowledge-graph.mdprompts/meta.mdprompts/primary.mdprompts/variations/deep.mdprompts/variations/quick.mdreferences/finops-operating-model.mdreferences/finops-optimization-playbook.mdreferences/finops-unit-economics.mdtemplates/output.docx.mdtemplates/output.htmlFinancial Operations para cloud — visibilidad completa de costos, optimización de rate y usage, gobernanza financiera, forecasting, y unit economics. Transforma cloud cost de un gasto opaco en un driver de decisiones de negocio con responsabilidad distribuida por equipos. [EXPLICIT]
Everyone takes ownership of their cloud usage — FinOps is a cultural shift, not just a tooling exercise. Engineers, finance, and leadership share accountability for cloud spend. Sin ownership distribuido, la optimización es un juego de whack-a-mole centralizado. [EXPLICIT]
Decisions are driven by business value, not just cost reduction — a $10K/month service that generates $100K revenue is well-spent. El objetivo no es "gastar menos" sino "gastar mejor". Cost efficiency sin business context es austeridad ciega. [EXPLICIT]
Cloud cost is a variable, manageable expense — real-time data enables real-time decisions. A diferencia de infraestructura on-premise (CAPEX fijo), cloud es OPEX variable. Esto es una ventaja competitiva si se gestiona activamente; un riesgo financiero si se ignora. [EXPLICIT]
Parametros:
MODO: [piloto-auto | desatendido | supervisado | paso-a-paso]
PROFUNDIDAD: [express | standard | deep]
FORMATO: [ejecutivo | tecnico | hibrido]
CLOUD: [aws | azure | gcp | multi-cloud]
ALCANCE: [visibility | optimization | governance | full]
Modos de autonomia:
- piloto-auto: Auto para analisis y recomendaciones, HITL para decisiones de compra (RI/SP). [EXPLICIT]
- desatendido: Cero interrupciones. Analisis completo con supuestos documentados. [EXPLICIT]
- supervisado: Autonomo con checkpoint en compras comprometidas y cambios de gobernanza. [EXPLICIT]
- paso-a-paso: Confirma cada seccion, cada recomendacion, y cada calculo. [EXPLICIT]
Deteccion automatica:
- Si existe billing data o Cost Explorer → CLOUD se infiere del provider
- Si el input menciona "RI" o "savings plans" → ALCANCE incluye optimization
- Si el input menciona "tags" o "allocation" → ALCANCE incluye visibility
- Si el input menciona "forecast" o "budget" → ALCANCE incluye governance
- Default: MODO=piloto-auto, PROFUNDIDAD=standard, ALCANCE=full, CLOUD=aws
Establece la base de visibilidad: saber quien gasta que, donde, y por que. [EXPLICIT]
Load references:
Read ${CLAUDE_SKILL_DIR}/references/finops-unit-economics.md
Tagging Strategy:
Environment, Team, Project, CostCenter, Application, OwnerCompliance, DataClassification, ExpirationDateCost Allocation:
Dashboards:
Entregable: Tagging strategy document, cost allocation model, dashboard specifications.
Reducir el precio unitario de los recursos cloud sin cambiar el consumo. [EXPLICIT]
Load references:
Read ${CLAUDE_SKILL_DIR}/references/finops-optimization-playbook.md
Reserved Instances / Savings Plans:
Spot / Preemptible:
Enterprise Discounts:
Entregable: Rate optimization plan con savings estimados por tecnica, timeline de implementacion.
Reducir el consumo eliminando waste y ajustando el tamaño de los recursos. [EXPLICIT]
Load references:
Read ${CLAUDE_SKILL_DIR}/references/finops-optimization-playbook.md
Right-Sizing:
Idle Resource Detection:
Scheduling:
Storage Tiering:
Entregable: Waste inventory, right-sizing recommendations, scheduling plan, estimated savings.
Estructura organizacional, procesos, y cadencia para sostener FinOps. [EXPLICIT]
Load references:
Read ${CLAUDE_SKILL_DIR}/references/finops-operating-model.md
Team Structure:
Cadence:
Maturity Model — Crawl/Walk/Run:
| Dimension | Crawl | Walk | Run |
|---|---|---|---|
| Visibility | Basic tagging, monthly reports | Full allocation, daily dashboards | Real-time, automated anomaly detection |
| Optimization | Ad-hoc right-sizing | Systematic RI/SP, scheduling | Autonomous optimization, ML-driven |
| Governance | Reactive budgets | Proactive forecasting | Predictive, business-aligned KPIs |
| Culture | Centralized FinOps team | Team-level champions | Engineering-owned, self-service |
Entregable: FinOps operating model document, RACI, cadence calendar, maturity assessment.
Predecir y controlar el gasto cloud con precision creciente. [EXPLICIT]
Forecasting Methods:
Budget Management:
Anomaly Detection:
Variance Analysis:
Entregable: Forecast model, budget framework, anomaly detection rules, variance report template.
Conectar cloud cost con metricas de negocio para decisiones informadas. [EXPLICIT]
Load references:
Read ${CLAUDE_SKILL_DIR}/references/finops-unit-economics.md
Unit Cost Metrics:
Margin Analysis:
Cloud P&L:
Showback/Chargeback:
Entregable: Unit economics dashboard, cloud P&L, showback/chargeback model, business alignment scorecard.
| Profundidad | Scope | Depth | Effort | When to Use |
|---|---|---|---|---|
| Express | Visibility + quick wins | Top-line analysis | 2-3 dias | Quick cost review, executive briefing |
| Standard | All 6 sections | Full analysis | 5-8 dias | FinOps program launch, quarterly review |
| Deep | All 6 + implementation guides | Full + tooling setup | 10-15 dias | Enterprise FinOps transformation |
Startup sin historico: Usar industry benchmarks y driver-based forecasting. Establecer tagging desde dia 1. Focus en S1 y S4 antes de optimizar. [EXPLICIT]
Multi-cloud environment: Normalizar costos cross-provider. Usar herramientas multi-cloud (CloudHealth, Apptio, Spot.io). Allocation model debe ser provider-agnostic. [EXPLICIT]
Acquired company integration: Mapear tagging strategies, unificar cost centers, reconciliar contratos de RI/SP, consolidar billing accounts. [EXPLICIT]
Massive AI/ML spend: AI workloads tienen patrones unicos (GPU burst, training vs. inference). Separar AI cost center. Evaluar Inferentia/Trainium, spot para training. [EXPLICIT]
Regulated industry: Cost data puede contener metadata sensible. Chargeback reports deben cumplir data governance. Shared cost allocation debe ser auditable. [EXPLICIT]
piloto-auto (default).standard (default).full (default). Si el contexto menciona solo "costos" → visibility + optimization. Si menciona "FinOps program" → full.El agente que ejecuta este skill debe verificar cada item antes de entregar el output al usuario.
| Skill | Relacion |
|---|---|
aws-architecture-design | Diseño AWS con cost considerations integradas |
aws-architecture-audit | Auditoría que incluye cost optimization pillar |
infrastructure-architecture | Infraestructura cloud donde se aplica FinOps |
cloud-migration | Migracion cloud donde FinOps debe integrarse desde dia 1 |
cost-estimation | Estimacion de costos para proyectos nuevos |
analisis-horizontal-financiero | Analisis financiero complementario (no cloud) |
if FORMATO == "ejecutivo":
Executive dashboard: total spend, trend, savings opportunities, unit economics
Audiencia: CFO, CTO, VP Engineering
if FORMATO == "tecnico":
Full 6-section analysis + implementation details + tool configurations
Audiencia: Cloud engineers, FinOps practitioners, DevOps
if FORMATO == "hibrido":
Executive summary + technical deep-dive por seccion
Audiencia: Engineering managers, technical leads reporting to C-level
## {Organization Name} — FinOps Assessment & Roadmap
### Executive Summary
[Total cloud spend, trend, savings potential, maturity score, top recommendations]
### S1: Cost Visibility & Allocation [Tag Compliance: X%]
[Tagging strategy, allocation model, dashboard specs]
### S2: Rate Optimization [Potential Savings: $XX,XXX/month]
[RI/SP analysis, spot opportunities, enterprise discounts]
### S3: Usage Optimization [Waste Identified: $XX,XXX/month]
[Right-sizing, idle resources, scheduling, storage tiering]
### S4: FinOps Operating Model [Maturity: Crawl|Walk|Run]
[Team structure, RACI, cadence, maturity roadmap]
### S5: Forecasting & Budgeting [Forecast Accuracy: ±X%]
[Forecast model, budget framework, anomaly detection]
### S6: Unit Economics [CPT: $X.XX, Cloud/Revenue: X%]
[Unit costs, margin analysis, cloud P&L, showback/chargeback]
### Implementation Roadmap
[Phased plan with quick wins, medium-term, strategic initiatives]
### Appendix: Savings Detail
[Line-item savings by category with confidence level]
Fuente: FinOps Foundation. FinOps Framework (2024). | Storment, J.R. & Fuller, M. (2023). Cloud FinOps (2nd ed.). O'Reilly.
Searches, retrieves, and installs Agent Skills from prompts.chat registry using MCP tools like search_skills and get_skill. Activates for finding skills, browsing catalogs, or extending Claude.