ai-operating-economics
Use when deciding whether an AI-enabled workflow should be adopted, scaled, constrained, redesigned, or retired, and the decision must connect business outcomes, worker or user effects, quality guardrails, full operating cost, telemetry, uncertainty, and accountable governance. Do not use for a standalone financial model, infrastructure cost calculation, agent evaluation design, runtime operations, or general AI governance; route those details to the neighboring specialist skills.
magnus919 · Static checks on file
Installation
Read the source and dependencies before running a command. Copying does not install or execute anything.
npx skills add magnus919/agent-skills --skill ai-operating-economicsAbout this skill
name: ai-operating-economics description: >- Use when deciding whether an AI-enabled workflow should be adopted, scaled, constrained, redesigned, or retired, and the decision must connect business outcomes, worker or user effects, quality guardrails, full operating cost, telemetry, uncertainty, and accountable governance. Do not use for a standalone financial model, infrastructure cost calculation, agent evaluation design, runtime operations, or general AI governance; route those details to the neighboring specialist skills. license: MIT compatibility: Agent-agnostic methodology; no runtime dependency. metadata: tags: ai-economics, value-realization, ai-adoption, outcome-measurement, cost-attribution, worker-impact, evidence-led-decisions source: "Synthesized from primary and independent sources listed in references/source-index.md"
AI Operating Economics
Overview
AI initiatives are operating interventions, not merely model purchases or ROI spreadsheets. Their value depends on what work changes, who benefits, what quality or risk changes with it, what the complete intervention costs, and whether the organization can observe and govern those changes.
This skill provides the cross-domain decision spine for evaluating an AI-enabled workflow. It does not replace financial modeling, product measurement, statistical inference, agent evaluation, runtime operations, or AI governance. It makes those inputs meet in one accountable decision record.
The core question is not “Did the model make people faster?” It is: “What changed in this workflow, for whom, at what full cost, with what outcome and countermetric evidence, and what authority should the organization grant next?”
Entry Points
| Starting state | Start with | Primary artifact or route |
|---|---|---|
| Idea or proposed AI workflow | Steps 1–2 | templates/ai-initiative-evidence-record.md |
| Existing pilot or outcome data | Steps 3–7 | references/evidence-method.md plus the evidence record |
| Request for broader population or side-effect authority | Steps 7–8; load references/evidence-method.md section 7a for the governance packet | Governance evidence packet plus the evidence record |
| Executive, portfolio, launch, or lifecycle review | Steps 8–9 | templates/ai-economics-review.md; route launch/runtime details onward |
| Standalone financial, statistical, telemetry, runtime, or governance implementation task | When Not to Use | Named adjacent specialist skill |
When to Use
Load this skill when the user needs to:
- Build an evidence-backed business case for an AI use case or agentic workflow.
- Decide whether an AI pilot should scale, remain bounded, be redesigned, or stop.
- Review claimed AI productivity, savings, adoption, or transformation results.
- Design an AI value-realization or post-launch outcome review.
- Connect model and tool spend to workflow outcomes and worker or customer effects.
- Compare AI options while accounting for measurement uncertainty and non-comparable evidence.
- Prepare an executive, product, portfolio, or lifecycle decision about an AI-enabled intervention.
When Not to Use
| If the task is primarily... | Route to | This skill still contributes... |
|---|---|---|
| Financial statements, pricing, CAC/LTV, runway, or SaaS metrics | financial-modeling | The AI workflow's outcome and cost evidence can feed the model |
| Token, infrastructure, quota, capacity, or SLO-cost modeling | capacity-and-cost-engineering | The economic decision can consume the resulting cost boundary |
| Metric trees, event schemas, instrumentation QA, or product dashboards | product-analytics-and-measurement | The decision defines which outcome and countermetric evidence matters |
| Experimental design, causal inference, statistical testing, or power analysis | data-scientist | The decision specifies the claim and comparison it must support |
| Agent datasets, graders, traces, regression analysis, or telemetry implementation | agent-evals-and-observability | The decision consumes verified evaluation and telemetry evidence |
| Production rollout, runtime budgets, authority, fallback, escalation, or disablement | agent-production-operations | The decision sets the evidence and authority boundary |
| Organization-wide AI risk, policy, compliance, or governance operating models | ai-governance | The initiative record supplies an operating case and unresolved gaps |
| Launch-readiness packet or production go/no-go decision | production-readiness | The initiative disposition becomes one readiness input |
| General product governance cadence without an AI-specific value question | product-operations-and-governance | Use this skill only for the AI-specific value and operating-economics question |
Non-Negotiable Reasoning Rules
- Workflow evidence beats model evidence. A benchmark, demo, or vendor claim does not establish value in the target workflow.
- Speed is not value. Time saved can be spent on lower-value work, offset by review and exception handling, or enable higher-value work. Measure the business or user outcome directly.
- Averages are not enough. Inspect worker, user, task, geography, tenure, risk, and quality slices. An aggregate gain can hide a subgroup loss.
- Every benefit metric needs a countermetric. Pair throughput or cost with quality, safety, customer, worker, privacy, or reliability measures appropriate to the workflow.
- Token cost is not total cost. Include model calls, tools, retrieval, storage, networking, observability, engineering, human review, change management, governance,