CtrlK
BlogDocsLog inGet started
Tessl Logo

capacity-planner

Use when an ops leader (Director of CX, Head of Support, VP Ops, Head of BizOps, Head of IT ops, Head of Finance ops) is sizing ops capacity, building a headcount plan, modeling utilization risk, planning Q3 capacity or annual support capacity, or designing CS coverage — and needs Erlang-C queueing math, P90 demand sizing, shrinkage-adjusted FTE, manager-trigger thresholds, and a quarterly hiring sequence with ramp + attrition. Apply when sustained team utilization is above 80% or when the team is growing >50% in 12 months. Run before committing the headcount budget. This is NOT engineering capacity (see vpe-advisor for DORA + cycle time) and NOT strategic 3-year workforce planning (see chro-advisor).

72

Quality

91%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

The canonical home for this skill is capacity-planner in alirezarezvani/claude-skills

SKILL.md
Quality
Evals
Security

Quality

Content

82%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A strong, highly actionable body with concrete commands, specific thresholds, and a clear sequenced workflow grounded in cited operational canon. Its main weaknesses are minor redundancy in the repeated forcing-question discipline, the absence of an explicit validate→fix→retry loop on script outputs, and bundle files that are referenced but not actually present.

Suggestions

Conciseness: state the forcing-question discipline ('one at a time, do not skip ahead, answers written down') once in the library intro and remove the two repetitions in the Workflow step and closing line.

Progressive disclosure: the referenced scripts/, references/, and assets/ files are not present in the bundle — add them so the signaled one-level-deep navigation actually resolves.

Workflow clarity: add an explicit validate→fix→retry loop for script outputs (e.g., 'if P(breach at P90) > 10%, re-run capacity_modeler.py with higher FTE and re-check') to close the feedback-loop gap.

DimensionReasoningScore

Conciseness

Dense and operational throughout, assuming Claude's competence (it cites Erlang-C, Little's Law, Reinertsen without explaining them), but the discipline phrases ('Do not skip ahead. Answers must be written down') repeat three times and the Q1-Q7 forcing-question format is elaborated beyond strict necessity — minor instances that could be trimmed. Not a 5 because not every token earns its place; not a 3 because there is no padding explaining concepts Claude already knows.

4 / 5

Actionability

Provides copy-paste-ready commands ('python3 scripts/capacity_modeler.py --sample') with concrete flags (--profile, --input, --output, --sample, --help) and specific numeric thresholds ('>85% sustained', 'Spread >30 percentage points', 'span of control crosses 7 ICs/manager', 'Q1 35%, Q4 15%'), covering the common cases fully.

5 / 5

Workflow Clarity

A clear 5-step sequence (Intake → Model → Flag risk → Sequence → Forcing questions) with real checkpoints ('If you only have averages, stop and pull the distribution', 'fix that before hiring', forcing-question gate before committing), but it lacks the explicit validate→fix→retry feedback loop shown in the score-5 anchor. Not a 3 because checkpoints are present and the skill is analytical rather than destructive, so the batch/destruction cap does not apply.

4 / 5

Progressive Disclosure

Well-organized with clearly signaled one-level-deep references split across Scripts, References, and Assets sections (e.g. 'references/queueing_theory_canon.md — ... 8 sources. The math.'), but the referenced bundle files do not actually exist on disk (references/, scripts/, assets/ are absent), so the signaled navigation resolves to dead ends — a real organization gap that keeps it off 5.

4 / 5

Total

17

/

20

Passed

Description

100%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

An exemplary description: it explicitly states both what the skill does and when to use it, packs in concrete capabilities and natural trigger terms with synonym coverage, and clearly fences off adjacent skills to avoid mis-triggering. Voice is third-person/imperative throughout with no first- or second-person penalty.

DimensionReasoningScore

Specificity

Lists multiple concrete capabilities — 'sizing ops capacity, building a headcount plan, modeling utilization risk, planning Q3 capacity or annual support capacity, or designing CS coverage' plus 'Erlang-C queueing math, P90 demand sizing, shrinkage-adjusted FTE, manager-trigger thresholds, and a quarterly hiring sequence with ramp + attrition' — giving comprehensive coverage of specific actions.

5 / 5

Completeness

Explicitly answers both 'what' ('needs Erlang-C queueing math, P90 demand sizing, shrinkage-adjusted FTE...') and 'when' ('Use when an ops leader... is sizing ops capacity...', 'Apply when sustained team utilization is above 80%', 'Run before committing the headcount budget') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Natural trigger phrases a user would say ('sizing ops capacity', 'building a headcount plan', 'utilization is above 80%', 'team is growing >50%') with synonym coverage across multiple role titles (Director of CX, Head of Support, VP Ops, etc.), matching the comprehensive-coverage anchor.

5 / 5

Distinctiveness Conflict Risk

Carves a clear niche (ops queued-work capacity sizing) and explicitly distinguishes from adjacent skills — 'This is NOT engineering capacity (see vpe-advisor...)' and 'NOT strategic 3-year workforce planning (see chro-advisor)' — minimizing conflict risk.

5 / 5

Total

20

/

20

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

referenced_paths_exist

Referenced path issues: 9 missing

Warning

Total

14

/

16

Passed

Repository
alirezarezvani/claude-skills
Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.