percentile-analyzer
Percentile Analyzer - Auto-activating skill for Performance Testing. Triggers on: percentile analyzer, percentile analyzer Part of the Performance Testing skill category.
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill percentile-analyzerOverall
score
19%
Does it follow best practices?
Validation for skill structure
Activation
7%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 capabilities describing what the skill does, e.g., 'Calculates and analyzes percentile metrics (p50, p90, p95, p99) from performance test data, identifies latency outliers, and generates distribution reports.'
Include a 'Use when...' clause with natural trigger terms: 'Use when analyzing response times, calculating percentiles, reviewing latency distributions, or when the user mentions p99, performance metrics, or load test results.'
Remove the duplicate trigger term and expand with variations users would naturally say: 'percentile', 'p99', 'latency analysis', 'response time distribution', 'performance percentiles'.
| 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 response times', or 'generate latency 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 common terms users would say like 'p99', 'latency', 'response time', 'performance metrics', or 'percentile calculation'. | 1 / 3 |
Distinctiveness Conflict Risk | While 'Percentile Analyzer' is somewhat specific to a niche domain, the lack of concrete details 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
0%This skill content is essentially a placeholder template with no substantive information about percentile analysis. It contains only generic descriptions of what a skill should do without any actual instructions, code examples, or concrete guidance. The content fails to teach Claude anything about calculating, interpreting, or using percentiles in performance testing.
Suggestions
Add executable code examples showing how to calculate common percentiles (p50, p90, p95, p99) from performance test data using specific tools like k6 or JMeter
Include concrete guidance on interpreting percentile results and when to use different percentile thresholds for SLA definitions
Provide a clear workflow for analyzing percentile data: collect metrics -> calculate percentiles -> identify outliers -> report findings
Remove all generic boilerplate text ('provides automated assistance', 'follows industry best practices') and replace with specific, actionable content
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that provides no actual information about percentile analysis. Phrases like 'provides automated assistance' and 'follows industry best practices' are meaningless filler that waste tokens. | 1 / 3 |
Actionability | There is zero concrete guidance - no code, no commands, no specific examples of how to actually analyze percentiles. The content describes what the skill supposedly does but never instructs how to do anything. | 1 / 3 |
Workflow Clarity | No workflow is provided whatsoever. There are no steps, no sequence, and no validation checkpoints for performing percentile analysis in performance testing contexts. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of vague descriptions with no structure pointing to detailed materials. The 'Related Skills' section mentions a category but provides no actual references or navigation. | 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.