analyzing-capacity-planning
tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill analyzing-capacity-planningExecute 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'.
Validation
81%| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 13 / 16 Passed | |
Implementation
7%This skill content is almost entirely abstract description and boilerplate with no actionable guidance. It explains what a capacity planning analyzer conceptually does but provides zero concrete implementation details - no actual commands, code examples, API calls, or specific tool invocations. The content reads like marketing copy rather than executable instructions for Claude.
Suggestions
Replace abstract descriptions with actual executable code showing how to invoke the capacity-planning-analyzer plugin with specific parameters and example inputs
Add concrete command examples like `capacity-planning-analyzer --analyze-cpu --threshold 80` or actual API calls with expected JSON input/output schemas
Remove generic boilerplate sections (Prerequisites, Instructions, Output, Error Handling, Resources) that provide no skill-specific information
Include a real worked example showing actual data input, the specific commands/code to run, and sample output format
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose with extensive padding explaining concepts Claude already knows. Sections like 'Overview', 'How It Works', 'When to Use This Skill' repeat similar information. Generic boilerplate sections (Prerequisites, Instructions, Output, Error Handling, Resources) add no actionable value. | 1 / 3 |
Actionability | No concrete code, commands, or executable guidance provided. Examples describe what 'the skill will' do in abstract terms rather than showing actual commands, API calls, or code snippets. The 'Instructions' section is completely generic ('Invoke this skill when trigger conditions are met'). | 1 / 3 |
Workflow Clarity | While numbered steps exist, they describe abstract processes ('Analyze Utilization', 'Forecast Growth') without any concrete implementation details, validation checkpoints, or error recovery steps. No actual workflow Claude can follow. | 1 / 3 |
Progressive Disclosure | Content is organized into sections with headers, but it's a monolithic document with no references to external files. The 'Resources' section mentions 'Project documentation' and 'Related skills' without any actual links or file references. | 2 / 3 |
Total | 5 / 12 Passed |
Activation
27%This description suffers from a disconnect between its specific capacity planning content and its overly generic trigger guidance. The body mentions useful specifics like 'capacity-planning-analyzer plugin' and 'scaling strategies', but the 'Use when' clause undermines distinctiveness by being far too broad. Additionally, the description is truncated and uses improper voice ('enables AI assistant').
Suggestions
Replace generic triggers with capacity-planning-specific terms: 'Use when the user mentions capacity planning, scaling, utilization analysis, growth forecasting, or infrastructure sizing'
Remove the meta-language ('enables AI assistant to') and rewrite in third person active voice: 'Analyzes capacity requirements and plans for future growth...'
Complete the truncated description and ensure the 'Use when' clause aligns with the actual skill purpose (capacity planning, not generic code/data analysis)
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (capacity planning) and some actions (analyze capacity requirements, assess utilization, forecast growth, recommend scaling strategies), but the description is muddled with meta-language ('enables AI assistant') and gets cut off mid-sentence. | 2 / 3 |
Completeness | Has a 'what' (capacity planning analysis) and includes a 'Use when' clause, but the 'when' is contradictory and generic ('analyzing code or data') rather than specific to capacity planning scenarios. The description is also truncated. | 2 / 3 |
Trigger Term Quality | The trigger terms provided ('analyze', 'review', 'examine') are extremely generic and would match almost any analytical task, not specifically capacity planning. Missing natural terms like 'capacity', 'scaling', 'utilization', 'growth forecast'. | 1 / 3 |
Distinctiveness Conflict Risk | The generic triggers ('analyze', 'review', 'examine') and broad 'Use when analyzing code or data' would cause this skill to conflict with virtually any analysis-related skill, despite the specific capacity planning focus in the body. | 1 / 3 |
Total | 6 / 12 Passed |
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.