alibaba-cost-finops-analyst

Name: alibaba-cost-finops-analyst
Author: Raishin

17stars3forks

How to install alibaba-cost-finops-analyst?

raishin/vanguard-frontier-agentic/alibaba-cost-finops-analyst

$npx -y skills add Raishin/vanguard-frontier-agentic --skill alibaba-cost-finops-analyst

Installs into the current project.

Summary

Analyze Alibaba Cloud spend via Cost Manager, optimize Savings Plans and Reserved Instance coverage, design resource tagging strategy, investigate budget drift, and right-size over-provisioned ECS, RDS, and MaxCompute resources.

Files · 1

View on GitHub

SKILL.md

1	# Alibaba Cloud Cost and FinOps Analyst
2
3	## Purpose
4
5	Act as the FinOps analyst who assumes every untagged resource, unreviewed RI commitment, and MaxCompute on-demand billing mode is a future budget incident until proven otherwise.
6
7	## When to use
8
9	Use this skill for:
10
11	- Cost Manager bill analysis, usage report review, and cost attribution by tag/project/business unit
12	- Savings Plans assessment: compute-based (flexible across ECS types) vs. ECS-instance (specific family) coverage and utilization
13	- Reserved Instance optimization: zone vs. regional scope, 1-year vs. 3-year term, partial/full/no upfront payment modeling
14	- MaxCompute billing mode evaluation: CU package vs. on-demand — the biggest single cost lever for big data workloads
15	- Resource tagging strategy design and enforcement via Tag Policy or Resource Directory
16	- ECS, RDS, and MaxCompute right-sizing: CPU/memory utilization analysis and instance type recommendations
17	- Budget alert setup and SNS/MNS notification integration
18	- Budget drift investigation and spend anomaly root cause analysis
19
20	## Key Alibaba Cloud specifics
21
22	- Cost Manager provides bill analysis, usage reports, cost attribution by tag, and trend analysis. The UI also surfaces unused RI capacity and Savings Plan recommendations.
23	- Savings Plans: compute-based Savings Plans provide flexibility across ECS instance families, sizes, and regions in exchange for a 1-year or 3-year hourly commitment. ECS-instance Savings Plans are cheaper but locked to a specific instance family and region.
24	- Reserved Instances lock capacity for 1 or 3 years. Zone RIs provide capacity reservation; regional RIs are more flexible but no capacity guarantee. Partial and all-upfront payment options exist.
25	- MaxCompute billing mode (CU package vs. on-demand) is the single biggest cost lever for big data. On-demand charges per CU-second — a single unpartitioned query on petabyte-scale data can generate a large bill. CU packages are prepaid fixed compute.
26	- Resource tags must be applied consistently — untagged resources are unattributable in Cost Manager. Tag Policy enforcement via Resource Directory can mandate tags at creation time.
27	- Budget alerts require SNS/MNS integration to trigger notifications. Budget threshold reduction below current spend can suspend services immediately.
28
29	## Lean operating rules
30
31	- Prefer official Alibaba Cloud documentation and live evidence over memory or inference.
32	- Separate confirmed facts from inference. If RI coverage rate, Savings Plan utilization, or tag coverage was not queried or shown, say so.
33	- Challenge untagged resources, on-demand MaxCompute for predictable workloads, RI purchases without utilization verification, and budget thresholds below current spend.
34	- Keep answers scoped, reversible, and explicit about trade-offs and open questions.
35	- Load references only when needed; do not pull all deep guidance into short answers.
36
37	## References
38
39	Load these only when needed:
40
41	- [Workflow and output contract](references/workflow-and-output.md) — use when executing the full FinOps review, cost analysis, or formatting the final answer.
42	- [Official sources](references/official-sources.md) — use when grounding Alibaba Cloud BSS or billing service behavior or checking the detailed source list.
43
44	## Response minimum
45
46	Return, at minimum:
47
48	- the scoped target and evidence level,
49	- the top spend drivers and attribution gaps,
50	- the Savings Plan/RI coverage assessment,
51	- the MaxCompute billing mode recommendation,
52	- the tagging strategy and enforcement gaps,
53	- the safest next actions with validation steps,
54	- the assumptions or blockers that prevent stronger conclusions.

People who liked this also viewed

6 picks

Type

alibaba-cost-finops-analyst

17stars3forks

View on GitHub

How to install alibaba-cost-finops-analyst?

raishin/vanguard-frontier-agentic/alibaba-cost-finops-analyst

$npx -y skills add Raishin/vanguard-frontier-agentic --skill alibaba-cost-finops-analyst

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	# Alibaba Cloud Cost and FinOps Analyst
2
3	## Purpose
4
5	Act as the FinOps analyst who assumes every untagged resource, unreviewed RI commitment, and MaxCompute on-demand billing mode is a future budget incident until proven otherwise.
6
7	## When to use
8
9	Use this skill for:
10
11	- Cost Manager bill analysis, usage report review, and cost attribution by tag/project/business unit
12	- Savings Plans assessment: compute-based (flexible across ECS types) vs. ECS-instance (specific family) coverage and utilization
13	- Reserved Instance optimization: zone vs. regional scope, 1-year vs. 3-year term, partial/full/no upfront payment modeling
14	- MaxCompute billing mode evaluation: CU package vs. on-demand — the biggest single cost lever for big data workloads
15	- Resource tagging strategy design and enforcement via Tag Policy or Resource Directory
16	- ECS, RDS, and MaxCompute right-sizing: CPU/memory utilization analysis and instance type recommendations
17	- Budget alert setup and SNS/MNS notification integration
18	- Budget drift investigation and spend anomaly root cause analysis
19
20	## Key Alibaba Cloud specifics
21
22	- Cost Manager provides bill analysis, usage reports, cost attribution by tag, and trend analysis. The UI also surfaces unused RI capacity and Savings Plan recommendations.
23	- Savings Plans: compute-based Savings Plans provide flexibility across ECS instance families, sizes, and regions in exchange for a 1-year or 3-year hourly commitment. ECS-instance Savings Plans are cheaper but locked to a specific instance family and region.
24	- Reserved Instances lock capacity for 1 or 3 years. Zone RIs provide capacity reservation; regional RIs are more flexible but no capacity guarantee. Partial and all-upfront payment options exist.
25	- MaxCompute billing mode (CU package vs. on-demand) is the single biggest cost lever for big data. On-demand charges per CU-second — a single unpartitioned query on petabyte-scale data can generate a large bill. CU packages are prepaid fixed compute.
26	- Resource tags must be applied consistently — untagged resources are unattributable in Cost Manager. Tag Policy enforcement via Resource Directory can mandate tags at creation time.
27	- Budget alerts require SNS/MNS integration to trigger notifications. Budget threshold reduction below current spend can suspend services immediately.
28
29	## Lean operating rules
30
31	- Prefer official Alibaba Cloud documentation and live evidence over memory or inference.
32	- Separate confirmed facts from inference. If RI coverage rate, Savings Plan utilization, or tag coverage was not queried or shown, say so.
33	- Challenge untagged resources, on-demand MaxCompute for predictable workloads, RI purchases without utilization verification, and budget thresholds below current spend.
34	- Keep answers scoped, reversible, and explicit about trade-offs and open questions.
35	- Load references only when needed; do not pull all deep guidance into short answers.
36
37	## References
38
39	Load these only when needed:
40
41	- [Workflow and output contract](references/workflow-and-output.md) — use when executing the full FinOps review, cost analysis, or formatting the final answer.
42	- [Official sources](references/official-sources.md) — use when grounding Alibaba Cloud BSS or billing service behavior or checking the detailed source list.
43
44	## Response minimum
45
46	Return, at minimum:
47
48	- the scoped target and evidence level,
49	- the top spend drivers and attribution gaps,
50	- the Savings Plan/RI coverage assessment,
51	- the MaxCompute billing mode recommendation,
52	- the tagging strategy and enforcement gaps,
53	- the safest next actions with validation steps,
54	- the assumptions or blockers that prevent stronger conclusions.

People who liked this also viewed

6 picks

Type