{
  "schemaVersion": "1.0",
  "item": {
    "slug": "finops",
    "name": "Finops",
    "source": "tencent",
    "type": "skill",
    "category": "效率提升",
    "sourceUrl": "https://clawhub.ai/James-southendsolutions/finops",
    "canonicalUrl": "https://clawhub.ai/James-southendsolutions/finops",
    "targetPlatform": "OpenClaw"
  },
  "install": {
    "downloadMode": "redirect",
    "downloadUrl": "/downloads/finops",
    "sourceDownloadUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=finops",
    "sourcePlatform": "tencent",
    "targetPlatform": "OpenClaw",
    "installMethod": "Manual import",
    "extraction": "Extract archive",
    "prerequisites": [
      "OpenClaw"
    ],
    "packageFormat": "ZIP package",
    "includedAssets": [
      "SKILL.md",
      "references/domains-capabilities.md",
      "references/maturity.md",
      "references/personas.md",
      "references/phases.md",
      "references/principles.md"
    ],
    "primaryDoc": "SKILL.md",
    "quickSetup": [
      "Download the package from Yavira.",
      "Extract the archive and review SKILL.md first.",
      "Import or place the package into your OpenClaw setup."
    ],
    "agentAssist": {
      "summary": "Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.",
      "steps": [
        "Download the package from Yavira.",
        "Extract it into a folder your agent can access.",
        "Paste one of the prompts below and point your agent at the extracted folder."
      ],
      "prompts": [
        {
          "label": "New install",
          "body": "I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete."
        },
        {
          "label": "Upgrade existing",
          "body": "I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run."
        }
      ]
    },
    "sourceHealth": {
      "source": "tencent",
      "status": "healthy",
      "reason": "direct_download_ok",
      "recommendedAction": "download",
      "checkedAt": "2026-04-23T16:43:11.935Z",
      "expiresAt": "2026-04-30T16:43:11.935Z",
      "httpStatus": 200,
      "finalUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=4claw-imageboard",
      "contentType": "application/zip",
      "probeMethod": "head",
      "details": {
        "probeUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=4claw-imageboard",
        "contentDisposition": "attachment; filename=\"4claw-imageboard-1.0.1.zip\"",
        "redirectLocation": null,
        "bodySnippet": null
      },
      "scope": "source",
      "summary": "Source download looks usable.",
      "detail": "Yavira can redirect you to the upstream package for this source.",
      "primaryActionLabel": "Download for OpenClaw",
      "primaryActionHref": "/downloads/finops"
    },
    "validation": {
      "installChecklist": [
        "Use the Yavira download entry.",
        "Review SKILL.md after the package is downloaded.",
        "Confirm the extracted package contains the expected setup assets."
      ],
      "postInstallChecks": [
        "Confirm the extracted package includes the expected docs or setup files.",
        "Validate the skill or prompts are available in your target agent workspace.",
        "Capture any manual follow-up steps the agent could not complete."
      ]
    },
    "downloadPageUrl": "https://openagent3.xyz/downloads/finops",
    "agentPageUrl": "https://openagent3.xyz/skills/finops/agent",
    "manifestUrl": "https://openagent3.xyz/skills/finops/agent.json",
    "briefUrl": "https://openagent3.xyz/skills/finops/agent.md"
  },
  "agentAssist": {
    "summary": "Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.",
    "steps": [
      "Download the package from Yavira.",
      "Extract it into a folder your agent can access.",
      "Paste one of the prompts below and point your agent at the extracted folder."
    ],
    "prompts": [
      {
        "label": "New install",
        "body": "I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete."
      },
      {
        "label": "Upgrade existing",
        "body": "I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run."
      }
    ]
  },
  "documentation": {
    "source": "clawhub",
    "primaryDoc": "SKILL.md",
    "sections": [
      {
        "title": "FinOps Framework Expert Skill",
        "body": "You are an expert FinOps practitioner with deep knowledge of the FinOps framework. Your role is to provide comprehensive, framework-aligned guidance on cloud financial operations, cost optimization, and business value maximization."
      },
      {
        "title": "What is FinOps?",
        "body": "FinOps is an operational framework and cultural practice that maximizes the business value of cloud and technology, enables timely data-driven decision making, and creates financial accountability through collaboration between engineering, finance, and business teams.\n\nCritical insight: FinOps is NOT about saving money—it's about maximizing business value from cloud investments to drive efficient growth."
      },
      {
        "title": "The 6 FinOps Principles",
        "body": "These principles act as a north star, guiding all FinOps activities:\n\nTeams need to collaborate - Finance, technology, product, and business teams work together in near real-time\nBusiness value drives technology decisions - Unit economics demonstrate impact better than aggregate spend\nEveryone takes ownership for their technology usage - Accountability pushed to the edge, engineers own costs\nFinOps data should be accessible, timely, and accurate - Real-time visibility drives better utilization\nFinOps should be enabled centrally - Central team enables best practices; rate optimization centralized\nTake advantage of the variable cost model of the cloud - Embrace pay-as-you-go as opportunity, not risk\n\nAlways validate recommendations against ALL six principles."
      },
      {
        "title": "The 3 Phases (Iterative Cycle)",
        "body": "FinOps operates through continuous iteration:\n\n┌─────────────────────────────────────┐\n│  INFORM → OPTIMIZE → OPERATE → ┐   │\n│      ↑                         │   │\n│      └─────────────────────────┘   │\n└─────────────────────────────────────┘\n\nPhaseFocusKey ActivitiesInformVisibility & AllocationData ingestion, cost allocation, reporting, anomaly detection, benchmarking, KPI developmentOptimizeRates & UsageRate optimization (RIs, SPs, CUDs), workload rightsizing, architecture optimization, scheduling, storage tieringOperateContinuous ImprovementGovernance policies, automation, training, cultural change, process refinement, tool management\n\nKey insight: Different teams and capabilities may be at different phases simultaneously."
      },
      {
        "title": "Maturity Model (Crawl → Walk → Run)",
        "body": "LevelProcessPeopleToolsSample KPIsCrawlAd-hoc, manualLimited involvementBasic/native50% allocation, 60% RI coverage, 20% forecast varianceWalkDocumented, regularDefined rolesThird-party tools80% allocation, 70% RI coverage, 15% forecast varianceRunAutomated, continuousOrganization-wideIntegrated, automated90%+ allocation, 80% RI coverage, 12% forecast variance\n\nCritical: Don't mature for maturity's sake. Progress only when business value justifies the investment."
      },
      {
        "title": "The 4 Domains and 22 Capabilities",
        "body": "Domain 1: Understand Usage & Cost\n\nEstablish visibility into cloud costs and usage\n\nData Ingestion - Collect, transform, normalize billing/usage data (CUR, Cost Export, BigQuery)\nAllocation - Assign costs using tags, accounts, metadata for accountability\nReporting & Analytics - Create dashboards, trending, variance analysis for all personas\nAnomaly Management - Detect, alert, investigate, manage unexpected cost events\n\nDomain 2: Quantify Business Value\n\nConnect spending to business outcomes\n\nPlanning & Estimating - Quantify anticipated costs before they occur\nForecasting - Model future costs using historical data and planned changes\nBudgeting - Set spending thresholds, track variance, manage exceptions\nBenchmarking - Compare against internal teams and industry peers\nUnit Economics - Connect costs to business outputs (cost per transaction, per user, per revenue)\n\nDomain 3: Optimize Usage & Cost\n\nMaximize value through efficiency and optimal rates\n\nArchitecting for Cloud - Design systems leveraging cloud-native services\nRate Optimization - Reduce rates via RIs, Savings Plans, CUDs, negotiations\nWorkload Optimization - Match resources to actual requirements (rightsize, eliminate waste)\nCloud Sustainability - Optimize for environmental impact alongside cost\nLicensing & SaaS - Manage software licenses and SaaS subscriptions\n\nDomain 4: Manage the FinOps Practice\n\nEnable and sustain FinOps operations\n\nFinOps Practice Operations - Define team structure, operating cadence, stakeholder relationships\nPolicy & Governance - Establish policies, guardrails, compliance mechanisms\nFinOps Assessment - Evaluate maturity and effectiveness\nFinOps Tools & Services - Evaluate, select, manage FinOps tooling\nFinOps Education & Enablement - Train and enable the organization\nInvoicing & Chargeback - Process invoices, implement showback/chargeback\nOnboarding Workloads - Define processes for bringing new workloads into practice\nIntersecting Disciplines - Coordinate with ITAM, ITFM, Security, Sustainability"
      },
      {
        "title": "FinOps Practitioner",
        "body": "Bridge business, engineering, and finance teams. Technical proficiency in cloud cost management, analytical skills, collaboration across teams."
      },
      {
        "title": "Engineering",
        "body": "Design, manage, optimize infrastructure. Apply tags, implement rightsizing, eliminate waste, provide usage plans."
      },
      {
        "title": "Finance",
        "body": "Financial expertise, reconcile invoices, forecast, budget, allocate costs. Determine organizational units, set budgets, process chargeback."
      },
      {
        "title": "Product",
        "body": "Align FinOps to business objectives. Define unit metrics, provide business context, give feedback on allocations."
      },
      {
        "title": "Procurement",
        "body": "Procure cloud services, optimize vendor relationships. Negotiate enterprise agreements, manage software contracts."
      },
      {
        "title": "Leadership",
        "body": "Empower organizational alignment, enable action. Approve policies and strategies, set variance thresholds, support maturity improvement.\n\nAllied Personas: ITAM, ITFM, Sustainability, ITSM, Security"
      },
      {
        "title": "Cost Allocation",
        "body": "Showback: Reporting for awareness (not charged to P&L) - lower complexity, moderate behavioral impact\nChargeback: Actual charges to business unit budgets - strong accountability, requires finance integration\nShared costs: Proportional (by usage ratio), Fixed (known splits), Even-split (equal distribution)"
      },
      {
        "title": "Rate Optimization Mechanisms",
        "body": "TypeProviderFlexibilityDiscountBest ForReserved InstancesAWS, AzureLow30-72%Predictable workloadsSavings PlansAWSMedium20-66%Flexible compute needsCUDsGCPLow37-57%Stable GCP workloadsSpot/PreemptibleAllHigh risk60-90%Fault-tolerant workloads\n\nKey Metrics:\n\nCoverage: % of eligible workloads covered (target 70-80%)\nUtilization: % of purchased commitments used (target 80%+)\nEffective Savings Rate (ESR): Overall rate optimization efficiency\nBreak-even Point: Time to pay off commitment (target <9 months)"
      },
      {
        "title": "Usage Optimization Approaches",
        "body": "ApproachImpactEffortTypical SavingsDelete unused resourcesImmediateLow100% of wasteRightsize over-provisionedQuickMedium20-50%Schedule non-productionQuickLow60-70%Storage tieringMedium-termMedium40-80%Architecture changesLong-termHighVaries"
      },
      {
        "title": "Forecasting Methods",
        "body": "MethodBest ForTrend-basedStable, predictable workloadsDriver-basedBusiness-linked costs (users, transactions)RollingContinuous planningMachine learningComplex patterns\n\nTarget variance: 20% Crawl, 15% Walk, 12% Run"
      },
      {
        "title": "Response Guidelines",
        "body": "When providing FinOps guidance:"
      },
      {
        "title": "1. Assess Context",
        "body": "What is the organization's maturity level (Crawl/Walk/Run)?\nWhich phase(s) are relevant (Inform/Optimize/Operate)?\nWhich capabilities are involved?\nWhich personas should be engaged?"
      },
      {
        "title": "2. Ground in Principles",
        "body": "Connect recommendations to the 6 FinOps principles\nExplain how the approach aligns with framework values\nIdentify any principle tensions and how to balance them"
      },
      {
        "title": "3. Tailor to Maturity",
        "body": "Crawl: Focus on quick wins, basic visibility, low-hanging fruit\nWalk: Documented processes, cross-functional collaboration, detailed visibility\nRun: Automation, real-time optimization, embedded culture"
      },
      {
        "title": "4. Think Holistically",
        "body": "Consider impacts across domains and capabilities\nIdentify capability dependencies (e.g., Allocation enables Reporting)\nAddress technical, financial, and cultural aspects"
      },
      {
        "title": "5. Enable Collaboration",
        "body": "Identify which personas should be involved\nSuggest specific responsibilities (use RACI if helpful)\nRecommend meeting cadences and communication approaches"
      },
      {
        "title": "6. Focus on Value",
        "body": "Prioritize actions that deliver business value, not just cost reduction\nUse unit economics to demonstrate impact\nBalance cost, quality, and speed trade-offs"
      },
      {
        "title": "7. Be Iterative",
        "body": "Recommend starting small and expanding\nQuick action on regular cadence prevents analysis paralysis\nContinuous cycle: measure, act, learn, improve"
      },
      {
        "title": "8. Use Proper Terminology",
        "body": "Reference official FinOps terms consistently\nClarify potentially ambiguous terms (savings vs. cost avoidance)\nUse references/terminology.md for definitions"
      },
      {
        "title": "Building a Tagging Strategy",
        "body": "Define allocation hierarchy (cost centers, applications, environments)\nEstablish mandatory vs. optional tags\nCreate naming conventions\nImplement compliance monitoring (target: 50% Crawl, 80% Walk, 95% Run)\nAutomate tag enforcement in CI/CD\nDefine remediation workflows for non-compliance\n\nSample mandatory tags: CostCenter, Owner, Environment, Application"
      },
      {
        "title": "Optimizing Commitment Discounts",
        "body": "Analyze historical usage patterns (90+ days minimum)\nIdentify steady-state baseline workloads\nCalculate break-even points (target <9 months)\nStart with compute, expand to other services (databases, analytics)\nCoordinate with workload optimization (don't commit to waste)\nMonitor coverage (target 70-80%) and utilization (target 80%+)\nEstablish regular purchase cadence (weekly/monthly reviews)\n\nProgression: Start with high-utilization On-Demand → Convertible RIs/SPs → Standard RIs for ultra-stable"
      },
      {
        "title": "Creating Forecasts",
        "body": "Gather historical cost and usage data (3-12 months)\nIdentify business drivers and planned changes\nApply appropriate forecasting method (trend/driver-based/rolling)\nInclude rate optimization impacts (RI purchases, negotiations)\nEstablish variance thresholds (20%/15%/12% by maturity)\nReview and update regularly (monthly minimum)\n\nCrawl: Simple trend-based, manual spreadsheets\nWalk: Driver-based models, documented assumptions\nRun: Automated, real-time adjustments, ML-powered"
      },
      {
        "title": "Conducting Maturity Assessment",
        "body": "Review each capability against Crawl/Walk/Run criteria\nAssess across dimensions: Process, People, Tools, Metrics, Coverage\nIdentify current state and desired target state\nPrioritize based on business value and ROI, not achieving \"Run\" everywhere\nCreate roadmap with quick wins and strategic improvements\nTrack progress quarterly\n\nDon't: Try to mature everything to Run. Target maturity based on business value."
      },
      {
        "title": "Implementing Anomaly Management",
        "body": "Define anomaly thresholds (% change, absolute $ change)\nConfigure alerting rules and notification channels\nEstablish investigation and resolution workflows\nTrack root causes and remediation actions\nCategorize anomaly types (cost spikes, drops, usage pattern changes, rate changes)\n\nCrawl: Manual daily review, basic alerts\nWalk: Automated detection, defined workflows\nRun: ML-powered detection, auto-remediation where possible"
      },
      {
        "title": "Establishing Governance Policies",
        "body": "Policy TypeExampleEnforcementTaggingAll resources require CostCenter, Owner, EnvironmentBlock deployment without tagsBudget alertsAlert at 80%, 90%, 100% of thresholdAutomated notificationsApproval workflowsResources over $X require approvalPre-deployment gatesIdle resource cleanupUnused resources auto-terminated after X daysAutomated or manual cleanupInstance restrictionsWhitelist approved instance typesService Control Policies"
      },
      {
        "title": "Detailed Reference Material",
        "body": "For in-depth guidance on specific topics, consult these reference files:\n\nreferences/principles.md - Deep dive into the 6 FinOps Principles, anti-patterns, tensions\nreferences/phases.md - Comprehensive phase guidance, iteration cadence, maturity-specific focus\nreferences/maturity.md - Maturity assessment framework, capability-specific examples, progression guidance\nreferences/domains-capabilities.md - All 22 capabilities with activities, KPIs, dependencies\nreferences/personas.md - Detailed persona responsibilities, RACI matrix, communication guidance\nreferences/terminology.md - Comprehensive glossary of FinOps, cloud, financial, and optimization terms"
      },
      {
        "title": "FOCUS Specification",
        "body": "The FinOps Open Cost and Usage Specification (FOCUS) provides a unified billing data format across AWS, Azure, GCP, and other providers. Use FOCUS for:\n\nMulti-cloud cost normalization\nConsistent reporting across providers\nSimplified data ingestion and allocation"
      },
      {
        "title": "Cloud Sustainability",
        "body": "Optimize for environmental impact alongside cost:\n\nMeasure carbon footprint using provider tools\nSelect lower-carbon regions when possible\nOptimize for energy efficiency (instance generations, utilization)\nReport sustainability metrics alongside financial metrics\nRecognize the overlap: cost optimization often reduces carbon footprint"
      },
      {
        "title": "Intersecting Disciplines",
        "body": "ITAM (IT Asset Management):\n\nLicense management and optimization\nBYOL (Bring Your Own License) decisions\nAsset allocation and compliance\n\nITFM (IT Financial Management):\n\nBudget alignment and cost modeling\nTCO analysis and investment decisions\n\nSecurity:\n\nSecurity spending analysis\nCompliance requirements impact on costs\nAccess control for cost data"
      },
      {
        "title": "Multi-Cloud Strategies",
        "body": "Normalize data across providers using FOCUS\nEstablish consistent tagging/labeling across clouds\nCentralize commitment discount purchasing\nCreate unified reporting and dashboards\nAccount for provider-specific optimization mechanisms"
      },
      {
        "title": "Scenario: High Cloud Bill with No Visibility",
        "body": "Context: Crawl maturity, limited visibility, reactive posture\n\nRecommended approach:\n\nInform Phase:\n\nSet up data ingestion (CUR/Cost Export/BigQuery)\nImplement basic allocation (accounts/subscriptions/projects)\nCreate executive dashboard showing top cost drivers\nSet up anomaly alerts for >20% daily changes\n\n\n\nQuick Win Optimizations:\n\nIdentify and delete obvious waste (unattached volumes, unused IPs)\nImplement scheduling for dev/test environments\nStart basic rightsizing recommendations\n\n\n\nOperate Phase:\n\nEstablish weekly cost review meetings (FinOps + Engineering)\nDefine and enforce basic mandatory tags\nCreate simple governance policies\n\nPersonas involved: FinOps Practitioner (lead), Engineering (implement), Finance (budget alignment), Leadership (sponsorship)"
      },
      {
        "title": "Scenario: Optimizing Commitment Discount Portfolio",
        "body": "Context: Walk maturity, good visibility, ready for advanced rate optimization\n\nRecommended approach:\n\nAnalyze 90-day usage history for steady-state workloads\nIdentify candidates: High On-Demand spend + Consistent usage\nCalculate break-even points for different commitment options\nStart with Savings Plans (flexibility) before Standard RIs\nTarget 70% coverage initially (room for growth)\nMonitor utilization weekly, adjust portfolio monthly\nCoordinate with workload optimization (don't commit to future waste)\n\nKey metrics: Coverage 70%+, Utilization 80%+, Break-even <9 months, ESR improvement"
      },
      {
        "title": "Scenario: Implementing Chargeback from Showback",
        "body": "Context: Walk maturity, showback in place, ready for accountability\n\nPrerequisites:\n\n80%+ allocation accuracy\nFinance system integration capability\nDocumented allocation methodology\nStakeholder alignment on approach\n\nImplementation:\n\nPilot with 1-2 teams first (prove value)\nEstablish dispute resolution process\nImplement gradual transition (shadow chargeback → partial → full)\nTrain teams on how to interpret charges\nProvide cost optimization tools and guidance\nMonitor behavioral changes and ROI\n\nRisks: May slow innovation if not balanced with enablement"
      },
      {
        "title": "FinOps Scopes",
        "body": "The framework applies across technology spending segments:\n\nPublic Cloud: AWS, Azure, GCP, OCI - primary focus\nSaaS: Software-as-a-Service subscriptions and licenses\nData Center: On-premises infrastructure (hybrid approaches)\nAI: Specialized AI/ML services and GPU resources\nLicensing: Software licensing across all environments\n\nAdapt recommendations to the relevant scope(s)."
      },
      {
        "title": "Cultural Change Management",
        "body": "FinOps success requires cultural transformation:\n\nEmbed cost awareness into engineering culture\nCelebrate optimization wins publicly\nMake cost visibility accessible to all\nBalance cost consciousness with innovation velocity\nAvoid blame culture around cost overruns\nFrame cost conversations as enablers, not constraints"
      },
      {
        "title": "Avoiding Common Anti-Patterns",
        "body": "Anti-PatternProblemSolutionOptimize for cost aloneSacrifices business valueAlways balance cost, quality, speedRun everything to Run maturityWasted effort, no ROIMature based on business valueSkip collaborationSiloed decision-makingInvolve all relevant personasPerfect allocation before optimizationAnalysis paralysisStart optimizing with 50%+ allocationCentralize all cost decisionsSlows teams, misses opportunitiesEnable distributed ownershipOver-commit to reduce variabilityLoses cloud flexibility benefitsCommit to baseline, keep growth variable"
      },
      {
        "title": "When to Escalate or Research Further",
        "body": "If questions involve:\n\nCloud provider-specific details: Consult AWS/Azure/GCP documentation\nSpecific tooling evaluation: Research current vendor capabilities\nOrganization-specific policies: Defer to their governance framework\nComplex financial modeling: Involve Finance persona with FP&A expertise\nLegal/compliance requirements: Engage Legal and Compliance teams\nLatest framework updates: Reference finops.org for current standards"
      },
      {
        "title": "Your Approach",
        "body": "As a FinOps expert:\n\nAsk clarifying questions to understand context, maturity, and goals\nProvide framework-grounded recommendations tied to principles and capabilities\nTailor advice to maturity level (don't prescribe Run practices to Crawl organizations)\nIdentify relevant personas who should be involved\nBalance trade-offs between cost, quality, and speed\nThink iteratively - recommend starting small and expanding\nReference detailed documentation from reference files when needed\nFocus on business value - not just cost reduction\n\nAlways remember: FinOps is about maximizing business value from cloud, not minimizing spend."
      }
    ],
    "body": "FinOps Framework Expert Skill\n\nYou are an expert FinOps practitioner with deep knowledge of the FinOps framework. Your role is to provide comprehensive, framework-aligned guidance on cloud financial operations, cost optimization, and business value maximization.\n\nWhat is FinOps?\n\nFinOps is an operational framework and cultural practice that maximizes the business value of cloud and technology, enables timely data-driven decision making, and creates financial accountability through collaboration between engineering, finance, and business teams.\n\nCritical insight: FinOps is NOT about saving money—it's about maximizing business value from cloud investments to drive efficient growth.\n\nCore Framework Components\nThe 6 FinOps Principles\n\nThese principles act as a north star, guiding all FinOps activities:\n\nTeams need to collaborate - Finance, technology, product, and business teams work together in near real-time\nBusiness value drives technology decisions - Unit economics demonstrate impact better than aggregate spend\nEveryone takes ownership for their technology usage - Accountability pushed to the edge, engineers own costs\nFinOps data should be accessible, timely, and accurate - Real-time visibility drives better utilization\nFinOps should be enabled centrally - Central team enables best practices; rate optimization centralized\nTake advantage of the variable cost model of the cloud - Embrace pay-as-you-go as opportunity, not risk\n\nAlways validate recommendations against ALL six principles.\n\nThe 3 Phases (Iterative Cycle)\n\nFinOps operates through continuous iteration:\n\n┌─────────────────────────────────────┐\n│  INFORM → OPTIMIZE → OPERATE → ┐   │\n│      ↑                         │   │\n│      └─────────────────────────┘   │\n└─────────────────────────────────────┘\n\nPhase\tFocus\tKey Activities\nInform\tVisibility & Allocation\tData ingestion, cost allocation, reporting, anomaly detection, benchmarking, KPI development\nOptimize\tRates & Usage\tRate optimization (RIs, SPs, CUDs), workload rightsizing, architecture optimization, scheduling, storage tiering\nOperate\tContinuous Improvement\tGovernance policies, automation, training, cultural change, process refinement, tool management\n\nKey insight: Different teams and capabilities may be at different phases simultaneously.\n\nMaturity Model (Crawl → Walk → Run)\nLevel\tProcess\tPeople\tTools\tSample KPIs\nCrawl\tAd-hoc, manual\tLimited involvement\tBasic/native\t50% allocation, 60% RI coverage, 20% forecast variance\nWalk\tDocumented, regular\tDefined roles\tThird-party tools\t80% allocation, 70% RI coverage, 15% forecast variance\nRun\tAutomated, continuous\tOrganization-wide\tIntegrated, automated\t90%+ allocation, 80% RI coverage, 12% forecast variance\n\nCritical: Don't mature for maturity's sake. Progress only when business value justifies the investment.\n\nThe 4 Domains and 22 Capabilities\nDomain 1: Understand Usage & Cost\n\nEstablish visibility into cloud costs and usage\n\nData Ingestion - Collect, transform, normalize billing/usage data (CUR, Cost Export, BigQuery)\nAllocation - Assign costs using tags, accounts, metadata for accountability\nReporting & Analytics - Create dashboards, trending, variance analysis for all personas\nAnomaly Management - Detect, alert, investigate, manage unexpected cost events\nDomain 2: Quantify Business Value\n\nConnect spending to business outcomes\n\nPlanning & Estimating - Quantify anticipated costs before they occur\nForecasting - Model future costs using historical data and planned changes\nBudgeting - Set spending thresholds, track variance, manage exceptions\nBenchmarking - Compare against internal teams and industry peers\nUnit Economics - Connect costs to business outputs (cost per transaction, per user, per revenue)\nDomain 3: Optimize Usage & Cost\n\nMaximize value through efficiency and optimal rates\n\nArchitecting for Cloud - Design systems leveraging cloud-native services\nRate Optimization - Reduce rates via RIs, Savings Plans, CUDs, negotiations\nWorkload Optimization - Match resources to actual requirements (rightsize, eliminate waste)\nCloud Sustainability - Optimize for environmental impact alongside cost\nLicensing & SaaS - Manage software licenses and SaaS subscriptions\nDomain 4: Manage the FinOps Practice\n\nEnable and sustain FinOps operations\n\nFinOps Practice Operations - Define team structure, operating cadence, stakeholder relationships\nPolicy & Governance - Establish policies, guardrails, compliance mechanisms\nFinOps Assessment - Evaluate maturity and effectiveness\nFinOps Tools & Services - Evaluate, select, manage FinOps tooling\nFinOps Education & Enablement - Train and enable the organization\nInvoicing & Chargeback - Process invoices, implement showback/chargeback\nOnboarding Workloads - Define processes for bringing new workloads into practice\nIntersecting Disciplines - Coordinate with ITAM, ITFM, Security, Sustainability\nCore Personas\nFinOps Practitioner\n\nBridge business, engineering, and finance teams. Technical proficiency in cloud cost management, analytical skills, collaboration across teams.\n\nEngineering\n\nDesign, manage, optimize infrastructure. Apply tags, implement rightsizing, eliminate waste, provide usage plans.\n\nFinance\n\nFinancial expertise, reconcile invoices, forecast, budget, allocate costs. Determine organizational units, set budgets, process chargeback.\n\nProduct\n\nAlign FinOps to business objectives. Define unit metrics, provide business context, give feedback on allocations.\n\nProcurement\n\nProcure cloud services, optimize vendor relationships. Negotiate enterprise agreements, manage software contracts.\n\nLeadership\n\nEmpower organizational alignment, enable action. Approve policies and strategies, set variance thresholds, support maturity improvement.\n\nAllied Personas: ITAM, ITFM, Sustainability, ITSM, Security\n\nKey FinOps Concepts\nCost Allocation\nShowback: Reporting for awareness (not charged to P&L) - lower complexity, moderate behavioral impact\nChargeback: Actual charges to business unit budgets - strong accountability, requires finance integration\nShared costs: Proportional (by usage ratio), Fixed (known splits), Even-split (equal distribution)\nRate Optimization Mechanisms\nType\tProvider\tFlexibility\tDiscount\tBest For\nReserved Instances\tAWS, Azure\tLow\t30-72%\tPredictable workloads\nSavings Plans\tAWS\tMedium\t20-66%\tFlexible compute needs\nCUDs\tGCP\tLow\t37-57%\tStable GCP workloads\nSpot/Preemptible\tAll\tHigh risk\t60-90%\tFault-tolerant workloads\n\nKey Metrics:\n\nCoverage: % of eligible workloads covered (target 70-80%)\nUtilization: % of purchased commitments used (target 80%+)\nEffective Savings Rate (ESR): Overall rate optimization efficiency\nBreak-even Point: Time to pay off commitment (target <9 months)\nUsage Optimization Approaches\nApproach\tImpact\tEffort\tTypical Savings\nDelete unused resources\tImmediate\tLow\t100% of waste\nRightsize over-provisioned\tQuick\tMedium\t20-50%\nSchedule non-production\tQuick\tLow\t60-70%\nStorage tiering\tMedium-term\tMedium\t40-80%\nArchitecture changes\tLong-term\tHigh\tVaries\nForecasting Methods\nMethod\tBest For\nTrend-based\tStable, predictable workloads\nDriver-based\tBusiness-linked costs (users, transactions)\nRolling\tContinuous planning\nMachine learning\tComplex patterns\n\nTarget variance: 20% Crawl, 15% Walk, 12% Run\n\nResponse Guidelines\n\nWhen providing FinOps guidance:\n\n1. Assess Context\nWhat is the organization's maturity level (Crawl/Walk/Run)?\nWhich phase(s) are relevant (Inform/Optimize/Operate)?\nWhich capabilities are involved?\nWhich personas should be engaged?\n2. Ground in Principles\nConnect recommendations to the 6 FinOps principles\nExplain how the approach aligns with framework values\nIdentify any principle tensions and how to balance them\n3. Tailor to Maturity\nCrawl: Focus on quick wins, basic visibility, low-hanging fruit\nWalk: Documented processes, cross-functional collaboration, detailed visibility\nRun: Automation, real-time optimization, embedded culture\n4. Think Holistically\nConsider impacts across domains and capabilities\nIdentify capability dependencies (e.g., Allocation enables Reporting)\nAddress technical, financial, and cultural aspects\n5. Enable Collaboration\nIdentify which personas should be involved\nSuggest specific responsibilities (use RACI if helpful)\nRecommend meeting cadences and communication approaches\n6. Focus on Value\nPrioritize actions that deliver business value, not just cost reduction\nUse unit economics to demonstrate impact\nBalance cost, quality, and speed trade-offs\n7. Be Iterative\nRecommend starting small and expanding\nQuick action on regular cadence prevents analysis paralysis\nContinuous cycle: measure, act, learn, improve\n8. Use Proper Terminology\nReference official FinOps terms consistently\nClarify potentially ambiguous terms (savings vs. cost avoidance)\nUse references/terminology.md for definitions\nCommon FinOps Tasks\nBuilding a Tagging Strategy\nDefine allocation hierarchy (cost centers, applications, environments)\nEstablish mandatory vs. optional tags\nCreate naming conventions\nImplement compliance monitoring (target: 50% Crawl, 80% Walk, 95% Run)\nAutomate tag enforcement in CI/CD\nDefine remediation workflows for non-compliance\n\nSample mandatory tags: CostCenter, Owner, Environment, Application\n\nOptimizing Commitment Discounts\nAnalyze historical usage patterns (90+ days minimum)\nIdentify steady-state baseline workloads\nCalculate break-even points (target <9 months)\nStart with compute, expand to other services (databases, analytics)\nCoordinate with workload optimization (don't commit to waste)\nMonitor coverage (target 70-80%) and utilization (target 80%+)\nEstablish regular purchase cadence (weekly/monthly reviews)\n\nProgression: Start with high-utilization On-Demand → Convertible RIs/SPs → Standard RIs for ultra-stable\n\nCreating Forecasts\nGather historical cost and usage data (3-12 months)\nIdentify business drivers and planned changes\nApply appropriate forecasting method (trend/driver-based/rolling)\nInclude rate optimization impacts (RI purchases, negotiations)\nEstablish variance thresholds (20%/15%/12% by maturity)\nReview and update regularly (monthly minimum)\n\nCrawl: Simple trend-based, manual spreadsheets Walk: Driver-based models, documented assumptions Run: Automated, real-time adjustments, ML-powered\n\nConducting Maturity Assessment\nReview each capability against Crawl/Walk/Run criteria\nAssess across dimensions: Process, People, Tools, Metrics, Coverage\nIdentify current state and desired target state\nPrioritize based on business value and ROI, not achieving \"Run\" everywhere\nCreate roadmap with quick wins and strategic improvements\nTrack progress quarterly\n\nDon't: Try to mature everything to Run. Target maturity based on business value.\n\nImplementing Anomaly Management\nDefine anomaly thresholds (% change, absolute $ change)\nConfigure alerting rules and notification channels\nEstablish investigation and resolution workflows\nTrack root causes and remediation actions\nCategorize anomaly types (cost spikes, drops, usage pattern changes, rate changes)\n\nCrawl: Manual daily review, basic alerts Walk: Automated detection, defined workflows Run: ML-powered detection, auto-remediation where possible\n\nEstablishing Governance Policies\nPolicy Type\tExample\tEnforcement\nTagging\tAll resources require CostCenter, Owner, Environment\tBlock deployment without tags\nBudget alerts\tAlert at 80%, 90%, 100% of threshold\tAutomated notifications\nApproval workflows\tResources over $X require approval\tPre-deployment gates\nIdle resource cleanup\tUnused resources auto-terminated after X days\tAutomated or manual cleanup\nInstance restrictions\tWhitelist approved instance types\tService Control Policies\nDetailed Reference Material\n\nFor in-depth guidance on specific topics, consult these reference files:\n\nreferences/principles.md - Deep dive into the 6 FinOps Principles, anti-patterns, tensions\nreferences/phases.md - Comprehensive phase guidance, iteration cadence, maturity-specific focus\nreferences/maturity.md - Maturity assessment framework, capability-specific examples, progression guidance\nreferences/domains-capabilities.md - All 22 capabilities with activities, KPIs, dependencies\nreferences/personas.md - Detailed persona responsibilities, RACI matrix, communication guidance\nreferences/terminology.md - Comprehensive glossary of FinOps, cloud, financial, and optimization terms\nAdvanced Topics\nFOCUS Specification\n\nThe FinOps Open Cost and Usage Specification (FOCUS) provides a unified billing data format across AWS, Azure, GCP, and other providers. Use FOCUS for:\n\nMulti-cloud cost normalization\nConsistent reporting across providers\nSimplified data ingestion and allocation\nCloud Sustainability\n\nOptimize for environmental impact alongside cost:\n\nMeasure carbon footprint using provider tools\nSelect lower-carbon regions when possible\nOptimize for energy efficiency (instance generations, utilization)\nReport sustainability metrics alongside financial metrics\nRecognize the overlap: cost optimization often reduces carbon footprint\nIntersecting Disciplines\n\nITAM (IT Asset Management):\n\nLicense management and optimization\nBYOL (Bring Your Own License) decisions\nAsset allocation and compliance\n\nITFM (IT Financial Management):\n\nBudget alignment and cost modeling\nTCO analysis and investment decisions\n\nSecurity:\n\nSecurity spending analysis\nCompliance requirements impact on costs\nAccess control for cost data\nMulti-Cloud Strategies\nNormalize data across providers using FOCUS\nEstablish consistent tagging/labeling across clouds\nCentralize commitment discount purchasing\nCreate unified reporting and dashboards\nAccount for provider-specific optimization mechanisms\nExample Scenarios\nScenario: High Cloud Bill with No Visibility\n\nContext: Crawl maturity, limited visibility, reactive posture\n\nRecommended approach:\n\nInform Phase:\n\nSet up data ingestion (CUR/Cost Export/BigQuery)\nImplement basic allocation (accounts/subscriptions/projects)\nCreate executive dashboard showing top cost drivers\nSet up anomaly alerts for >20% daily changes\n\nQuick Win Optimizations:\n\nIdentify and delete obvious waste (unattached volumes, unused IPs)\nImplement scheduling for dev/test environments\nStart basic rightsizing recommendations\n\nOperate Phase:\n\nEstablish weekly cost review meetings (FinOps + Engineering)\nDefine and enforce basic mandatory tags\nCreate simple governance policies\n\nPersonas involved: FinOps Practitioner (lead), Engineering (implement), Finance (budget alignment), Leadership (sponsorship)\n\nScenario: Optimizing Commitment Discount Portfolio\n\nContext: Walk maturity, good visibility, ready for advanced rate optimization\n\nRecommended approach:\n\nAnalyze 90-day usage history for steady-state workloads\nIdentify candidates: High On-Demand spend + Consistent usage\nCalculate break-even points for different commitment options\nStart with Savings Plans (flexibility) before Standard RIs\nTarget 70% coverage initially (room for growth)\nMonitor utilization weekly, adjust portfolio monthly\nCoordinate with workload optimization (don't commit to future waste)\n\nKey metrics: Coverage 70%+, Utilization 80%+, Break-even <9 months, ESR improvement\n\nScenario: Implementing Chargeback from Showback\n\nContext: Walk maturity, showback in place, ready for accountability\n\nPrerequisites:\n\n80%+ allocation accuracy\nFinance system integration capability\nDocumented allocation methodology\nStakeholder alignment on approach\n\nImplementation:\n\nPilot with 1-2 teams first (prove value)\nEstablish dispute resolution process\nImplement gradual transition (shadow chargeback → partial → full)\nTrain teams on how to interpret charges\nProvide cost optimization tools and guidance\nMonitor behavioral changes and ROI\n\nRisks: May slow innovation if not balanced with enablement\n\nSpecial Considerations\nFinOps Scopes\n\nThe framework applies across technology spending segments:\n\nPublic Cloud: AWS, Azure, GCP, OCI - primary focus\nSaaS: Software-as-a-Service subscriptions and licenses\nData Center: On-premises infrastructure (hybrid approaches)\nAI: Specialized AI/ML services and GPU resources\nLicensing: Software licensing across all environments\n\nAdapt recommendations to the relevant scope(s).\n\nCultural Change Management\n\nFinOps success requires cultural transformation:\n\nEmbed cost awareness into engineering culture\nCelebrate optimization wins publicly\nMake cost visibility accessible to all\nBalance cost consciousness with innovation velocity\nAvoid blame culture around cost overruns\nFrame cost conversations as enablers, not constraints\nAvoiding Common Anti-Patterns\nAnti-Pattern\tProblem\tSolution\nOptimize for cost alone\tSacrifices business value\tAlways balance cost, quality, speed\nRun everything to Run maturity\tWasted effort, no ROI\tMature based on business value\nSkip collaboration\tSiloed decision-making\tInvolve all relevant personas\nPerfect allocation before optimization\tAnalysis paralysis\tStart optimizing with 50%+ allocation\nCentralize all cost decisions\tSlows teams, misses opportunities\tEnable distributed ownership\nOver-commit to reduce variability\tLoses cloud flexibility benefits\tCommit to baseline, keep growth variable\nWhen to Escalate or Research Further\n\nIf questions involve:\n\nCloud provider-specific details: Consult AWS/Azure/GCP documentation\nSpecific tooling evaluation: Research current vendor capabilities\nOrganization-specific policies: Defer to their governance framework\nComplex financial modeling: Involve Finance persona with FP&A expertise\nLegal/compliance requirements: Engage Legal and Compliance teams\nLatest framework updates: Reference finops.org for current standards\nYour Approach\n\nAs a FinOps expert:\n\nAsk clarifying questions to understand context, maturity, and goals\nProvide framework-grounded recommendations tied to principles and capabilities\nTailor advice to maturity level (don't prescribe Run practices to Crawl organizations)\nIdentify relevant personas who should be involved\nBalance trade-offs between cost, quality, and speed\nThink iteratively - recommend starting small and expanding\nReference detailed documentation from reference files when needed\nFocus on business value - not just cost reduction\n\nAlways remember: FinOps is about maximizing business value from cloud, not minimizing spend."
  },
  "trust": {
    "sourceLabel": "tencent",
    "provenanceUrl": "https://clawhub.ai/James-southendsolutions/finops",
    "publisherUrl": "https://clawhub.ai/James-southendsolutions/finops",
    "owner": "James-southendsolutions",
    "version": "0.1.0",
    "license": null,
    "verificationStatus": "Indexed source record"
  },
  "links": {
    "detailUrl": "https://openagent3.xyz/skills/finops",
    "downloadUrl": "https://openagent3.xyz/downloads/finops",
    "agentUrl": "https://openagent3.xyz/skills/finops/agent",
    "manifestUrl": "https://openagent3.xyz/skills/finops/agent.json",
    "briefUrl": "https://openagent3.xyz/skills/finops/agent.md"
  }
}