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

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

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

The body reads as a marketing overview of a 'capacity-planning-analyzer plugin' rather than actionable skill instructions: it contains no executable code, commands, or real workflow, and it ignores the bundled scripts that hold the actual capability. Most sections (Instructions, Output, Error Handling, Resources) are generic boilerplate that could apply to any skill.

Suggestions

Replace the conceptual 'How It Works' prose with concrete, executable steps that invoke the bundled script (e.g., 'Run `python scripts/analyze_capacity.py --input data.csv` to generate the utilization report').

Cut the Overview/Best Practices/Integration marketing copy and the generic Instructions/Output/Error-Handling boilerplate; keep only guidance Claude does not already know.

Add a well-signaled reference to the bundled materials (e.g., 'See [scripts/analyze_capacity.py](scripts/analyze_capacity.py) for the analyzer, and references/ for data formats') so the SKILL.md acts as an overview pointing one level deep into the bundle.

Dimension	Reasoning	Score
Conciseness	The body is padded with conceptual/marketing prose ('This skill empowers Claude to analyze...', 'It generates insights into growth trends, identifies potential bottlenecks...') and generic advice Claude already knows ('Ensure that the data used for analysis is accurate'), matching the verbose/explains-concepts-Claude-knows anchor.	1 / 3
Actionability	It describes what a 'plugin' does ('The plugin analyzes...', 'The plugin forecasts...') rather than instructing Claude, provides no code or commands, and even the bundled analyze_capacity.py script is never invoked or referenced, matching the 'describes rather than instructs' anchor.	1 / 3
Workflow Clarity	The 'How It Works' steps describe the plugin's behavior rather than a Claude-executable sequence, and the 'Instructions' section is generic boilerplate ('Invoke this skill... Provide context... Review the generated output') with no real task sequence and no validation checkpoints, matching the 'steps unclear or missing; no sequence for multi-step tasks' anchor.	1 / 3
Progressive Disclosure	The body has organized section headers, but the provided bundle files (scripts/analyze_capacity.py and the scripts/references/assets READMEs) are never referenced or signaled from the body, and the 'Resources' section is a placeholder ('Project documentation / Related skills and commands') rather than real one-level-deep navigation, fitting the 'some structure but references not clearly signaled; content that should be separate is inline' anchor.	2 / 3
	Total	5 / 12 Passed

Description

45%

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 conveys a clear capacity-planning purpose with both a 'what' and a 'when' clause, but it is undermined by broken grammar, a truncation artifact, and trigger terms that are far too generic to be distinctive. The voice and grammar issues plus off-topic 'code or data' phrasing make it read as machine-generated boilerplate.

Suggestions

Rewrite in clean third-person voice and fix the truncated/garbled text (e.g., 'Analyzes current resource utilization, forecasts growth, and recommends scaling strategies for CPU, memory, storage, and network capacity').

Replace the generic triggers with capacity-specific natural terms a user would say, such as 'capacity planning', 'forecast growth', 'scaling', 'resource utilization', or 'do we have enough capacity'.

Remove the off-topic 'Use when analyzing code or data' clause so the description does not invite conflicts with unrelated analysis skills.

Dimension	Reasoning	Score
Specificity	It lists several concrete actions ('assess current utilization, forecast growth trends, and recommend scaling strategies'), approaching the multi-action anchor, but the opening sentence is grammatically broken ('Execute this skill enables AI assistant to...') and the description uses imperative/second-person voice ('use this skill when...'), which per the guidelines reduces the specificity score by one.	2 / 3
Completeness	It explicitly states both what the skill does ('analyze capacity requirements and plan for future growth... recommend scaling strategies') and when to use it via a 'Use when...' clause with explicit trigger phrases, satisfying the both-what-and-when anchor; the low quality of those triggers is captured in trigger_term_quality rather than here.	3 / 3
Trigger Term Quality	The only trigger phrases offered are the generic verbs 'analyze', 'review', or 'examine' plus 'Use when analyzing code or data'; these are overly generic and omit the natural capacity-planning vocabulary (capacity, scaling, forecast growth, resource planning) a user would actually say, matching the 'overly generic' anchor.	1 / 3
Distinctiveness Conflict Risk	The triggers ('analyze', 'review', 'examine', 'analyzing code or data') are so generic they would fire for code review, data analysis, and document skills alike, so it 'would conflict with many skills' per the lowest anchor despite the specific capacity-planning 'what' clause.	1 / 3
	Total	7 / 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
Commit: 3022dd3

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.