القائمة
Use at the start of any CloudZero cost analysis session to load organization-specific context — custom dimensions, team structures, cost allocation policies, and workflows
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Use when proactively scanning for cost anomalies, unusual spending, unexpected charges, or irregular patterns — during weekly reviews, after incidents, or when something looks off
Use when comparing costs between time periods, environments, accounts, regions, or teams to understand spending differences and identify inefficiencies
Project the monthly cost of an infrastructure definition (Terraform, CDK, CloudFormation, SAM) using CloudZero spend data. Reads IaC files, enumerates resources, and produces a line-item cost breakdown.
Use when a cost spike or unexpected increase has already been identified and you need to find which service, account, or resource is responsible
Use when analyzing whether costs are growing, declining, or stable over time — for forecasting, budget planning, or understanding spending velocity
Use when analyzing costs by organization-specific dimensions like teams, products, business units, or applications for showback, chargeback, or business-aligned cost reporting
| name | understand-cloudzero-organization |
| description | Use at the start of any CloudZero cost analysis session to load organization-specific context — custom dimensions, team structures, cost allocation policies, and workflows |
| author | CloudZero <support@cloudzero.com> |
| version | 1.0.0 |
| license | Apache-2.0 |
This foundational skill retrieves organization-specific context from CloudZero that is essential for accurate cost analysis. It should be invoked once at the beginning of any cost analysis session to understand the organization's unique dimensions, workflows, and business context.
Note: Once organization context is retrieved in a conversation, other skills should reference the cached information rather than re-reading it.
Organization context from get_org_context includes:
Before calling the MCP tool, check the conversation history:
get_org_context been called already in this conversation?Call the CloudZero MCP server tool:
get_org_context()
This returns comprehensive organization-specific information.
Review the returned context to understand:
Store key insights from organization context for reference by subsequent skills:
After retrieving organization context, provide a concise summary:
Organization Name: [If available] Primary Focus: [Optimization / Allocation / FinOps / etc.]
Based on organization context:
All other cost analysis skills should follow this pattern:
## Prerequisites
Before using this skill, ensure organization context has been retrieved via the
[Understand CloudZero Organization](../understand-cloudzero-organization/SKILL.md) skill.
If not already done in this conversation:
1. Use the understand-cloudzero-organization skill first
2. Then proceed with this skill's analysis
If organization context was already retrieved, reference that information.
Avoid redundant calls: Once get_org_context is called in a conversation,
DO NOT call it again. Other skills should reference the previously retrieved context
rather than making duplicate API calls.
User request: "Analyze my cloud costs"
Assistant response:
I'll start by understanding your CloudZero organization context, then analyze your costs.
[Calls get_org_context]
I can see your organization uses custom dimensions for Teams and Products.
You have 8 engineering teams and 3 main products. Your cost allocation
policy requires Environment and Team tags on all resources.
Now let me analyze your top cost drivers using these dimensions...
[Proceeds with cost analysis using appropriate dimensions]
Re-invoke this skill if: