analyzing-system-throughput
tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill analyzing-system-throughputAnalyze and optimize system throughput including request handling, data processing, and resource utilization. Use when identifying capacity limits or evaluating scaling strategies. Trigger with phrases like "analyze throughput", "optimize capacity", or "identify bottlenecks".
60%
Overall
Validation
Implementation
Activation
Validation
81%| Criteria | Description | Result |
|---|---|---|
skill_md_line_count | SKILL.md line count is 99 (<= 500) | Pass |
frontmatter_valid | YAML frontmatter is valid | Pass |
name_field | 'name' field is valid: 'analyzing-system-throughput' | Pass |
description_field | 'description' field is valid (276 chars) | Pass |
description_voice | 'description' uses third person voice | Pass |
description_trigger_hint | Description includes an explicit trigger hint | Pass |
compatibility_field | 'compatibility' field not present (optional) | Pass |
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
metadata_field | 'metadata' field not present (optional) | Pass |
license_field | 'license' field is present: MIT | Pass |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
body_present | SKILL.md body is present | Pass |
body_examples | Examples detected (code fence or 'Example' wording) | Pass |
body_output_format | Output/return/format terms detected | Pass |
body_steps | Step-by-step structure detected (ordered list) | Pass |
Total | 13 / 16 Passed |
Implementation
20%This skill is highly verbose and abstract, explaining concepts Claude already understands while failing to provide any concrete, executable guidance. It references a 'throughput-analyzer' plugin but never shows actual usage syntax or commands. The content is mostly descriptive filler that could be replaced with a few concrete code examples and specific commands.
Suggestions
- Replace abstract descriptions with concrete executable examples showing actual throughput-analyzer plugin commands/API calls
- Remove redundant sections (Overview, How It Works, When to Use all say the same thing) and consolidate into a lean quick-start
- Add specific code examples for collecting metrics, e.g., actual commands to query '{baseDir}/metrics/throughput/' files
- Include validation checkpoints in the workflow, such as 'verify metrics are being collected before proceeding to analysis'
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose with significant redundancy. The 'Overview', 'How It Works', 'When to Use', and 'Examples' sections all repeat the same concepts. Explains obvious things Claude already knows (what throughput analysis is, what bottlenecks are). The content could be reduced by 70%+ without losing actionable information. | 1 / 3 |
Actionability | No concrete code, commands, or executable guidance. Everything is abstract description ('analyze metrics', 'identify bottlenecks') without showing HOW to do it. References a 'throughput-analyzer' plugin but provides no actual usage syntax, API calls, or command examples. The examples describe what 'the skill will do' rather than providing executable steps. | 1 / 3 |
Workflow Clarity | Steps are listed in the 'Instructions' section with a clear sequence, but there are no validation checkpoints, no feedback loops for error recovery, and no concrete verification steps. The 'Error Handling' section lists things to check but doesn't integrate them into the workflow. | 2 / 3 |
Progressive Disclosure | Content is organized into sections, but it's a monolithic document with no references to external files for detailed content. The structure exists but much of the content is redundant across sections rather than appropriately split. References to '{baseDir}/metrics/throughput/' suggest external resources but don't provide clear navigation. | 2 / 3 |
Total | 6 / 12 Passed |
Activation
100%This is a well-crafted skill description that excels across all dimensions. It provides specific capabilities, includes explicit trigger guidance with natural user phrases, and clearly defines both what the skill does and when to use it. The domain focus on system throughput and capacity analysis creates a distinct niche with low conflict risk.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'analyze and optimize system throughput', 'request handling', 'data processing', 'resource utilization', 'identifying capacity limits', and 'evaluating scaling strategies'. | 3 / 3 |
Completeness | Clearly answers both what (analyze/optimize throughput, request handling, data processing, resource utilization) AND when (identifying capacity limits, evaluating scaling strategies) with explicit 'Use when' and 'Trigger with' clauses. | 3 / 3 |
Trigger Term Quality | Includes explicit natural trigger phrases users would say: 'analyze throughput', 'optimize capacity', 'identify bottlenecks', plus domain terms like 'scaling strategies' and 'capacity limits'. | 3 / 3 |
Distinctiveness Conflict Risk | Clear niche focused on system throughput and capacity analysis with distinct triggers like 'throughput', 'capacity', 'bottlenecks', and 'scaling strategies' that are unlikely to conflict with general coding or document skills. | 3 / 3 |
Total | 12 / 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.