apdex-score-calculator
Apdex Score Calculator - Auto-activating skill for Performance Testing. Triggers on: apdex score calculator, apdex score calculator Part of the Performance Testing skill category.
34
3%
Does it follow best practices?
Impact
87%
1.01xAverage 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/apdex-score-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 extremely thin—it essentially just names the skill and its category without explaining what it does, when to use it, or providing meaningful trigger terms. The duplicated trigger term and lack of concrete actions or use-case guidance make it poorly suited for skill selection among multiple options.
Suggestions
Add concrete actions the skill performs, e.g., 'Calculates Apdex scores from response time data using configurable satisfaction thresholds (T values), classifies responses as satisfied/tolerating/frustrated, and interprets the resulting score.'
Add an explicit 'Use when...' clause, e.g., 'Use when the user asks about Apdex scores, application performance satisfaction ratings, response time thresholds, or needs to evaluate web application performance metrics.'
Expand trigger terms to include natural variations: 'apdex', 'application performance index', 'response time satisfaction', 'performance score', 'apdex threshold', 'satisfied tolerating frustrated'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description names the tool ('Apdex Score Calculator') but does not describe any concrete actions like calculating scores from response times, setting thresholds, or interpreting results. It merely states it's an 'auto-activating skill for Performance Testing' which is vague. | 1 / 3 |
Completeness | The 'what' is extremely weak—it only names itself without explaining what it actually does. The 'when' is limited to a duplicated trigger phrase with no explicit 'Use when...' clause describing scenarios that should activate this skill. | 1 / 3 |
Trigger Term Quality | The trigger terms are just 'apdex score calculator' repeated twice. It misses natural variations users might say like 'apdex', 'application performance index', 'response time satisfaction', 'apdex threshold', or 'calculate apdex'. | 1 / 3 |
Distinctiveness Conflict Risk | The term 'Apdex' is fairly niche and specific to application performance monitoring, which reduces conflict risk. However, the generic 'Performance Testing' category label and lack of specific actions could cause overlap with other performance testing 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 a hollow placeholder that contains no substantive content. It repeatedly describes itself in abstract terms without ever providing the Apdex formula (Apdex = (Satisfied + Tolerated/2) / Total), threshold configuration guidance, executable code, or any concrete instructions. It fails on every dimension of the rubric.
Suggestions
Add the actual Apdex formula with clear definitions of Satisfied, Tolerating, and Frustrated categories, including the threshold parameter T.
Provide executable code examples (e.g., Python or JavaScript functions) that calculate Apdex scores from sample response time data.
Include concrete input/output examples showing how response time arrays and a threshold value produce a specific Apdex score with interpretation (e.g., 0.85 = 'Good').
Remove all meta-description sections ('When to Use', 'Example Triggers', 'Capabilities') that describe the skill rather than teaching the task, and replace with actionable technical content.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is almost entirely filler and meta-description. It explains what the skill does in abstract terms without providing any actual Apdex calculation logic, formulas, code, or concrete guidance. Every section restates the same vague information. | 1 / 3 |
Actionability | There is zero actionable content—no Apdex formula, no code, no commands, no concrete examples. The skill describes itself rather than instructing Claude how to calculate Apdex scores. A user would learn nothing from this. | 1 / 3 |
Workflow Clarity | No workflow is defined. There are no steps for calculating an Apdex score, no inputs/outputs specified, no validation checkpoints. The phrase 'step-by-step guidance' is promised but never delivered. | 1 / 3 |
Progressive Disclosure | No bundle files exist and no references are provided. The content is a monolithic block of meta-description with no structure that aids navigation or discovery of actual technical content. | 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
22f797a
- 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.