throughput-calculator
Throughput Calculator - Auto-activating skill for Performance Testing. Triggers on: throughput calculator, throughput calculator Part of the Performance Testing skill category.
36
3%
Does it follow best practices?
Impact
100%
1.05xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./planned-skills/generated/10-performance-testing/throughput-calculator/SKILL.mdQuality
Discovery
7%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 description is essentially a label rather than a functional description. It names the skill and its category but provides no concrete actions, no meaningful trigger terms beyond the skill's own name, and no guidance on when Claude should select it. It would be nearly useless for skill selection in a multi-skill environment.
Suggestions
Add concrete actions describing what the skill does, e.g., 'Calculates throughput metrics such as requests per second, transactions per second, and data transfer rates for performance testing scenarios.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks about throughput, requests per second, RPS, TPS, bandwidth, load capacity, or performance benchmarks.'
Include diverse natural keywords users might say, such as 'requests per second', 'RPS', 'TPS', 'load testing', 'bandwidth', 'capacity planning', rather than repeating the skill name.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description names the domain ('Performance Testing') and the tool ('Throughput Calculator') but does not describe any concrete actions. There is no indication of what the skill actually does—no verbs like 'calculates', 'measures', 'estimates', etc. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond naming itself, and the 'when' clause is essentially just the skill name repeated. There is no explicit 'Use when...' guidance with meaningful triggers. | 1 / 3 |
Trigger Term Quality | The only trigger terms listed are 'throughput calculator' repeated twice. There are no natural variations a user might say, such as 'requests per second', 'RPS', 'load testing', 'bandwidth calculation', 'TPS', or other common synonyms. | 1 / 3 |
Distinctiveness Conflict Risk | The term 'Throughput Calculator' is somewhat specific and unlikely to conflict with many other skills, but the vague 'Performance Testing' category and lack of concrete scope means it could overlap with other performance-related skills. | 2 / 3 |
Total | 5 / 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 an empty shell—a meta-description of what a throughput calculator skill would do, without any actual content. It contains no formulas, no code examples, no tool-specific guidance (k6, JMeter, etc.), and no actionable instructions. It reads as an auto-generated template that was never filled in with real substance.
Suggestions
Add concrete throughput calculation formulas and executable code examples (e.g., calculating requests/second, bytes/second) with tools like k6 or JMeter.
Define a clear workflow: e.g., 1) Define test parameters, 2) Run load test with specific command, 3) Collect metrics, 4) Calculate throughput, 5) Validate against baseline.
Remove all self-referential meta-content ('This skill activates when...', 'Example Triggers') and replace with actual domain knowledge about throughput measurement.
Include at least one complete, copy-paste-ready example showing input parameters and expected throughput output.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic filler that tells Claude nothing useful. Phrases like 'Provides step-by-step guidance' and 'Follows industry best practices' are vague platitudes. The entire file explains what the skill is rather than providing any actual throughput calculation knowledge or instructions. | 1 / 3 |
Actionability | There is zero concrete guidance—no formulas, no code, no commands, no examples of actual throughput calculations. The skill describes itself rather than instructing Claude how to perform throughput calculations. There is nothing executable or copy-paste ready. | 1 / 3 |
Workflow Clarity | No workflow, steps, or process is defined. The skill claims to provide 'step-by-step guidance' but contains none. There are no validation checkpoints, no sequenced operations, and no actual procedure for calculating throughput. | 1 / 3 |
Progressive Disclosure | There are no references to external files, no bundle files, and no structured navigation. The content is a shallow, monolithic placeholder with no depth or layered information architecture. | 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
172d892
- 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.