「spend」の検索結果

Audit personal finance and budgeting app spending intelligence features. Triggers: you need to evaluate transaction categorization accuracy (MCC mapping, ML classification, merchant matching).

日本語の概要は準備中です。原文の説明を表示しています。

The art-route layer of the Forge skills. route_media.py is the one command that generates an image or an image-to-video clip - through the paid API of any provider whose key is configured (OpenAI, Google Gemini, xAI, BytePlus ModelArk, fal.ai; the configured key is the owner's consent), else through the user's own signed-in Codex or Grok CLI - and prints one JSON line with the route, artifact, sha256 and cost estimate; with no route it answers no-route (codeart2d is then the last resort). Also the capability check (forge_doctor), API key configuration, the spend ledger, resume and Codex image adoption. Use when a Forge skill sends a generation here, for the capability check, or when the user asks about keys, routes or spend. Not for planning, processing or QA of sprites, video frames or maps (generate2dsprite, video2dsprite, generate2dmap) or for code-drawn art (codeart2d).

日本語の概要は準備中です。原文の説明を表示しています。

Find every LLM workflow in the current repository and label it, so Caveman Cloud groups spend by what the code actually does (support-reply, nightly-digest) instead of one anonymous bucket. Use when the user pastes the Caveman discovery prompt, says "discover workflows", or asks to break LLM spend down by workflow. The repo should already route through the Caveman gateway (the caveman-setup skill does that part).

日本語の概要は準備中です。原文の説明を表示しています。

Use when Agentforce run costs are climbing, you need to forecast scale, or you want to reduce tokens per conversation without hurting quality. Covers topic (now subagent) design impact on cost, prompt/template reuse, grounding size discipline, caching, and model-tier selection. Triggers: 'agentforce cost', 'tokens per conversation too high', 'reduce agentforce runs spend', 'forecast agentforce scale cost', 'einstein trust layer tokens'. NOT for capping spend per user with a budget gate and fallback — use agentforce/agent-rate-limit-strategy. NOT for org-wide model-tier and BYOLLM platform strategy — use architect/ai-platform-architecture.

日本語の概要は準備中です。原文の説明を表示しています。

Track and report Claude Code token usage, spending, and budgets from a local cost-tracking database. Use when the user asks about costs, spending, usage, tokens, budgets, or cost breakdowns by project, tool, session, or date.

日本語の概要は準備中です。原文の説明を表示しています。

Audit your company's AI spending — find waste, measure ROI, and right-size your tool stack.

日本語の概要は準備中です。原文の説明を表示しています。

Product marketing and go-to-market strategy for B2B SaaS launches and positioning. Use this skill when planning a product launch, developing positioning and messaging, analyzing competitive landscape, building customer advocacy programs, designing a win/loss interview program, working out why we lose deals, designing GTM strategy, creating category positioning, planning analyst briefings, or deciding which country to expand into and how far to localize. Also use it for brand marketing and demand creation — how much to spend on brand versus performance, what to measure when a brand campaign produces no conversion event, and how to answer "we cannot attribute it". Also triggers on: positioning, product launch, competitive intelligence, messaging, customer advocacy, win/loss analysis, win/loss interviews, why we lose deals, closed-lost analysis, loss reason, close-reason field, competitive displacement, displace an incumbent, rip and replace, competitive takeout, switch from a competitor, win deals from a competitor, incumbent contract, renewal window, auto-renewal notice period, switching costs, EU Data Act, cloud switching rights, why do we lose to no decision, GTM, category design, analyst briefing, G2 review, international expansion, market entry, expand into Europe, which country should we launch in next, localization, translate our site, in-country go-to-market, regional GTM, is cold email legal in Germany, brand marketing, brand awareness, brand vs performance, brand versus demand gen, demand creation, demand capture, 95-5 rule, out of market buyers, category entry points, distinctive brand assets, mental availability, brand tracking, brand health, brand lift, share of search, how do we measure brand, justify brand spend, brand budget.

日本語の概要は準備中です。原文の説明を表示しています。

Full-funnel paid advertising operations for B2B SaaS. Use this skill for PPC strategy, Google Ads optimization, LinkedIn Ads, social media advertising, programmatic buying, creative strategy, attribution modeling, budget allocation, budget pacing and planned-vs-delivered reconciliation, audience overlap and campaign self-competition audits, suppression lists, ROAS improvement, media spend optimization, and the media no auction sells — newsletter and podcast sponsorships, community and industry-publication placements, paid review-site listings on G2 and Capterra, and pay-per-lead content syndication. Also triggers on: PPC, Google Ads, LinkedIn Ads, social ads, programmatic, ad creative, attribution, media budget, paid campaigns, ROAS, CPA, ad spend, newsletter sponsorship, podcast sponsorship, community sponsorship, sponsor a newsletter, content syndication, pay-per-lead, cost per lead vendor, media kit, rate card, insertion order, direct buy, publisher partnership, make-good, G2 paid listing, Capterra ads, review site advertising, sponsorship ROI, budget pacing, we underspent our budget, are our campaigns competing with each other, audience overlap, self-competition, campaign cannibalization, suppression list, exclusion list, ad frequency across channels, how many ad accounts do we have.

日本語の概要は準備中です。原文の説明を表示しています。

中断された組織を再開する。.state/org-state.md が存在し Status: SUSPENDED のとき、 「再開」「続きから」「前回どこまでやった？」と言われたときに使う。 起動時の自動ブリーフィングにも対応。

Busabase-backed App-in-Skill dashboard for a shared LLM gateway's cost and model governance — daily spend trend, cost breakdown by service/model, a canary-rollout status board, and a deterministic cost/error anomaly list. Use when the user invokes $kelly-llm-gateway or /kelly-llm-gateway, or wants to review LLM gateway spend, model routing, canary rollouts, rollback readiness, or cost/error anomalies for services routed through one shared gateway to multiple LLM providers/models. Human actions (promote/rollback/hold a rollout, acknowledge an anomaly) write directly onto the route's own Busabase record — this skill never changes a real routing config.

日本語の概要は準備中です。原文の説明を表示しています。

Investigate LLM spend in PostHog — total cost over time, cost by model, provider, user, trace, or custom dimension, token and cache-hit economics, and cost regressions. Use when the user asks "how much are we spending on LLMs?", "which model / user / feature is most expensive?", "why did cost spike?", wants to build a cost dashboard or alert, or pastes a trace URL and asks about its cost.

日本語の概要は準備中です。原文の説明を表示しています。

OpenAI API (developers.openai.com) の運用・管理リファレンス。 Administration API, admin API keys, RBAC, roles, groups, invites, projects, spend limits, audit logs, usage / costs API, Terraform provider (openai/openai), workload identity federation (WIF, OIDC/SPIFFE), safety best practices, moderation API, production best practices, deployment checklist, cost / latency optimization, fast mode, Realtime API costs。rate limits・error handling・prompt caching は openai-api-core、Codex のワークスペース 管理は openai-codex が担当。

Claude API (platform.claude.com) の組織管理・Admin API (sk-ant-admin) リファレンス。 users, invites, workspaces, API keys, service accounts, RBAC (groups / roles), Workload Identity Federation (WIF, federation issuers / rules), Usage & Cost API, rate limits / spend limits, Analytics API, Compliance API, CMEK, zero data retention (ZDR), data residency, inference hooks。

Fix the psychologically significant moment, not the logically significant metric — Rory Sutherland on experience. Use when the outcome is fine but the journey feels bad: complaints about waiting, anxiety, uncertainty, or 'it's technically fast/cheap/correct but people still hate it'; when the user asks 'how do we reduce complaints', 'how do we make waiting/onboarding/checkout feel better', 'people are anxious during X', or is about to spend big to shave a number (wait time, load time, steps) when the real pain is how the moment feels. Covers uncertainty reduction, idle vs occupied waiting, and the peak-end rule. Inspired by Rory Sutherland's *Alchemy*. Routed to from psycho-logic. 日本語の相談（「待ち時間のクレームが多い」「手続きの途中で離脱される」「お客様を不安にさせている」）にも使う。中文咨询（“等待时间投诉多”“办理中途流失”“让客户感到不安”）也适用。

Bulk mode — maximum development speed by spending tokens aggressively on massive parallel sub-agents and multi-agent workflows, while the orchestrator context stays lean (pairs with /slim). Invoking /bulk is the user's explicit opt-in to Workflow/ultracode-style orchestration for this session. Use when the user types /bulk, asks for "爆速", "並列で大量に", "ultracode", "多エージェント", or hands over a big task where wall-clock speed matters more than token cost.

Preregister a paid eval (bars, arms, decoys, stop rules), dry-run it at zero cost, then run a three-item priced pilot whose spend table gates approval. (gstack)

日本語の概要は準備中です。原文の説明を表示しています。

Read-only review of Caveman Cloud evidence: cost, Cave Score, workflows, traces, latency, errors, routing, savings. Use when asked what Caveman found or where LLM spend goes.

日本語の概要は準備中です。原文の説明を表示しています。

Wire a repository through the Caveman Cloud gateway so every LLM request is measured, with no behavior change. Use for "set up caveman" or adding LLM spend observability.

日本語の概要は準備中です。原文の説明を表示しています。

Believable agent cost report for any period, default the last 7 full days PT, not counting today. Measured tokens from Claude Code transcripts priced at OpenRouter list prices (ESTIMATED), measured provider spend when a sanctioned source exists, note-taker cost separate, Timing-style HTML/PDF plus report.json, line-items.csv, evidence.json.

日本語の概要は準備中です。原文の説明を表示しています。

View cost breakdowns, token usage, and call logs from the CLI. Filter by provider, model, or date range. Export usage reports and inspect per-connection spending.

日本語の概要は準備中です。原文の説明を表示しています。

Create, list, rotate, and revoke OmniRoute API keys. Control per-key scopes, spending limits, and expiration. Keys gate access to all proxy and management endpoints.

日本語の概要は準備中です。原文の説明を表示しています。

Configure spending limits, token quotas, and rate-limit policies per API key or globally. Inspect current consumption and enforce cost controls across providers.

日本語の概要は準備中です。原文の説明を表示しています。

Run a GEPA learning cycle via `metaharness learn` (upstream ADR-235, metaharness@0.3.0) — optimizes a harness genome against a SWE-bench-style slice manifest. $0 dry-run by default; `--run` is the explicit spend opt-in. Requires a metaharness repo checkout (`--repo` or $METAHARNESS_REPO) — without one it reports `checkout-required` with clone instructions. Degrades gracefully when metaharness is absent.

日本語の概要は準備中です。原文の説明を表示しています。

OpenRouter real spend — key limit and usage today/week/month, one request's billed cost by generation id, account credits. Use when asked what OpenRouter charged or whether a key is near its limit. Network and API key: asks first.

日本語の概要は準備中です。原文の説明を表示しています。