throughput-calculator
Throughput Calculator - Auto-activating skill for Performance Testing. Triggers on: throughput calculator, throughput calculator Part of the Performance Testing skill category.
39
Quality
7%
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 severely underdeveloped, essentially serving as a placeholder rather than a functional skill description. It lacks any explanation of what the skill does, provides redundant and narrow trigger terms, and gives Claude no meaningful guidance for when to select this skill over others.
Suggestions
Add concrete actions describing what the skill does, e.g., 'Calculates throughput metrics including requests per second, transactions per minute, and data transfer rates from performance test results.'
Add a 'Use when...' clause with natural trigger terms like 'calculate throughput', 'measure TPS', 'requests per second', 'performance metrics', 'load test results'.
Remove the duplicate trigger term and expand to include variations users would naturally say when needing throughput calculations.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names the skill ('Throughput Calculator') and its category ('Performance Testing') without describing any concrete actions. There are no verbs indicating what the skill actually does. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name, and while it mentions triggers, they are just the skill name repeated. There is no 'Use when...' clause or explanation of when Claude should select this skill. | 1 / 3 |
Trigger Term Quality | The trigger terms are redundant ('throughput calculator' listed twice) and overly narrow. Missing natural variations users might say like 'calculate throughput', 'measure throughput', 'requests per second', 'TPS', or 'performance metrics'. | 1 / 3 |
Distinctiveness Conflict Risk | The term 'throughput calculator' is fairly specific and unlikely to conflict with many other skills, but 'Performance Testing' as a category is broad and could overlap with other performance-related skills without clearer differentiation. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
7%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is essentially a placeholder with no actual content. It describes what a throughput calculator skill would do but provides no formulas, code, examples, or actionable guidance for calculating throughput. The entire content could be replaced with a single sentence and lose nothing of value.
Suggestions
Add actual throughput calculation formulas (e.g., throughput = requests / time, with units and variations)
Include executable code examples showing how to calculate throughput from test results (e.g., parsing k6 or JMeter output)
Provide concrete examples with sample inputs and expected outputs (e.g., '1000 requests in 60 seconds = 16.67 req/sec')
Add guidance on interpreting throughput metrics and common thresholds for different application types
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that provides no actual value. Phrases like 'provides automated assistance' and 'follows industry best practices' are vague filler that Claude doesn't need. | 1 / 3 |
Actionability | There is zero concrete guidance - no code, no commands, no formulas, no examples of actual throughput calculations. The content describes what the skill does rather than instructing how to do anything. | 1 / 3 |
Workflow Clarity | No workflow is provided whatsoever. A throughput calculator should show formulas, input parameters, and calculation steps, but none are present. | 1 / 3 |
Progressive Disclosure | The content has some structure with clear sections, but there's nothing of substance to disclose. No references to detailed materials or examples are provided. | 2 / 3 |
Total | 5 / 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
0c08951
- 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.