505건 · 관련도순
Govern Alchemy compute usage and spend with current account evidence, workload attribution, budgets, and reversible optimizations. Use when forecasting or reducing Alchemy cost. Trigger with "Alchemy cost", "Alchemy compute units", or "reduce Alchemy spend".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Reduce Adobe integration spend using contract, invoice, usage, queue, storage, and retry evidence instead of invented per-call prices. Use when the task requires adobe workload cost and waste review. Trigger with "reduce Adobe cost", "Adobe spend review", or "PDF transaction budget".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Buys well — specifying need, running competitive sourcing, negotiating, and category strategy before a contract exists. Use this to run an RFP or vendor selection, negotiate a purchase, consolidate spend across a category, decide between single and multiple suppliers, or bring uncontrolled spending under management.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
The CIO's remit — running the technology the company works on, service quality, IT spend, and the boundary with product engineering. Use this to set IT priorities, decide what IT owns versus engineering, structure IT spend or an IT roadmap, judge whether to build, buy or outsource, or work out why IT is seen as a cost center rather than an enabler.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Für Sperrung Suspendierung: ordnet Norm, Beweislast und Gegenargument; Ergebnis: Prüfprodukt mit Risiko und nächstem Schritt.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Forecast Azure spend and price planned resources or workloads. WHEN: "forecast Azure spending", "project next month cost", "compare forecast to my planning target", "how much will Azure cost", "estimate VM cost", "compare storage tiers", "compare Azure regions", "retail price", "EA rate card", "negotiated pricesheet". DO NOT USE FOR: configured budget health or alerts, bill analysis, cost spikes, rightsizing, or commitments.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Produce a structured budget variance analysis from actual vs budget figures. Use when asked to analyse budget variances, explain underspend or overspend, write a variance commentary, or investigate why actuals differ from plan. Produces a categorised variance table with root cause analysis and management commentary.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Audit whether the organisation's AI spend actually paid — measured against baselines, not vendor math or vibes. Use when a CFO asks what the AI tools returned, when renewing AI contracts, when consolidating overlapping AI subscriptions, or to build the measurement plan before the next spend. Produces an ROI audit with per-tool verdicts (keep/consolidate/cut), the honest-measurement method behind each number, and a baseline plan for whatever can't be scored yet. To forecast ROI before an investment use roi-estimator; this skill measures what already happened.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Analyze prompt-cache effectiveness for Claude Code usage from the Agent Monitor dashboard — cache hit rate (total_cache_read / (total_cache_read + total_input)), cache_write vs cache_read reuse, cache-read vs cache-write spend, and the sessions with the poorest reuse. Pulls token totals from /api/analytics, per-session detail from /api/sessions, and dollar splits from /api/pricing/cost. Use when diagnosing cache spend or deciding whether prompt caching is paying off.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when administering a Scenario team from an agent through MCP: restricting which models a team or project can run (model access control, allowlist, blocklist), inviting or removing team and project members, changing roles, capping a member's Creative Unit spend, creating or deleting projects, auditing API keys and their roles or scopes, or attributing consumption per user or model. Keywords: governance, model control, consumption cap, spend limit, API key hygiene, team admin, enterprise.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Build, run, debug, and operate applications on AWS Lambda MicroVMs — Firecracker-isolated, snapshot-resumable serverless compute environments that run inside a container with up to 8-hour lifetimes. Triggers on: Lambda MicroVMs, Firecracker isolation, snapshot-resumable compute, suspend/resume, sandboxed or untrusted code execution, AI/agent code-execution sandboxes, interactive code playgrounds and notebooks (Jupyter, REPLs), reinforcement-learning environments, multi-tenant CI executors and build runners, sessionful game or simulation servers, isolated security scanners, long-lived sessions, or port-listening servers (gRPC, WebSocket, custom TCP). For standard event-driven Lambda functions, use the aws-lambda skill instead.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Project ad budget pacing by script from live accounts or given numbers: month-end overspend. "are we overspending this month"
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Pull Google Ads performance data and generate reports. Use when asked about ad campaign performance, keyword costs, quality scores, ROAS, conversion tracking, or ad spend analysis. Trigger phrases: "google ads", "adwords", "campaign performance", "ad spend", "quality score", "CPC report", "ROAS", "ad conversion", "keyword performance", "google ads report".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Weekly. Audits the paid and measurement setup the member already has by reading it, then assembles the parts that are missing as local files: campaign structure, ad copy, negative keyword seeds, and conversion tracking specifications, each one complete and ready to paste. It creates nothing in an account, saves nothing, activates nothing, and spends nothing, unless you released the channel. This is where the spend stop lives.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when the user needs an overall marketing plan for a period — objectives, segments, positioning, channel mix, content direction, budget, timeline, KPIs, and a risk matrix, adapted to US, EU, SEA, or LATAM. Trigger on 'marketing plan', 'marketing strategy for next year', 'go-to-market roadmap', 'plan for Q3', 'we have no marketing plan', 'where should we spend next quarter'. Also use when a founder only says the business needs to grow and has no idea which channel to start with. Not for — one specific campaign, see `02-campaign-brief-global`; working backward from a revenue goal to spend, see `10-reverse-kpi-global`; splitting a budget across channels and months, see `61-budget-planning-global`; taking a brand new product to market, see `59-go-to-market-global`.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when a PAID MEDIA plan is needed — work backward from revenue to max CPA and required budget, split spend across channels, funnel stages, and campaign types, build a ramp-up timeline, set KPI targets per channel, and prepare a contingency plan. Trigger on 'media plan', 'paid media budget', 'how much should I spend on ads', 'channel mix for the campaign', 'plan the ad budget', 'we have 10k a month and no plan'. Also use when a budget number exists and nobody has decided where it goes. Not for — the pure revenue-to-budget math, see `10-reverse-kpi-global`; the whole marketing budget including non-paid, see `61-budget-planning-global`; the next period plan built from results, see `57-next-ads-plan-global`.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Systematic analysis of Google Ads and Meta advertising spend to identify wasted budget. Produces actionable exclusion lists with thematic categorization and statistical validation. Use when onboarding new accounts, performing monthly hygiene, or preparing for budget optimization.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Design or review annual operating budget — headcount plan, departmental spending, revenue targets, and variance tracking. Use when asked to "build our budget", "plan headcount for next year", or "review our spending".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Audit AI spend — per-model cost breakdown, top consumers, waste identification, optimization levers. Use when asked "why is our AI bill so high", "audit LLM spend", or "where is our token waste".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Expert FinOps guidance for cloud, AI, and SaaS technology spend. Covers AI cost management, agentic FinOps, GenAI capacity planning, self-hosted vs managed inference, Anthropic billing, open-weight vendor APIs (DeepSeek, Qwen, Kimi, GLM), AWS (EC2, Bedrock, SageMaker, Savings Plans, CUR), Azure (reservations, AHB, OpenAI PTUs), GCP (Vertex AI, BigQuery), OCI, on-prem and hybrid, Kubernetes cost allocation, data platforms (Databricks, Fabric F-SKUs, Snowflake), tagging governance, SaaS management (SAM, shadow IT), AI coding tools (Cursor, Claude Code, Copilot, Codex), ITAM, allocation, showback, chargeback, anomaly management, KPIs and benchmarking, forecasting, waste detection playbooks, workload onboarding and M&A, and GreenOps (cloud carbon, CSRD). Use for any technology cost or waste question in your estate - expiring commitments or RIs, NAT gateway bills, idle VMs, snapshot sprawl - and for commitment sizing, rightsizing, or connecting spend to business value. Built by OptimNow.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Run CodeBurn locally or as an MCP server so agents can inspect token usage, cost, model mix, project spend, and budget waste across coding tools.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
"Calculate and analyze Customer Acquisition Cost (CAC) and Customer Lifetime Value (LTV) to evaluate unit economics and marketing efficiency. Use this skill when the user needs to assess whether their customer acquisition is profitable, optimize marketing spend allocation, or evaluate business model viability — even if they say 'are we spending too much on ads', 'what's each customer worth', or 'is our growth sustainable'.".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
"Optimize advertising budget allocation across campaigns using marginal returns analysis. Use this skill when the user needs to distribute budget across multiple campaigns, optimize spend pacing, or maximize overall ROAS under budget constraints — even if they say 'how to split my ad budget', 'campaign budget optimization', or 'diminishing returns on ad spend'.".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.