Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →gotempsh/estimate-temps-savings
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 Sta
Passed 11 of 18 test cases with the skill, and 7 of 18 without it.
and 6 more in the full report
7 fixed7 passed either way7 still failing1 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 7 test cases the skill fixed. Same model, same prompt, with and without the skill.
We detected PostHog, Vercel, and Supabase in our repo. We do not know our exact pageviews or seat count right now, so ask us what you need to price this stack.
| Checked | Without skill | With skill |
|---|---|---|
| Asks usage questions in a single batched prompt. | Passed | Passed |
| Applies explicit default metric values when usage data is unknown. | Missed | Passed |
The instructions your model reads when the skill loads.
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).
.env* file, extract key names (cut -d= -f1) — never echo values into the report or your reasoning.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.
| Category | Signal → Tool |
|---|---|
| Hosting | vercel.json or .vercel/ → Vercel · netlify.toml → Netlify · railway.json/railway.toml → Railway · render.yaml → Render · fly.toml → Fly.io · Procfile + no Dockerfile → Heroku · amplify.yml → AWS Amplify |
| Analytics | posthog-js/posthog-node → PostHog · plausible-tracker or plausible.io script tag → Plausible · mixpanel-browser → Mixpanel · @amplitude/* → Amplitude · fathom-client → Fathom · @segment/analytics-* → Segment · @vercel/analytics → Vercel Analytics |
| Error tracking | @sentry/*, sentry.properties, sentry-sdk → Sentry · @bugsnag/* → Bugsnag · rollbar → Rollbar · @honeybadger-io/* → Honeybadger |
| Session replay | logrocket → LogRocket · @fullstory/browser → FullStory · Hotjar script tag / HOTJAR_ID → Hotjar · @highlight-run/* → Highlight · PostHog with session_recording config → PostHog Replay |
| Uptime / status | checkly.config.ts → Checkly · env keys or CI mentioning Pingdom / UptimeRobot / Better Stack (BetterUptime) / Statuspage |
| Managed DB / cache | @supabase/supabase-js or supabase.co host → Supabase · @neondatabase/serverless or neon.tech host → Neon · @planetscale/database or psdb.cloud host → PlanetScale · mongodb+srv:// or mongodb.net host → MongoDB Atlas · @upstash/redis or upstash.io host → Upstash · rds.amazonaws.com host → AWS RDS · redns.redis-cloud.com host → Redis Cloud |
| Transactional email | @sendgrid/mail / SENDGRID_API_KEY → SendGrid · postmark / POSTMARK_SERVER_TOKEN → Postmark · resend / RESEND_API_KEY → Resend · mailgun.js / MAILGUN_API_KEY → Mailgun · email-smtp.*.amazonaws.com → AWS SES (already cheap — flag, don't count) |
| Observability (partial) | DD_API_KEY/datadog → Datadog · NEW_RELIC_LICENSE_KEY → New Relic (Temps covers logs/metrics/traces basics — count partially, note the caveat) |
Env key names worth grepping for: SENTRY_DSN, NEXT_PUBLIC_POSTHOG_KEY, MIXPANEL_TOKEN, AMPLITUDE_API_KEY, SEGMENT_WRITE_KEY, LOGROCKET_APP_ID, DATABASE_URL, REDIS_URL, MONGODB_URI, UPSTASH_REDIS_REST_URL, VERCEL_TOKEN, NETLIFY_AUTH_TOKEN, RAILWAY_TOKEN, FLY_API_TOKEN.
Multi-repo note: if the user says this is one of several apps, ask how many apps/environments share these tools — per-seat and per-project pricing multiplies.
Ask ONLY about categories you detected, in one batch. Every question needs a default so the user can answer "don't know":
test cases passed, vs 7 / 18 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.