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.
Overall
score
24%
Does it follow best practices?
Validation for skill structure
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill apdex-score-calculatorActivation
22%This description is essentially a placeholder that relies entirely on the skill name for identification. It lacks any explanation of what the calculator actually does, what inputs it requires, or when users should invoke it. The duplicated trigger term and absence of concrete actions make this description inadequate for skill selection among multiple options.
Suggestions
Add specific actions the skill performs, e.g., 'Calculates Apdex scores from response time data using configurable satisfaction thresholds (T values)'
Include a 'Use when...' clause with explicit triggers like 'Use when analyzing application response times, calculating user satisfaction metrics, or when the user mentions apdex, response time thresholds, or performance satisfaction scores'
Add natural keyword variations users might say: 'apdex', 'application performance index', 'response time satisfaction', 'T threshold', 'frustrated/tolerating/satisfied users'
| 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's 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, which provides some distinctiveness. 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%This skill content is essentially a placeholder template with no actual substance. It contains zero technical content about Apdex scores - no formula (Apdex = (Satisfied + Tolerating/2) / Total), no threshold definitions, no code examples, and no practical guidance. The entire content describes what the skill claims to do rather than actually doing it.
Suggestions
Add the actual Apdex formula with clear variable definitions: Apdex = (Satisfied + (Tolerating/2)) / Total Samples, where Satisfied = response time ≤ T, Tolerating = T < response time ≤ 4T, Frustrated = response time > 4T
Provide executable code example for calculating Apdex from a list of response times with a configurable threshold T
Include interpretation guidance: what Apdex scores mean (1.0 = excellent, 0.94-0.85 = good, 0.70-0.85 = fair, <0.70 = poor)
Remove all meta-description content ('This skill activates when...', 'Provides step-by-step guidance...') and replace with actual technical content
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with boilerplate that provides no actionable value. It explains what the skill does in abstract terms without any actual implementation details, formulas, or code that Claude doesn't already know. | 1 / 3 |
Actionability | No concrete guidance whatsoever - no Apdex formula, no code examples, no threshold definitions (T value), no calculation methods. The content describes rather than instructs, with phrases like 'provides step-by-step guidance' without actually providing any. | 1 / 3 |
Workflow Clarity | No workflow is defined. For an Apdex calculator, there should be clear steps: define threshold T, categorize response times (satisfied/tolerating/frustrated), apply the formula. None of this is present. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of meta-description with no actual technical content to organize. There are no references to detailed materials, examples, or related documentation - just self-referential trigger descriptions. | 1 / 3 |
Total | 4 / 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.