be-cost-monitoring
Monitor and analyze backend GPU costs for LTX API and LTX Studio. Use when analyzing cost trends, detecting anomalies, breaking down costs by endpoint/model/org/process, monitoring utilization, or investigating cost efficiency drift.
npx skills add majiayu000/claude-skill-registry --skill be-cost --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Backend Cost Monitoring ## When to use - "Monitor GPU costs" - "Analyze cost trends (daily/weekly/monthly)" - "Detect cost anomalies or spikes" - "Break down API costs by endpoint/model/org" - "Break down Studio costs by process/workspace" - "Compare API vs Studio cost distribution" - "Investigate cost-per-request efficiency drift" - "Monitor GPU utilization and idle costs" - "Alert on cost budget breaches" - "Day-over-day or week-over-week cost comparisons" ## Steps ### 1. Gather Requirements Ask the user: - **What to monitor**: Total costs, cost by product/feature, cost efficiency, utilization, anomalies - **Scope**: LTX API, LTX Studio, or both? Specific endpoint/org/process? - **Time window**: Daily, weekly, monthly? How far back? - **Analysis type**: Trends, comparisons (DoD/WoW), anomaly detection, breakdowns - **Alert threshold** (if setting up alerts): Absolute ($X/day) or relative (spike > X% vs baseline) ### 2. Read Shared Knowledge Before writing SQL: - **`shared/product-context.md`** — LTX products and business context - **`shared/bq-schema.md`** — GPU cost table schema (lines 418-615) - **`shared/metric-standards.md`** — GPU cost metric patterns (section 13) - **`sha
- When to use
- Steps
- 1. Gather Requirements
- 2. Read Shared Knowledge
- 3. Run Query Templates
- 4. Execute Query
- 5. Analyze Results
- 6. Present Findings
- 7. Set Up Alert (if requested)
- Schema Reference
- Reference Files
- Rules
- Query Best Practices
- Cost Calculation
bq --project_id=ltx-dwh-explore query --use_legacy_sql=false --format=pretty "
What does the be-cost-monitoring skill do?
Monitor and analyze backend GPU costs for LTX API and LTX Studio. Use when analyzing cost trends, detecting anomalies, breaking down costs by endpoint/model/org/process, monitoring utilization, or investigating cost efficiency drift.
How do I install it?
Run `npx skills add majiayu000/claude-skill-registry --skill be-cost --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.