thesoftwarehouse/tsh-optimizing-cloud-cost
.github/skills/tsh-optimizing-cloud-cost/SKILL.md
Optimize cloud costs through resource rightsizing, tagging strategies, reserved instances, and spending analysis. Use when reducing cloud expenses, analyzing infrastructure costs, or implementing cost governance policies.
$ install --global
skillsauthnpx skillsauth add thesoftwarehouse/copilot-collections tsh-optimizing-cloud-costInstall 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: Apr 15, 2026, 11:58 PM9.3s2 files scanned
SKILL.md
- name:
- tsh-optimizing-cloud-cost
- description:
- Optimize cloud costs through resource rightsizing, tagging strategies, reserved instances, and spending analysis. Use when reducing cloud expenses, analyzing infrastructure costs, or implementing cost governance policies.
Cloud Cost Optimization
When to Use
- Reducing cloud spending or meeting budget constraints
- Right-sizing resources based on utilization
- Implementing cost governance and tagging
- Analyzing multi-cloud cost optimization opportunities
Pricing Model Decision
| Workload Type | AWS | Azure | GCP | Savings | |---------------|-----|-------|-----|---------| | Steady-state (24/7) | Reserved Instances / Savings Plans | Reserved VMs | Committed Use | 30-72% | | Variable / burst | On-Demand + Auto-scaling | Pay-as-you-go | On-Demand | Baseline | | Fault-tolerant batch | Spot Instances | Spot VMs | Preemptible | Up to 90% | | Serverless / event-driven | Lambda | Functions | Cloud Functions | Pay-per-use |
Storage Tiering Decision
| Data Access Pattern | AWS | Azure | GCP | |---------------------|-----|-------|-----| | Frequent (hot) | S3 Standard | Hot | Standard | | Infrequent (30+ days) | S3 Standard-IA | Cool | Nearline | | Rare (90+ days) | S3 Glacier | Cold | Coldline | | Archive (365+ days) | S3 Deep Archive | Archive | Archive |
Rule: Implement lifecycle policies to auto-transition data between tiers.
Required Tags
| Tag | Purpose | Example |
|-----|---------|---------|
| Environment | Cost allocation by env | production, staging |
| Project | Cost allocation by project | my-project |
| CostCenter | Finance reporting | engineering |
| Owner | Contact for unused resources | [email protected] |
| ManagedBy | Track IaC vs manual | terraform |
Reference: See references/tagging-standards.md for full standards.
Process
- Audit current spend → Use Cost Explorer / Cost Management to identify top costs
- Tag all resources → Apply required tags for cost allocation
- Identify waste → Find unused EBS, EIPs, snapshots, idle instances
- Right-size resources → Use Compute Optimizer / Advisor recommendations
- Apply pricing models → Reserved/Committed for steady, Spot for batch
- Implement tiering → Storage lifecycle policies, database right-sizing
- Set up alerts → Budget alerts at 50%, 80%, 100% thresholds
- Schedule reviews → Weekly cost review, monthly optimization
Checklist
- [ ] Cost allocation tags applied to all resources
- [ ] Unused resources deleted (EBS, EIPs, snapshots, idle instances)
- [ ] Instances right-sized based on utilization metrics
- [ ] Reserved capacity purchased for steady workloads (>70% utilization)
- [ ] Spot/preemptible used for fault-tolerant workloads
- [ ] Storage lifecycle policies configured
- [ ] Budget alerts enabled (50%, 80%, 100%)
- [ ] Cost anomaly detection enabled
- [ ] Auto-scaling configured for variable workloads
Anti-Patterns
| ❌ Don't | ✅ Do | |----------|-------| | Over-provision "just in case" | Right-size based on metrics, scale up if needed | | Use On-Demand for steady workloads | Use Reserved/Committed for predictable usage | | Store all data in hot tier | Implement lifecycle policies | | Skip tagging | Tag everything for cost visibility | | Review costs monthly | Review weekly, alert on anomalies |
Tools
| Provider | Tools | |----------|-------| | AWS | Cost Explorer, Cost Anomaly Detection, Compute Optimizer | | Azure | Cost Management, Advisor | | GCP | Cost Management, Recommender | | Multi-cloud | CloudHealth, Cloudability, Kubecost |
Reference Files
references/tagging-standards.md- Tagging conventions and enforcement
Related Skills
tsh-implementing-terraform-modules- For resource provisioningtsh-designing-multi-cloud-architecture- For cloud selection
Related Skills
thesoftwarehouse/tsh-writing-hooks
development
VerifiedTrustedCommunity
Custom hook and composable patterns — naming, composition, stable return shapes, lifecycle cleanup, and testing strategies. Use when writing reusable logic units (React hooks, Vue composables), refactoring logic into hooks, debugging hook behavior, or reviewing hook implementations.
206SKILL.mdUpdated Apr 15, 2026
thesoftwarehouse/tsh-ui-verifying
testing
VerifiedTrustedCommunity
UI verification criteria, structure checklists, severity definitions, and tolerance rules for comparing implementations against Figma designs. Use for verifying UI matches design, understanding what to check, and determining acceptable differences.
206SKILL.mdUpdated Apr 15, 2026
thesoftwarehouse/tsh-transcript-processing
development
VerifiedTrustedCommunity
Clean raw workshop or meeting transcripts from small talk, filler words, and off-topic tangents. Extract and structure business-relevant content into a standardized format with discussion topics, key decisions, action items, and open questions.
206SKILL.mdUpdated Apr 15, 2026
thesoftwarehouse/tsh-technical-context-discovering
development
VerifiedTrustedCommunity
Discover and establish technical context before implementing any feature. Prioritize project instructions, existing codebase patterns, and external documentation in that order. Use for any task requiring understanding of project conventions, coding standards, architecture patterns, and established practices before writing code.
206SKILL.mdUpdated Apr 15, 2026