analyzing-capacity-planning

Execute this skill enables AI assistant to analyze capacity requirements and plan for future growth. it uses the capacity-planning-analyzer plugin to assess current utilization, forecast growth trends, and recommend scaling strategies. use this skill when the u... Use when analyzing code or data. Trigger with phrases like 'analyze', 'review', or 'examine'.

Quality

44%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/performance/capacity-planning-analyzer/skills/analyzing-capacity-planning/SKILL.md

Quality

Content

20%

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

The body is generic, non-actionable filler with no executable guidance and no links to the real bundled script, while its listed bundle references include files that do not exist. It describes the skill's purpose rather than telling Claude how to perform it.

Suggestions

Add concrete executable guidance: show how to run the bundled analyze_capacity.py (e.g. `python scripts/analyze_capacity.py <dir> --output report.txt --json`) and what its output means, instead of the vague Instructions/Output sections.

Cut generic filler (Overview restating the description, Best Practices truisms, "produces structured output relevant to the task") so every remaining section earns its tokens.

Fix progressive disclosure: link the real analyze_capacity.py from the body, and correct the scripts/assets READMEs to remove the non-existent forecast_capacity.py, recommend_scaling.py, and example_capacity_data.csv listings (or add those files).

Dimension	Reasoning	Score
Conciseness	The body is padded with generic prose Claude already knows ("Ensure that the data used for analysis is accurate and up-to-date", "Regularly monitor capacity metrics") and low-value sections (vague Instructions, "produces structured output relevant to the task"), matching the level-1 verbose anchor.	1 / 3
Actionability	There is no code, command, or concrete example anywhere; the body describes rather than instructs ("Invoke this skill when the trigger conditions are met", "Provide necessary context and parameters"), and the bundled analyze_capacity.py is never referenced or shown, matching level 1.	1 / 3
Workflow Clarity	A 3-step sequence exists (Analyze Utilization → Forecast Growth → Generate Recommendations), but it describes the plugin's behavior abstractly rather than Claude's actions and has no validation checkpoints, matching level 2's "steps listed but checkpoints missing".	2 / 3
Progressive Disclosure	The body is sectioned but references none of the bundle files, and the bundle READMEs list phantom files (forecast_capacity.py, recommend_scaling.py, example_capacity_data.csv) that do not actually exist — structure exists but references are not signaled and partly broken, matching level 2.	2 / 3
	Total	6 / 12 Passed

Description

70%

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

The description names concrete capabilities and includes explicit trigger guidance, but its trigger terms are overly generic and would conflict with many other skills; the text is also grammatically broken and partly truncated ("use this skill when the u...").

Suggestions

Replace the generic trigger verbs ("analyze", "review", "examine") with capacity-specific natural phrases a user would actually say, e.g. "Use when planning capacity, forecasting resource growth, or deciding how to scale CPU, memory, storage, or network infrastructure."

Fix the broken/truncated text ("use this skill when the u...") and the malformed opening ("Execute this skill enables AI assistant to...") so the description reads cleanly in third person.

Add domain-specific trigger nouns ("capacity planning", "resource utilization", "scaling strategy", "forecast growth") to distinguish this skill from general code/data analysis skills and reduce wrong-skill conflicts.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — "analyze capacity requirements", "assess current utilization", "forecast growth trends", "recommend scaling strategies" — matching the level-3 anchor for multiple specific concrete actions.	3 / 3
Completeness	Clearly answers what (concrete capacity actions) and provides an explicit when clause ("Use when analyzing code or data. Trigger with phrases like 'analyze', 'review', or 'examine'"); the Use-when guidance is present, not merely implied.	3 / 3
Trigger Term Quality	Relevant domain keywords appear (capacity, growth, scaling), but the explicit trigger list ("analyze", "review", "examine") is generic and missing natural variations like "capacity planning" or "forecast resource needs", matching level 2.	2 / 3
Distinctiveness Conflict Risk	"Use when analyzing code or data" plus generic trigger verbs (analyze/review/examine) would fire for many unrelated skills, matching the level-1 anchor for very generic, conflict-prone triggers.	1 / 3
	Total	9 / 12 Passed

Validation

87%

Warnings & errors only

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

Validation — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
allowed_tools_field	'allowed-tools' contains unusual tool name(s)	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	14 / 16 Passed

Repository: jeremylongshore/claude-code-plugins-plus-skills
Path: plugins/performance/capacity-planning-analyzer/skills/analyzing-capacity-planning/SKILL.md
Commit: 15940c5

Reviewed: 2 days ago

Table of Contents

Discovery Implementation Validation

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.