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

13%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./plugins/performance/capacity-planning-analyzer/skills/analyzing-capacity-planning/SKILL.md

Quality

Discovery

27%

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 suffers from a fundamental contradiction: the body describes a specific capacity planning tool, but the trigger clause is extremely generic ('analyze code or data'). The description is also truncated and uses first/second person phrasing ('this skill enables AI assistant'), reducing clarity. The generic triggers would cause this skill to conflict with many other analytical skills.

Suggestions

Replace the generic trigger clause with capacity-planning-specific triggers, e.g., 'Use when the user asks about capacity planning, resource utilization, scaling strategies, growth forecasting, or infrastructure sizing.'

Fix the truncated text ('when the u...') and remove the contradictory 'analyzing code or data' trigger to avoid conflicts with other analytical skills.

Rewrite in third person voice (e.g., 'Analyzes capacity requirements and plans for future growth') instead of 'this skill enables AI assistant'.

Dimension	Reasoning	Score
Specificity	It names a domain (capacity planning) and some actions (analyze capacity requirements, assess utilization, forecast growth, recommend scaling strategies), but the description is muddled by mixing specific capacity planning language with a generic trigger clause about 'analyzing code or data'.	2 / 3
Completeness	It attempts to answer both 'what' (capacity planning analysis) and 'when' (Use when analyzing code or data), but the 'when' clause is contradictory and overly generic compared to the specific 'what'. The description also appears truncated ('when the u...').	2 / 3
Trigger Term Quality	The trigger terms ('analyze', 'review', 'examine') are extremely generic and would match virtually any analytical task. They are not natural keywords a user would say specifically when needing capacity planning. The mismatch between the capacity planning domain and the generic triggers is problematic.	1 / 3
Distinctiveness Conflict Risk	The trigger clause 'Use when analyzing code or data' with triggers like 'analyze', 'review', or 'examine' would conflict with virtually any analytical skill. Despite the capacity planning specifics in the body, the trigger guidance makes it highly prone to false matches.	1 / 3
	Total	6 / 12 Passed

Implementation

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

This skill is almost entirely generic boilerplate with no actionable, concrete, or executable content. It describes what a capacity planning analyzer would do in abstract terms but provides zero specific commands, code, tool invocation syntax, or real examples. The content wastes tokens on explanations of obvious concepts and placeholder sections that add no value.

Suggestions

Replace abstract descriptions with concrete, executable examples showing exact tool invocation syntax (e.g., the specific command or API call to the capacity-planning-analyzer plugin with real parameters and expected output).

Remove all generic boilerplate sections (Prerequisites, Instructions, Output, Error Handling, Resources) that contain no skill-specific information — these waste tokens without adding value.

Add a concrete workflow with validation steps, e.g., 'Run `capacity-analyzer --check cpu,memory,storage` → review output → if utilization > 80%, run `capacity-analyzer --forecast --horizon 90d` → generate scaling plan'.

Provide at least one complete input/output example showing the actual data format the plugin expects and the structured output it produces.

Dimension	Reasoning	Score
Conciseness	Extremely verbose and padded with unnecessary context. The 'Overview' section restates the title, 'How It Works' explains obvious plugin behavior, 'When to Use' repeats the description, and sections like 'Best Practices', 'Integration', 'Prerequisites', 'Instructions', 'Output', 'Error Handling', and 'Resources' are all generic filler that teach Claude nothing actionable. Nearly every token is wasted.	1 / 3
Actionability	There is no concrete code, no executable commands, no API calls, no specific tool invocation syntax, and no real examples with actual input/output. The examples describe what the skill 'will do' in abstract terms rather than showing how to invoke it. Instructions like 'Invoke this skill when the trigger conditions are met' and 'Provide necessary context and parameters' are completely vague.	1 / 3
Workflow Clarity	The numbered steps in 'How It Works' and 'Instructions' are abstract descriptions, not actionable workflows. There are no validation checkpoints, no error recovery loops, no specific commands to run, and no concrete sequencing. The 'Instructions' section is entirely generic boilerplate with no task-specific guidance.	1 / 3
Progressive Disclosure	The content is a monolithic wall of text with no references to external files, no bundle files to support it, and no meaningful structure for navigation. Sections like 'Resources' point to nothing specific ('Project documentation', 'Related skills and commands'). Content that could be split or referenced is instead presented as vague inline filler.	1 / 3
	Total	4 / 12 Passed

Validation

81%

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 — 9 / 11 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	9 / 11 Passed

Repository: jeremylongshore/claude-code-plugins-plus-skills
Commit: 4801da6

Reviewed: 5 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.