Skills DirectorySkills Directory
SkillsLearnSecurityCategoriesDocsCommunityBlog
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

Company

  • About
  • Community
  • Blog
  • API Docs
  • Advertise

2026 Skills Directory. All rights reserved.

ProTermsPrivacyRefunds
Back to skills

Resource Allocation Analysis

ASecurity

Distributes limited resources across competing needs — making the trade-offs explicit rather than implicit. Triggers: 'resource allocation', 'how do we distribute this', 'competing priorities', 'trade-off analysis', 'how do we split this', 'allocation decision'.

19 stars
0 votes
0 copies
1 views
Added 9/19/2026
ai-agentsgo

Security Analysis

A100/100

Scanned 9/19/2026

Install to Claude Code

$npx -y skills add rondoflow/rondoflow --skill resource-allocation-analysis --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Resource Allocation Analysis?

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

Security grade badge for Resource Allocation Analysis
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/rondoflow-resource-allocation-analysis/badge)](https://www.skillsdirectory.com/skills/rondoflow-resource-allocation-analysis)

More formats (shields.io, HTML) on the badges page.

Download with Pro
Files
SKILL.md
---
name: resource-allocation-analysis
description: "Distributes limited resources across competing needs — making the trade-offs explicit rather than implicit. Triggers: 'resource allocation', 'how do we distribute this', 'competing priorities', 'trade-off analysis', 'how do we split this', 'allocation decision'."
---

# Resource Allocation Analysis

Every allocation is a trade-off — giving to one thing means giving less to another. The problem is that most allocations are made implicitly, leaving the trade-offs invisible. Making trade-offs explicit forces honest prioritisation and prevents the political habit of pretending everything can be fully funded.

---

## Your Process

**Step 1: Inventory Available Resources**
Name and quantify the resources to be allocated: budget, headcount, time, capacity. Be precise about what is actually available — not what is desired.

**Framing check:** Confirm the specific allocation situation before continuing. State what resources you've identified and the decision context they apply to in one sentence, then use `AskUserQuestion`:
- **Question:** "I'm reading this as: [your one-sentence framing — e.g. 'Distributing $X budget / Y headcount across Z competing claims to determine the best allocation for [goal]']. Is that right?"
- **Header:** "Framing"
- **Options:**
  - **Yes — proceed** — framing is correct
  - **Adjust** — one element is off; user will correct it before you continue
  - **Reframe** — different situation than read; incorporate the correction before proceeding

**Step 2: List All Competing Claims**
Every demand on the resource. Include maintenance and ongoing commitments, not just new initiatives. Claims that are implicitly assumed to be funded should be made explicit here.

**Step 3: Assess Each Claim**
For each claim: what is the strategic priority (how directly does this serve the most important goals)? What is the cost of under-resourcing it (what breaks, slows, or is lost if it receives less)?

**Step 4: Identify Constraints**
Are there minimums (must have at least X to function), maximums (more than Y produces no additional value), or dependencies (A must be funded before B makes sense)?

**Step 5: Draft an Allocation**
Distribute the available resource across claims. At this stage, make the trade-offs explicit: write down what each claim gives up under this draft allocation.

**Step 6: Sense-Check Against Overall Goals**
Does this allocation, taken as a whole, serve the most important outcomes? Where is the allocation driven by politics or inertia rather than strategic priority?

---

## Human Check-in

Before proceeding, use the `AskUserQuestion` tool. State your interpretation of the situation in 1–2 sentences — what is being analyzed and what the core question is — then ask:

- **Question:** "My read: [your 1–2 sentence interpretation]. How do you want to proceed?"
- **Header:** "Scope"
- **Options:**
  - **Full analysis** — Complete all steps, reasoning shown throughout
  - **Key findings only** — Bottom-line output, skip step-by-step detail
  - **Trade-off table only** — What each allocation gives up, skip the full recommendation
  - **Reframe** — The read is off; correct it and the analysis will follow the corrected framing

Proceed based on their selection. If the user reframes, incorporate the correction before running any analysis.

## Output Format

### Available Resources
| Resource | Total Available |
|----------|----------------|
| ... | ... |

### Competing Claims
| Claim | Strategic Priority | Cost of Under-Resourcing | Constraints |
|-------|------------------|-------------------------|-------------|
| ... | High / Medium / Low | ... | Min / Max / Dependency |

### Draft Allocation
| Claim | Allocation | Trade-off (what it gives up) |
|-------|-----------|------------------------------|
| ... | ... | ... |

### Strategic Alignment Check
Does this allocation serve the most important outcomes? Where does it diverge from strategic priority — and is that divergence justified?

---

## Notes

The most useful output is the trade-off column — if the trade-offs can't be written clearly, the allocation hasn't been thought through. Force each trade-off to be named before the allocation is finalised.

---

## What's Next

After delivering this output, use `AskUserQuestion` to offer the next move:

- **Question:** "Allocation analysed. What's next?"
- **Header:** "Next"
- **Options:**
  - `/resource-bottleneck-analysis` — Find bottlenecks in the current allocation
  - `/decision-criteria-weighting` — Weight criteria by resource constraints
  - `/resource-waste-audit` — Audit for waste in the current allocation
  - **Done** — Wrap up and synthesise what we have so far

Attribution

rondoflowrondoflow
View sourceMore from rondoflow →
SSkills DirectorySkills Directory

Know which skills are safe — weekly.

Best new skills + every skill we flagged as malicious. From the team that scanned 103,619.

Join free

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

Know which skills are safe — weekly.

Best new skills + every skill we flagged as malicious. From the team that scanned 103,619.

Join free

Related Skills

Caveman

Ultra-compressed communication mode that cuts output tokens while keeping technical accuracy. Levels: lite, full, ultra and the wenyan variants. Use for /caveman, "caveman mode", "talk like caveman", "be brief" or "less tokens".

1074701 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', ...

693161 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.

3351 votes

catchup

Recovers the conversation and failed tool calls of a previous Codex, Claude Code, Antigravity, Cline, Copilot CLI, Cursor, DeepSeek Harness, 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.

691 votes

math-skill

A comprehensive mathematical reasoning skill for AI assistants — handles arithmetic to research-level problems with rigorous step-by-step reasoning, systematic verification, and transparent uncertainty handling

381 votes
View all in ai-agents →