analyzing-system-throughput
Analyze 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".
51
41%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/performance/throughput-analyzer/skills/analyzing-system-throughput/SKILL.mdQuality
Discovery
82%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a solid description that clearly communicates both what the skill does and when to use it, with explicit trigger phrases. Its main weaknesses are that the capability descriptions remain somewhat high-level (e.g., 'resource utilization' is broad) and the domain could overlap with adjacent performance/infrastructure skills. Adding more concrete actions or distinguishing details would strengthen it further.
Suggestions
Add more concrete, specific actions to improve specificity—e.g., 'measure requests per second, profile queue depths, model horizontal vs vertical scaling tradeoffs'.
Differentiate from related skills (e.g., general performance profiling, infrastructure monitoring) by clarifying scope boundaries—e.g., 'Focuses on system-level throughput metrics, not application-level code profiling or network diagnostics'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (system throughput) and lists some actions (analyze, optimize, request handling, data processing, resource utilization), but these are still fairly broad and not deeply concrete—e.g., it doesn't specify particular techniques, tools, or output formats. | 2 / 3 |
Completeness | Clearly answers both 'what' (analyze and optimize system throughput including request handling, data processing, resource utilization) and 'when' (identifying capacity limits, evaluating scaling strategies) with explicit trigger phrases provided. | 3 / 3 |
Trigger Term Quality | Includes explicit trigger phrases like 'analyze throughput', 'optimize capacity', 'identify bottlenecks', plus natural keywords such as 'scaling strategies', 'capacity limits', 'request handling', and 'resource utilization'—good coverage of terms a user would naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | While it targets throughput and capacity analysis specifically, terms like 'optimize', 'bottlenecks', and 'resource utilization' could overlap with general performance optimization, infrastructure monitoring, or profiling skills. It's somewhat specific but not fully distinct. | 2 / 3 |
Total | 10 / 12 Passed |
Implementation
0%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 abstract description with no actionable content. It reads like a marketing overview rather than an operational guide—it repeatedly describes what the skill does without ever showing how to do it. There are no concrete commands, code examples, metric queries, or specific analysis techniques that Claude could execute.
Suggestions
Replace abstract descriptions with concrete, executable examples: show actual commands for collecting throughput metrics (e.g., specific CLI tools, API calls, or scripts), sample metric data, and how to interpret results.
Add a concrete workflow with validation checkpoints, e.g., 'Run `X command` to collect metrics → verify output contains Y fields → if saturation > 80%, flag as bottleneck → recommend specific scaling action.'
Remove redundant sections (Overview, How It Works, When to Use, Best Practices, Integration) that explain concepts Claude already knows, and consolidate into a lean quick-start section with executable steps.
Either provide the referenced bundle files (metrics templates, analyzer scripts) or remove references to them; hollow references to non-existent tools undermine the skill's credibility.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose with extensive explanation of concepts Claude already knows. Sections like 'Overview', 'How It Works', 'When to Use This Skill', 'Best Practices', and 'Integration' are padded with generic descriptions that add no actionable value. The content could be reduced by 70%+ without losing useful information. | 1 / 3 |
Actionability | No concrete code, commands, or executable guidance anywhere. The 'Examples' section describes what the skill 'will do' in abstract terms rather than showing actual commands, queries, or analysis techniques. The 'Instructions' section is a vague numbered list with no specifics on how to actually perform any of the steps. | 1 / 3 |
Workflow Clarity | The workflow steps are abstract and lack any validation checkpoints. Steps like 'Identify critical system components' and 'Collect request and data throughput metrics' provide no concrete guidance on how to execute them, what tools to use, or how to verify results. No feedback loops or error recovery within the workflow. | 1 / 3 |
Progressive Disclosure | Monolithic wall of text with no bundle files to reference. Content is poorly organized with redundant sections (the 'How It Works' and 'Instructions' sections largely overlap). References to '${CLAUDE_SKILL_DIR}/metrics/throughput/' and a 'throughput-analyzer' plugin exist but no supporting files are provided, making these references hollow. | 1 / 3 |
Total | 4 / 12 Passed |
Validation
81%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 | |
- Commit
3a2d27d
- 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.