throughput-calculator
Throughput Calculator - Auto-activating skill for Performance Testing. Triggers on: throughput calculator, throughput calculator Part of the Performance Testing skill category.
Overall
score
23%
Does it follow best practices?
Validation for skill structure
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill throughput-calculatorActivation
7%This description is severely underdeveloped, essentially serving as a placeholder rather than a functional skill description. It lacks any explanation of what the throughput calculator actually calculates, what inputs it takes, or what outputs it produces. The redundant trigger terms and absence of concrete actions make it nearly useless for skill selection.
Suggestions
Add specific actions the skill performs, e.g., 'Calculates requests per second, transactions per minute, and data transfer rates from performance test results'
Include a 'Use when...' clause with natural trigger terms like 'calculate throughput', 'measure TPS', 'requests per second', 'performance metrics', 'load test results'
Specify the inputs and outputs, e.g., 'Takes response times and request counts to compute throughput metrics and identify bottlenecks'
| 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 the 'when' clause is just a repetition of the skill name rather than meaningful trigger guidance. No explicit 'Use when...' clause with actionable triggers. | 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 | While 'throughput calculator' is somewhat specific, the vague 'Performance Testing skill category' could overlap with other performance-related skills. The lack of specific use cases makes it unclear when this skill should be chosen over other performance tools. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
7%This skill is essentially an empty placeholder with no actual content. It describes what a throughput calculator skill would do but provides zero actionable guidance, formulas, code examples, or concrete instructions 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 examples)
Include executable code examples for calculating throughput from test results (e.g., parsing k6 or JMeter output)
Provide concrete input/output examples showing sample data and expected calculated results
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, calculation steps, and output formats - none of which are present. | 1 / 3 |
Progressive Disclosure | The content is organized into clear sections with headers, but there's nothing of substance to disclose. The structure exists but contains no meaningful content to navigate. | 2 / 3 |
Total | 5 / 12 Passed |
Validation
69%Validation — 11 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
description_trigger_hint | Description may be missing an explicit 'when to use' trigger hint (e.g., 'Use when...') | Warning |
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 |
body_steps | No step-by-step structure detected (no ordered list); consider adding a simple workflow | Warning |
Total | 11 / 16 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.