Skills DirectorySkills Directory
SkillsLearnSecurityCategoriesDocsBlogPro
Sign InSubmit Skill
Skills Directory

Security-tested agent skills for Claude, coding agents, and AI workflows.

Directory

  • Browse Skills
  • All Skills A–Z
  • Claude Skills
  • Claude Code Skills
  • Agent Skills
  • Categories
  • Authors
  • Submit a Skill

Learn

  • Learn Hub
  • Install Claude Skills
  • Write SKILL.md
  • Skills vs MCP
  • Directories Compared

Security

  • Security
  • Methodology
  • Secure Claude Skills
  • Security Badges
  • Chrome Extension
  • Skill Manager

Company

  • About
  • Community
  • Blog
  • API Docs
  • Advertise

2026 Skills Directory. All rights reserved.

ProTermsPrivacyRefunds
Back to skills

Capital Allocation

ASecurity

Evaluates where to spend limited capital — investment appraisal, hurdle rates, payback, and comparing proposals that are not alike. Use this to evaluate an investment or major purchase, compare competing funding requests, set a hurdle rate, decide between building and buying, or review whether past investments delivered what was claimed.

646 stars
0 votes
0 copies
0 views
Added 9/23/2026
ai-agentsgoapi

Works with

api

Security Analysis

A100/100

Scanned 9/23/2026

$npx -y skills add majiayu000/claude-skill-registry --skill capital-allocation --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Capital Allocation?

Add the live security badge to your README — it updates automatically with every re-scan.

Security grade badge for Capital Allocation
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/majiayu000-capital-allocation/badge)](https://www.skillsdirectory.com/skills/majiayu000-capital-allocation)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
Files
SKILL.md
---
name: capital-allocation
description: Evaluates where to spend limited capital — investment appraisal, hurdle rates, payback, and comparing proposals that are not alike. Use this to evaluate an investment or major purchase, compare competing funding requests, set a hurdle rate, decide between building and buying, or review whether past investments delivered what was claimed.
---

# Capital allocation

Choosing among investments is choosing what not to do. This is the appraisal of individual
proposals; which businesses and bets the company should be in belongs to
`corporate-strategy:portfolio-strategy`.

## Appraise on incremental cash

Only cash flows that change because of the decision belong in the analysis:

- **Sunk costs are irrelevant.** Money already spent is not a reason to continue, though it is
  reliably presented as one.
- **Allocated overhead is usually irrelevant.** If the cost occurs anyway, it does not belong in the
  incremental case.
- **Opportunity cost is relevant**, including the capacity consumed that then cannot serve anything
  else.
- **Working capital is a real outflow.** Growth that consumes cash is not free because it is growth.

Discount for time and risk. A hurdle rate should reflect the risk of the specific proposal — applying
one company-wide rate systematically overfunds risky projects and starves safe ones.

## Read payback for what it tells you

Payback ignores everything after the threshold and so is a poor ranking tool. It is a good *liquidity
and uncertainty* measure: how long capital is at risk, and how far into an uncertain future the case
depends on.

Use net present value to decide, payback to understand exposure. A proposal with strong NPV whose
returns all arrive in years four and five is a forecasting question as much as an investment one.

## Interrogate the case, not the sponsor

Every proposal arrives advocated for. The useful questions are structural:

- What has to be true for this to work, and which of those is least certain?
- What is the counterfactual — what happens if we do nothing?
- Where is the optionality: can it be staged so a small commitment buys information before the large
  one?
- Who is accountable for the benefit after approval?

Stage-gating dominates all-or-nothing commitment where uncertainty is high. Paying for information
first is usually cheaper than being right by luck.

## Look back, or the numbers stay fictional

Compare realized outcomes against the approved case, and make it routine rather than punitive. Where
nobody looks back, forecasts drift optimistic because optimism is rewarded at approval and never
tested afterwards.

## Never

- Include sunk cost in a forward case.
- Apply one hurdle rate to proposals of different risk.
- Rank by payback.
- Approve a benefit with no owner after approval.

Attribution

majiayu000majiayu000
View sourceSee grades on GitHubMore from majiayu000 →
SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments (0)

No comments yet. Be the first to comment!

SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Related Skills

Caveman

Terse caveman voice: answer first, fluff gone, every technical fact kept. Use for /caveman, "caveman mode", "talk like caveman", "be brief", "less tokens". Stays on until "stop caveman" or "normal mode".

1100021 votes

Hyperplan

Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...

698461 votes

Writing Skills

Create and manage Claude Code skills in HASH repository following Anthropic best practices. Use when creating new skills, modifying skill-rules.json, understanding trigger patterns, working with hooks, debugging skill activation, or implementing progressive disclosure. Covers skill structure, YAML frontmatter, trigger types (keywords, intent patterns), UserPromptSubmit hook, and the 500-line rule. Includes validation and debugging with SKILL_DEBUG. Examples include rust-error-stack, cargo-dep...

3931 votes

Mcp Code Execution

Routes multi-tool workflows through MCP servers for large datasets and pipelines. Use when Bash tool overhead is limiting throughput on data-heavy tasks.

3421 votes

catchup

Recovers the conversation and failed tool calls of a previous Codex, Amp, Claude Code, Antigravity, Cline, Copilot CLI, Cursor, DeepSeek Harness, Grok Build, Kimi, OpenCode, Pi Agent, or ZCode session. Use when the user says "catch up", "what did the last session do", "get me up to speed", "I switched agents", asks to recover/summarize a previous session before continuing, or asks to diagnose or report a catchup failure. Do NOT use for the current conversation, git history, or any non-agent log.

741 votes
View all in ai-agents →