percentile-analyzer
Percentile Analyzer - Auto-activating skill for Performance Testing. Triggers on: percentile analyzer, percentile analyzer Part of the Performance Testing skill category.
39
Quality
7%
Does it follow best practices?
Impact
100%
1.00xAverage 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/percentile-analyzer/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 concrete actions, meaningful trigger terms, or usage guidance. The repeated trigger term and boilerplate structure suggest auto-generated content that was never properly filled in.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Calculates p50, p95, p99 percentiles from response time data, identifies latency outliers, generates distribution histograms'
Include a 'Use when...' clause with natural trigger terms like 'p99 latency', 'response time percentiles', 'performance distribution', 'tail latency analysis'
Remove the duplicate trigger term and expand with variations users would naturally say when needing percentile analysis
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names the skill ('Percentile Analyzer') and category ('Performance Testing') without describing any concrete actions. No specific capabilities like 'calculate percentiles', 'analyze latency distributions', or 'generate performance reports' are mentioned. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name, and provides no 'when should Claude use it' guidance. There is no 'Use when...' clause or equivalent explicit trigger guidance. | 1 / 3 |
Trigger Term Quality | The only trigger terms listed are 'percentile analyzer' repeated twice, which is the skill name itself rather than natural user language. Missing obvious terms like 'p99', 'p95', 'latency', 'response time', 'performance metrics', or 'distribution analysis'. | 1 / 3 |
Distinctiveness Conflict Risk | While 'Percentile Analyzer' is somewhat specific to a niche domain, the lack of concrete capability descriptions means it could overlap with other performance testing or analytics skills. The category mention provides some distinction but is insufficient. | 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 a hollow template with no actual content about percentile analysis. It contains only generic placeholder text that could apply to any skill topic. There is no executable code, no formulas for calculating percentiles (p50, p95, p99), no examples of analyzing latency distributions, and no guidance on interpreting results.
Suggestions
Add concrete code examples showing how to calculate percentiles from performance data (e.g., using numpy.percentile or k6's built-in percentile metrics)
Include specific formulas and thresholds for common percentile analysis (p50, p95, p99) with interpretation guidance
Provide a clear workflow for analyzing percentile data: collect metrics -> calculate percentiles -> identify outliers -> report findings
Add real examples showing input data and expected percentile output with interpretation
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that explains nothing specific about percentile analysis. Phrases like 'provides automated assistance' and 'follows industry best practices' are filler that Claude doesn't need. | 1 / 3 |
Actionability | No concrete code, commands, formulas, or specific guidance on how to actually analyze percentiles. The content describes what the skill does abstractly rather than instructing how to do it. | 1 / 3 |
Workflow Clarity | No workflow, steps, or process defined. Claims to provide 'step-by-step guidance' but contains zero actual steps for percentile analysis tasks. | 1 / 3 |
Progressive Disclosure | The content is organized into clear sections with headers, but there are no references to detailed materials, examples, or external files. The structure exists but contains no substantive content to disclose. | 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.