storage-cost-optimization

Automate object storage lifecycle rules and orphan cleanup across cloud providers.

Updated Mar 29, 2026

Search Tags:#monitoring #lifecycle #cost-optimization #storage #orphan-cleanup #per-tenant

Ready to run

npx skills add https://github.com/marquesfelip/agents-and-skills --skill storage-cost-optimization

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: storage-cost-optimization
Source: https://github.com/marquesfelip/agents-and-skills/tree/main/skills/storage-cost-optimization
Command: npx skills add https://github.com/marquesfelip/agents-and-skills --skill storage-cost-optimization

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Storage costs can spiral in SaaS platforms due to unoptimized object storage usage and manual lifecycle management.

Core Features & Use Cases

Design and apply object storage lifecycle rules across prefixes to transition data and expire old objects.
Identify and clean up orphaned storage objects by cross-referencing DB records.
Track per-tenant storage usage and trigger cost alerts to enforce budgets.
Provide a repeatable automation blueprint for implementing storage cost controls in production environments.

Quick Start

Define a basic lifecycle policy for your primary bucket and run an initial orphan cleanup in dry-run mode.

Frequently Asked Questions about storage-cost-optimization

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I automate object storage lifecycle rules to cut S3 and Azure Blob costs?▼

You can automate object storage lifecycle rules by defining prefix-based policies that transition data to Standard-IA or Glacier and expire old objects. This enforces automated storage cost controls across S3, GCS, and Azure Blob platforms.

What is the best way to clean up orphaned storage objects in a SaaS platform?▼

The best way to clean up orphaned storage objects is by cross-referencing your cloud storage buckets against database records. You can run an initial dry-run cleanup process to safely identify and delete unreferenced uploads, exports, or backups.

How does per-tenant storage usage tracking work for enforcing budget limits?▼

Per-tenant storage usage tracking works by monitoring individual tenant consumption across cloud prefixes and triggering cost alerts. This mechanism enforces predefined budget limits by notifying you when a tenant exceeds their allocated storage threshold.

Can I apply storage lifecycle transitions across different prefixes like uploads and logs?▼

Yes, you can apply storage lifecycle transitions across different prefixes. The system supports policy-driven transitions and expiration rules for uploads, exports, backups, and logs to automate data archival and deletion across your SaaS object storage.

When should I use policy-driven storage transitions instead of manual object deletion?▼

You should use policy-driven storage transitions when managing large-scale SaaS platforms with per-tenant storage usage. Automated lifecycle rules provide a repeatable blueprint for transitioning data to Standard-IA or Glacier, preventing spiraling costs better than manual deletion.

Do I need a database record to identify and remove orphan objects from my cloud storage?▼

Yes, you need a database record to cross-reference and identify orphan objects. The cleanup process validates existing storage objects against your database to safely determine which uploads, exports, or backups are unreferenced before deleting them.