Token导航 LogoToken导航

Agent Skill · 运维和基础设施

thinking-opportunity-cost(思考机会成本)

thinking-opportunity-cost 用于处理 GitHub 仓库、Issue、Pull Request 和代码协作信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要围绕仓库状态、代码变更或协作事项进行整理时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

thinking-opportunity-cost 是运维和基础设施类 Agent Skill,可用宿主为 Codex、Claude、Cursor、Gemini CLI,通过GitHub 仓库获取,权限为权限未标注;许可证信息还不明确,第三方扫描已通过,按安装量在运维和基础设施类的 2,449 个 Skill 里排第 1,613。

总安装 465周安装 19GitHub Stars 46下载 149核验 2026-05-01

安装说明

本站只整理中文说明,不托管安装包,也不代用户安装。
GitHub
许可证
unknown

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:thinking-opportunity-cost(思考机会成本)
来源仓库:https://github.com/tjboudreaux/cc-thinking-skills
仓库路径:skills/thinking-opportunity-cost
安装命令:
npx skills add https://github.com/tjboudreaux/cc-thinking-skills --skill thinking-opportunity-cost
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 npx skills 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

skills.shnpx skills
npx skills add https://github.com/tjboudreaux/cc-thinking-skills --skill thinking-opportunity-cost

这个 Skill 是做什么的

运维和基础设施类 Skill 处理部署、监控、日志和云资源,多数需要较高的执行权限。

思考机会成本用于处理 GitHub 仓库、Issue、Pull Request 和代码协作信息。适合在资源受限环境下权衡任务价值与投入产出比。量化时间、人力与技术债之间的替代关系,辅助优先级排序。

安装命令:npx skills add https://github.com/tjboudreaux/cc-thinking-skills --skill thinking-opportunity-cost 需用户提供完整备选方案列表,否则默认假设可能失真。

来源仓库内路径:skills/thinking-opportunity-cost

上手步骤

4 步
  1. 1

    确认自己的宿主工具

    公开资料标注支持 Codex、Claude、Cursor、Gemini CLI;先确认自己用的是其中之一,再按对应工具的 Skills 目录放置。

  2. 2

    拿到安装命令

    可以直接复制的命令是 npx skills add https://github.com/tjboudreaux/cc-thinking-skills --skill thinkin…;命令里的占位符换成自己的路径或密钥再执行。

  3. 3

    安装后重启宿主

    命令执行完要完全退出宿主工具再打开,让新装的 Skill 被重新扫描到,否则列表里可能看不到。

  4. 4

    按最小权限试用

    权限没有明确标注,第一次使用时只给一个无关紧要的任务,观察它到底读了哪些文件和网络。

常见问题

6 条

thinking-opportunity-cost 怎么安装?

在终端执行 npx skills add https://github.com/tjboudreaux/cc-thinking-skills --skill thinking-opportun…。装完完全退出宿主工具再打开,让它重新扫描本地 Skill。

thinking-opportunity-cost 支持哪些 AI 工具?

公开资料标注支持 Codex、Claude、Cursor、Gemini CLI。其他工具只要能读取本地 Skill 目录,一般也能手动放进去,但要自己确认触发方式是否一致。

thinking-opportunity-cost 需要什么权限?

权限级别没有明确标注。第一次使用时建议只给无关紧要的任务,观察它实际读写了哪些内容。

thinking-opportunity-cost 是免费的吗?

公开资料没有标注明确许可证,收费和商用限制都无法确认。正式使用前请到来源仓库核对授权说明。

thinking-opportunity-cost 用的人多吗?

公开数据是累计安装 465 次,近一周安装 19 次,下载 149 次,GitHub 46 星。这些数字来自第三方目录统计,只能当作热度参考,不代表质量或安全性。

thinking-opportunity-cost 安全吗?

第三方扫描结果为通过,但这只覆盖已知的静态检查项,不能替代自己读一遍源码和安装命令。

值得选的地方和要先想清楚的地方

值得选的地方

  • 同时适配 4 种工具,换客户端不用重新找替代品。
  • 第三方扫描已通过,常见的高风险行为没有命中。

先想清楚的地方

  • 许可证没有明确标注,能不能商用、能不能再分发都不确定。
  • 第三方目录整理,版本更新和行为细节以来源仓库为准。

适不适合你

更适合

  • 已经在用 Codex,想直接扩展它能力的人。
  • 需要处理运维和基础设施类任务、又不想每次都手写提示词的人。

不太适合

  • 需要明确授权才能用到公司项目里的场景。
  • 需要厂商级技术支持和 SLA 的生产系统。

运维和基础设施类 Skill 对比

6 个同类
Skill总安装GitHub 星权限许可证扫描
brainstorming

头脑风暴 · Codex、Claude

3,148,776173,131操作浏览器MIT通过
copywriting

文案写作 · Codex、Claude

1,996,72425,583需要联网MIT通过
openclaw-secure-linux-cloud

OpenClaw secure linux cloud 命令行 · Codex、Claude

1,853,08840接触敏感数据未明确未通过
xget

xget 命令行 · Codex、Claude

1,799,28040执行命令未明确未通过
requesting-code-review

代码审查请求 · Codex、Claude

1,590,144173,103权限未标注MIT通过
thinking-opportunity-cost

思考机会成本 · 本页

46546权限未标注未明确通过

按安装量取同分类前几名;数字来自第三方目录统计,只作热度参考,不代表质量结论。

SKILL.md 原文

Opportunity Cost Thinking

Overview

Opportunity cost is the value of the next-best alternative foregone when making a choice. Every decision to do X is simultaneously a decision not to do Y, Z, and everything else. Engineers often focus on the value of their chosen path while underweighting what they're giving up.

Core Principle: The true cost of anything is what you give up to get it. A "free" option that consumes time has massive opportunity cost.

When to Use

  • Resource allocation (time, money, people)
  • Feature prioritization
  • Build vs. buy decisions
  • Technical debt evaluation
  • Career decisions
  • Architecture choices
  • Saying "yes" to any commitment

Decision flow:

Making a commitment?
  → Have you considered what you're NOT doing? → no → APPLY OPPORTUNITY COST
  → Is the foregone value significant? → yes → Factor into decision
                                       ↘ no → Proceed

The Opportunity Cost Framework

Step 1: Identify the Choice

State the decision explicitly:

Choice: Build custom authentication system
Commitment: 3 engineers for 4 months

Step 2: List the Alternatives

What else could you do with those resources?

Alternatives for 3 engineers × 4 months:
A. Build custom auth (the choice)
B. Use Auth0 ($500/mo) + build 3 features
C. Improve performance of existing system
D. Reduce technical debt backlog by 40%
E. Build new product line MVP

Step 3: Value Each Alternative

Estimate the value of each path:

| Alternative | Direct Value | Strategic Value | Risk | Total Value |
|-------------|--------------|-----------------|------|-------------|
| Custom auth | Full control, no vendor cost | IP ownership | High (security) | Medium |
| Auth0 + features | Features faster | Time to market | Low | High |
| Performance work | 2x throughput | Customer satisfaction | Low | Medium-High |
| Tech debt | Faster future dev | Developer retention | Low | Medium |
| New product MVP | Revenue diversification | Growth potential | High | High |

Step 4: Calculate Opportunity Cost

Opportunity cost = Value of best foregone alternative

If we choose Custom Auth:
  Best alternative foregone: Auth0 + features (rated "High")
  Opportunity cost: The features we won't build + faster time to market

Step 5: Make Decision with Full Accounting

Total cost of choice = Direct cost + Opportunity cost

Custom Auth True Cost:
  Direct: 3 engineers × 4 months = 12 engineer-months
  Opportunity: 3 features delayed by 4 months
             + Market share lost to faster competitors
             + Developer time not on revenue features

Question: Is custom auth worth all of that?

Opportunity Cost Patterns

The "Free" Trap

Nothing is free if it consumes time:

Scenario: "We can build this ourselves instead of paying $10K for the tool"

Analysis:
- Tool cost: $10,000
- Build time: 2 engineers × 2 weeks = 4 engineer-weeks
- Engineer cost: ~$4,000/week fully loaded = $16,000
- Maintenance: 1 week/quarter = $16,000/year ongoing

True cost: $16K + ongoing maintenance > $10K + $0 maintenance
Plus: What else could those engineers have built?

The Sunk Cost Interaction

Don't let sunk costs distort opportunity cost analysis:

BAD thinking:
"We've already spent 6 months on this, we can't abandon it"
(Sunk cost fallacy ignores opportunity cost of continuing)

GOOD thinking:
"Given where we are now, what's the best use of the NEXT 6 months?"
(Fresh opportunity cost analysis from current state)

The Hidden Alternative

The status quo is always an alternative:

Proposal: Migrate to Kubernetes
Alternatives considered: ECS, Nomad, K8s
Missing alternative: Don't migrate, improve current system

Full analysis should include:
- Cost of migration (all options)
- Cost of staying put (often undervalued)
- Opportunity cost of engineers doing migration vs. features

Time as the Scarcest Resource

Time opportunity cost is often highest:

"Quick meeting, only 30 minutes"

For 8-person meeting:
- Direct cost: 30 min × 8 = 4 person-hours
- Opportunity cost: 4 hours not spent on focused work
- Context switching cost: 15 min recovery × 8 = 2 more hours
- True cost: ~6 person-hours of productivity

Question: Is this meeting worth 6 hours of productivity?

Application Areas

Feature Prioritization

## Opportunity Cost Analysis: Feature A vs. B

| Factor | Feature A | Feature B |
|--------|-----------|-----------|
| Dev time | 4 weeks | 2 weeks |
| Revenue impact | $50K/month | $30K/month |
| Time to value | 4 weeks | 2 weeks |

If we build A first:
- We get A in 4 weeks
- We get B in 6 weeks
- 2 extra weeks without B = $60K foregone

If we build B first:
- We get B in 2 weeks
- We get A in 6 weeks
- 2 extra weeks without A = $100K foregone

Decision: Build A first despite higher dev cost (higher opportunity cost of delay)

Build vs. Buy

## Build vs. Buy: Monitoring System

Build:
- Development: $200K (4 engineers × 6 months)
- Maintenance: $80K/year
- Time to production: 6 months
- Opportunity cost: Features those engineers would have built

Buy (Datadog):
- License: $50K/year
- Integration: $30K (2 engineers × 1 month)
- Time to production: 1 month
- Opportunity cost: None significant

5-year TCO:
- Build: $200K + ($80K × 5) + opportunity cost = $600K + opportunity
- Buy: ($50K × 5) + $30K = $280K

Decision: Buy unless unique requirements justify 2x+ cost

Technical Debt

## Technical Debt Opportunity Cost

Current state: 20% of engineering time on maintenance
Proposed: 3-month refactoring project

Analysis:
- 3 months of refactoring = no features for 3 months
- After refactoring: 10% time on maintenance (saves 10%)
- Break-even: When does saved maintenance = investment?

If team = 10 engineers:
- Investment: 10 × 3 = 30 engineer-months
- Monthly savings: 10 × 10% = 1 engineer-month
- Break-even: 30 months

Opportunity cost: Features not built during 3-month refactoring
Real question: Are those features worth more than 30+ months of 10% overhead?

Hiring Decisions

## Hiring Opportunity Cost

Choice: Hire senior engineer at $250K
Alternative: Two mid-level at $300K total

Analysis:
- Senior: Higher immediate productivity, mentorship
- Two mid: More throughput long-term, redundancy

Opportunity cost of senior:
- Fewer total engineers
- Less coverage/redundancy
- Longer ramp-up if they leave

Opportunity cost of two mid:
- More management overhead
- Longer to complex projects
- Training investment

Decision depends on: Current team composition, project complexity, growth stage

Opportunity Cost Template

# Opportunity Cost Analysis: [Decision]

## The Choice
What we're considering: [Primary option]
Resource commitment: [Time, money, people]

## Alternatives
What else could we do with these resources?

| # | Alternative | Resource Use | Direct Value | Strategic Value |
|---|-------------|--------------|--------------|-----------------|
| 1 | [Primary choice] | [X] | [Value] | [Strategic] |
| 2 | [Alternative 1] | [X] | [Value] | [Strategic] |
| 3 | [Alternative 2] | [X] | [Value] | [Strategic] |
| 4 | Do nothing | [X] | [Value] | [Strategic] |

## Opportunity Cost Calculation

Best foregone alternative: [Which one]
Value of that alternative: [Quantified if possible]

## True Cost of Primary Choice
- Direct cost: [Resources consumed]
- Opportunity cost: [Value of foregone alternative]
- Total: [Sum]

## Decision
Is [primary choice] worth [total cost]?
[Reasoning]

## Reversibility
If we're wrong, can we change course? At what cost?

Mental Shortcuts

The "What Else?" Question

Always ask: "If we didn't do this, what would we do instead?"

The 10x Test

If opportunity cost is 10x the direct cost, rethink the decision.

The Time Value Multiplier

Engineer time often has 3-5x multiplier in opportunity cost vs. dollar cost.

The Status Quo Alternative

Always include "change nothing" as an explicit alternative.

Verification Checklist

  • Explicitly stated the choice and resource commitment
  • Listed at least 3 alternatives (including status quo)
  • Valued each alternative (even roughly)
  • Identified the best foregone alternative
  • Calculated opportunity cost explicitly
  • Made decision accounting for full cost
  • Considered reversibility

Key Questions

  • "What are we NOT doing by choosing this?"
  • "Is the 'free' option actually free?"
  • "What would we do with these resources otherwise?"
  • "What's the value of our next-best alternative?"
  • "Is this worth more than everything we're giving up?"
  • "Have we included the status quo as an option?"

Economic Wisdom

"There is no such thing as a free lunch." — Milton Friedman

Every choice has a cost, even if it's not written on an invoice. The cost is what you gave up to make that choice. Recognizing opportunity cost transforms how you evaluate decisions.

"The cost of a thing is the amount of what I will call life which is required to be exchanged for it." — Henry David Thoreau

For engineers: substitute "engineering time" for "life" — it's your most valuable and constrained resource.

平台分布

Codex

35.68%
按下载量换算53

Claude

28%
按下载量换算42

Cursor

20.53%
按下载量换算31

Gemini CLI

8.59%
按下载量换算13

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

权限未标注

当前来源未能明确判断权限范围,默认进入异常复核队列。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。目前只有一个公开来源,建议同时核对源仓库。

继续浏览同类 Skills