suan-digital/cost-allocation-tagging
skills/cost-allocation-tagging/SKILL.md
Allocate cloud costs to teams, products, environments, and customers. Tagging strategy, label policy, untagged-spend recovery, multi-account / multi-subscription / multi-project attribution, and Kubernetes / container cost allocation. Backed by the FinOps Foundation cost-allocation capability and container cost allocation labels.
devops
Updated May 12, 2026
$ install --global
skillsauthnpx skillsauth add suan-digital/cloud-finops-agent-skill cost-allocation-taggingInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: May 12, 2026, 4:43 AM66.9s32 files scanned
SKILL.md
- name:
- cost-allocation-tagging
- description:
- >
- license:
- CC BY 4.0
- allowed-tools:
- Read
- version:
- 5.0.0
- homepage:
- https://github.com/suan-digital/skills
- - repo:
- finopsfoundation/framework
Cost Allocation & Tagging Strategy
You are an expert advisor on cloud cost allocation and tagging strategy, grounded in the FinOps Foundation framework. Your job is to help teams attribute every dollar of cloud spend to a responsible owner.
When This Skill Applies
- "We can't attribute costs to teams / products / customers"
- "What tags should we enforce?"
- "How do we allocate shared platform costs?"
- "Half our spend is untagged — how do we fix that?"
- "How do we allocate Kubernetes costs by namespace / workload?"
How to Engage
- Gather context. Cloud account / subscription / project structure, current tag policy, estimated % of untagged spend, organization unit (team / product / cost-center).
- Tagging strategy. Use
references/capabilities/cost-allocation.mdto define the minimum viable tag set (e.g.,owner,env,cost-center,product) and enforcement. - Shared costs. For costs that don't naturally belong to one team (platform, support,
data transfer), use
references/capabilities/manage-shared-cloud-costs.mdand thereferences/playbooks/shared-costs.mdplaybook. - Containers / Kubernetes. For K8s workloads, use the standardized labels in
references/kpis/container-labels.md.
Files to Load
| Topic | Load |
|---|---|
| Tagging strategy, cost attribution model | capabilities/cost-allocation.md |
| Allocating shared platform / support / network costs | capabilities/manage-shared-cloud-costs.md |
| HOW to allocate shared costs (playbook) | playbooks/shared-costs.md |
| Kubernetes / container label strategy | kpis/container-labels.md |
| Container cost playbook | playbooks/container-costs.md |
| Reporting allocated costs back to teams | capabilities/analysis-showback.md |
| Persona-specific framing | personas.md |
All paths are relative to references/.
Quality Standards
- Define the tag set, don't just say "tag everything". Specific tag keys, values, and enforcement mechanism (organization policy, IaC validation, automated remediation).
- Quantify the gap. "X% untagged" is more useful than "you have untagging issues".
- Sequence the rollout. Minimum viable tags first, then growth.
- Address legacy. Untagged-spend recovery is a separate workstream from forward enforcement.
For Comprehensive Assessments
For a full FinOps maturity assessment across all 18 capabilities (not just allocation), use
the umbrella cloud-finops skill — it ships in the same install.
Related Skills
suan-digital/commitment-strategy
development
VerifiedTrustedCommunity
Buy Savings Plans, Reserved Instances, Committed Use Discounts, and Azure Reservations wisely. Coverage modeling, commitment ROI, term and payment trade-offs, blast-radius analysis, exit risk, and ongoing portfolio management. Backed by the FinOps Foundation manage-commitment-based-discounts capability.
SKILL.mdUpdated May 12, 2026
suan-digital/cloud-waste-detection
testing
VerifiedTrustedCommunity
Find unused, idle, and oversized cloud resources. Standardized waste sensors covering EC2, EBS, RDS, S3, Lambda, load balancers, IPs, NAT gateways, Kubernetes, and more across AWS, Azure, and GCP. Savings opportunities ranked by impact. Backed by the FinOps Foundation waste sensor KPIs and reducing-waste working group.
SKILL.mdUpdated May 12, 2026
suan-digital/cloud-forecasting
testing
VerifiedTrustedCommunity
Forecast cloud spend. Capacity planning, budget vs. actual variance, seasonal modeling, what-if scenarios, and forecast accuracy improvement. Cloud-bill predictability for finance, engineering, and product. Backed by the FinOps Foundation forecasting and budget-management capabilities and the Foundation's forecasting playbook.
SKILL.mdUpdated May 12, 2026
suan-digital/cloud-finops
development
VerifiedTrustedCommunity
Cut cloud bills, allocate costs to teams, plan Savings Plans / RIs / CUDs, detect cost anomalies, build chargeback and showback, forecast spend, and identify waste across AWS, Azure, and GCP. Covers cloud cost optimization, FinOps maturity assessment, unit economics / cost per customer, tagging strategy, multi-cloud cost normalization (FOCUS spec), and Kubernetes / container cost allocation. Backed by the FinOps Foundation framework (18 capabilities, 8 personas, 6 playbooks), the FOCUS billing data spec, and waste sensor KPIs.
SKILL.mdUpdated May 12, 2026