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.
39
Quality
11%
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
22%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 just restating the skill name without explaining what it actually does or when to use it. The trigger terms are redundant (listed twice identically) and miss common user phrasings. The description provides no actionable information for Claude to determine when this skill should be selected over others.
Suggestions
Add concrete actions describing what the calculator does, e.g., 'Calculates Apdex scores from response time data using configurable satisfaction thresholds (T values)'
Add a 'Use when...' clause with explicit triggers like 'Use when the user needs to calculate application performance satisfaction scores, measure user experience metrics, or analyze response time distributions'
Expand trigger terms to include natural variations: 'apdex', 'application performance index', 'response time satisfaction', 'performance score', 'user satisfaction metric'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names the tool ('Apdex Score Calculator') without describing any concrete actions. It doesn't explain what calculations are performed, what inputs are needed, or what outputs are produced. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name, and the 'when' guidance is circular (triggers on its own name). There is no explicit 'Use when...' clause explaining scenarios for activation. | 1 / 3 |
Trigger Term Quality | Includes 'apdex score calculator' as a trigger term (duplicated), which is a relevant keyword. However, it misses natural variations users might say like 'calculate apdex', 'application performance index', 'response time satisfaction', or 'apdex threshold'. | 2 / 3 |
Distinctiveness Conflict Risk | The term 'Apdex' is fairly specific to application performance monitoring, reducing conflict risk. However, the generic 'Performance Testing' category and lack of specific use cases could cause overlap with other performance-related skills. | 2 / 3 |
Total | 6 / 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 placeholder that provides no actual value. It contains only meta-description of what the skill claims to do without any concrete information about Apdex score calculation (formula, thresholds, code examples, interpretation guidelines). The entire content could be replaced with the actual Apdex formula and a single code example to be infinitely more useful.
Suggestions
Add the actual Apdex formula: Apdex = (Satisfied + Tolerating/2) / Total samples, with explanation of threshold T
Include executable code example showing how to calculate Apdex from response time data (e.g., Python function taking response times and threshold T)
Provide concrete examples with sample data: 'Given T=500ms and these response times [200, 450, 800, 2500], Apdex = ...'
Add interpretation guidelines: what Apdex scores mean (0.94+ excellent, 0.85-0.93 good, etc.) and how to choose appropriate T values
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that provides no actual information about Apdex score calculation. It explains what the skill does in abstract terms without any concrete content, wasting tokens on meta-description rather than actionable guidance. | 1 / 3 |
Actionability | There is zero concrete guidance on how to calculate Apdex scores. No formula, no code, no examples of threshold values (T), no sample calculations. The content only describes what the skill claims to do without actually doing it. | 1 / 3 |
Workflow Clarity | No workflow is provided whatsoever. Apdex calculation involves specific steps (defining threshold T, categorizing response times as satisfied/tolerating/frustrated, applying the formula) but none of this is present. | 1 / 3 |
Progressive Disclosure | The content is a single block of generic placeholder text with no structure for actual learning. There are no references to detailed materials, no examples section, and no organized content to navigate. | 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
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.