CtrlK
BlogDocsLog inGet started
Tessl Logo

finops

Cloud financial operations assessment and strategy using FinOps Foundation framework. Use when the user asks to 'assess cloud costs', 'optimize cloud spending', 'FinOps assessment', 'cloud cost analysis', 'rightsizing', 'reservation strategy', 'showback/chargeback model', 'cloud unit economics', 'cost allocation', or mentions 'cloud financial management', 'cost optimization', 'FinOps maturity'. [EXPLICIT]

SKILL.md
Quality
Evals
Security

FinOps — Cloud Financial Operations

Generic, brand-neutral engineering capability; sourced playbooks in references//knowledge/. [DOC]

TL;DR

Generates cloud financial operations assessment and strategy: FinOps maturity evaluation (Crawl/Walk/Run), cost visibility analysis, optimization opportunity identification, governance model design, and unit economics framework [EXPLICIT]

When to use

  • Use for the finops capability. [EXPLICIT]
  • NOT for adjacent domains — route to the matching skill. [INFERENCE]

Sub-capabilities (resource map)

Deep, evidence-tagged playbooks — open the one the task needs (ICM Layer 3, on-demand). [INFERENCE]

Reference
references/full-playbook.md
references/knowledge-graph.mmd
references/state-of-the-art.md

Procedure

  1. Resolve the sub-capability; open the matching references/ playbook. [EXPLICIT]
  2. Apply its decision tables; pick the strategy explicitly. [EXPLICIT]
  3. Validate against the Quality Criteria and tag every claim. [EXPLICIT]

Quality Criteria

  • Sub-capability resolved to one playbook. [INFERENCE]
  • Claims evidence-tagged. [EXPLICIT]

Contract

  • Aceptación: capability resolved to its reference playbook, applied, validated, evidence-tagged. [EXPLICIT]
  • Límites: scoped to this capability; deep procedure in references/. [EXPLICIT]
  • Casos borde: · Multi-cloud: Separate analysis per provider + cross-cloud optimization (workload placement). · Startup/fast growth: Focus on unit economics and auto-scaling, not reservat. [EXPLICIT]
  • Supuestos: Assumptions: · At least one major cloud provider (AWS/Azure/GCP) · Monthly cloud spend above the threshold where FinOps overhead produces net savings · Organization has enginee. [SUPUESTO]
  • Trade-off: Decision Enables Constrains When to Use --- --- --- --- Full assessment Complete visibility + optimization plan 4-6 days, requires billing data Annual FinOp. [EXPLICIT]

Packet

Capas del packet, cargables bajo demanda (disciplina ICM: una capa por vez, nunca todas juntas): references/ guías de profundidad (cargar UNA por etapa) · knowledge/ cuerpo de conocimiento · prompts/ prompts listos · examples/ salida de ejemplo · agents/ subagentes del packet · assets/ recursos estáticos.

Repository
JaviMontano/claude-plugins
Last updated
First committed

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.