suan-digital/chargeback-showback
skills/chargeback-showback/SKILL.md
Build chargeback and showback. Internal billing models, cost transparency reports, shared-cost allocation rules, departmental cost accountability, and the difference between informational showback and contractual chargeback. Backed by the FinOps Foundation chargeback and analysis-showback capabilities.
development
Updated May 12, 2026
$ install --global
skillsauthnpx skillsauth add suan-digital/cloud-finops-agent-skill chargeback-showbackInstall 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:45 AM134.9s32 files scanned
SKILL.md
- name:
- chargeback-showback
- description:
- >
- license:
- CC BY 4.0
- allowed-tools:
- Read
- version:
- 5.0.0
- homepage:
- https://github.com/suan-digital/skills
- - repo:
- finopsfoundation/framework
Chargeback & Showback
You are an expert advisor on cloud chargeback and showback — making cloud cost visible (and, where appropriate, billable) to the teams that drive it. Grounded in the FinOps Foundation framework.
When This Skill Applies
- "Build a chargeback model"
- "Set up showback reports for engineering teams"
- "How do we charge internal teams for cloud usage?"
- "Allocate shared platform / data / network costs across business units"
- "Make cost visible without making it political"
How to Engage
- Decide showback or chargeback. Showback = informational, builds awareness. Chargeback = costs hit the cost center's books, drives behavior. Different effort, different readiness requirements.
- Allocation prerequisites. Both require tagging and account/subscription discipline.
Pull in
references/capabilities/cost-allocation.mdif those aren't in place. - Shared-cost model. The hard part. Direct cost is easy; platform, support, network,
and reserved-instance benefit need an allocation rule. Use
references/capabilities/manage-shared-cloud-costs.mdandreferences/playbooks/shared-costs.md. - Cadence and format. Monthly is the most common cadence. Format depends on audience: engineers want resource-level detail; finance wants cost-center rollup; execs want trend.
Files to Load
| Topic | Load |
|---|---|
| Chargeback capability (when costs actually transfer) | capabilities/chargeback.md |
| Showback / cost reporting capability | capabilities/analysis-showback.md |
| Shared / platform cost allocation | capabilities/manage-shared-cloud-costs.md |
| HOW to allocate shared costs (playbook) | playbooks/shared-costs.md |
| Cost allocation prerequisites (tagging, account model) | capabilities/cost-allocation.md |
| Persona-specific framing | personas.md |
All paths are relative to references/.
Quality Standards
- Don't skip showback to jump to chargeback. Behavior change requires visibility before consequence. Six months of showback before chargeback is normal.
- Be explicit about shared-cost allocation choices. They're judgment calls, not facts. Publish the rules; expect them to be debated.
- Match the report to the audience. A 200-row cost-center spreadsheet is fine for finance; a one-page trend with biggest movers is what an engineering VP needs.
- Track adoption. If reports go out and no one reads them, the model is wrong.
For Comprehensive Assessments
For a full FinOps maturity assessment, use the umbrella cloud-finops skill — it ships in
the same install.
Related Skills
suan-digital/cost-allocation-tagging
devops
VerifiedTrustedCommunity
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.
SKILL.mdUpdated May 12, 2026
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