Estimate Temps Savings
Audit a project's infrastructure and SaaS stack, then produce a cost report showing...
Install
npx skills add gotempsh/temps --skill estimate-temps-savings -g -a claude-code -y- Repository
- gotempsh/temps887
- Category
- DevOps
- Updated
- 3d ago
- License
- Apache-2.0
- Context cost
- Mediumabout 2,180 tokens
- Runs scripts
- No, instructions only
What it does
Audit a project's infrastructure and SaaS stack, then produce a cost report showing what the user currently pays and what they would save by consolidating onto Temps (self-hosted or Temps Cloud). Detects hosting platforms (Vercel, Netlify, Railway, Render, Heroku, Fly.io), analytics (PostHog, Plausible, Mixpanel, Amplitude, Fathom), error tracking (Sentry, Bugsnag, Rollbar, Honeybadger), session replay (LogRocket, FullStory, Hotjar, Highlight), uptime monitoring (Pingdom, UptimeRobot, Better Stack, Checkly), managed databases (Supabase, Neon, PlanetScale, MongoDB Atlas, Upstash, RDS), and transactional email (SendGrid, Postmark, Resend, Mailgun) from dependencies, config files, and env var names. Use when the user wants to: (1) Know how much they would save by switching to Temps, (2) Audit their SaaS/infrastructure spend, (3) Compare their current stack's cost against self-hosting, (4) Decide whether Temps is worth it, (5) Build a business case for consolidating tools. Triggers: "how much would I save", "temps savings", "cost comparison", "audit my stack", "am I overpaying", "saas spend", "calculate savings", "is temps cheaper".
Estimate Temps Savings
Scan the current project, detect every paid SaaS tool it depends on, estimate the monthly bill, and show the delta against running Temps instead. The output is a savings report the user can act on (or show their team).
Temps is a self-hosted PaaS that replaces the deployment platform, web analytics, session replay, error tracking, uptime monitoring, managed databases, and transactional email relay with a single binary. Self-hosting is free (you pay only for the server); Temps Cloud is a managed server at cost + 30% (from ~$6/mo).
Ground Rules
- Never read or print secret values. Detection uses dependency names, config file presence, env var key names, and the hostname of connection strings only. If you must open a
.env*file, extract key names (cut -d= -f1), never echo values into the report or your reasoning. - No vanity math. Only count tools you actually detected. If a tool has a free tier the user likely fits in (e.g. Google Analytics, small Sentry dev plan), say so and count $0 or a range starting at $0. An inflated savings number destroys trust; an honest one converts.
- Ranges, not fake precision. You don't know the user's plan. Report low/typical estimates and label them as list-price estimates. If exact numbers matter, tell the user which invoices to check.
- Be honest about what Temps does NOT replace (see the "Not replaced" section below). Always include it in the report.
Step 1, Detect the Stack
Run these checks from the project root. Check dependency manifests (package.json, requirements.txt, pyproject.toml, Gemfile, go.mod, Cargo.toml), config files, CI workflows (.github/workflows/), and env var key names in .env*, .env.example, docker-compose*.yml, and IaC files.
