benchmark-suite-creator
Benchmark Suite Creator - Auto-activating skill for Performance Testing. Triggers on: benchmark suite creator, benchmark suite creator Part of the Performance Testing skill category.
31
0%
Does it follow best practices?
Impact
84%
1.02xAverage 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/benchmark-suite-creator/SKILL.mdQuality
Discovery
0%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 essentially a template placeholder with no substantive content. It repeats the skill name as its only trigger term, provides no concrete actions or capabilities, and lacks any explicit guidance on when Claude should select this skill. It would be indistinguishable from other performance or testing skills in a multi-skill environment.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Creates benchmark test suites, defines performance metrics, generates load test configurations, and produces performance comparison reports.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks about benchmarking, performance testing, load tests, stress tests, throughput measurement, or creating test suites for performance evaluation.'
Remove the duplicated trigger term and replace with diverse natural language variations users might actually say, such as 'benchmark', 'perf test', 'load test', 'stress test', 'performance suite', 'benchmark comparison'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description names a domain ('Performance Testing') and a label ('Benchmark Suite Creator') but does not describe any concrete actions. There are no specific capabilities listed such as 'creates benchmark tests', 'measures response times', or 'generates performance reports'. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name itself, and there is no 'when should Claude use it' clause. The 'Triggers on' line just repeats the skill name rather than providing meaningful trigger guidance. | 1 / 3 |
Trigger Term Quality | The only trigger terms listed are 'benchmark suite creator' repeated twice. There are no natural user keywords like 'performance test', 'load testing', 'benchmarking', 'throughput', 'latency', or other terms a user would naturally say. | 1 / 3 |
Distinctiveness Conflict Risk | The description is too vague to distinguish this skill from other performance-related or testing-related skills. 'Performance Testing' and 'Benchmark Suite Creator' are broad labels without specific differentiating details. | 1 / 3 |
Total | 4 / 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 shell with no substantive content. It consists entirely of meta-descriptions about what the skill supposedly does without providing any actual instructions, code, commands, or concrete guidance for creating benchmark suites. It fails on every dimension of the rubric.
Suggestions
Add concrete, executable code examples for creating benchmark suites using specific tools (e.g., k6 scripts, JMeter configurations, or Python benchmarking frameworks).
Define a clear multi-step workflow for creating a benchmark suite: e.g., 1) identify metrics, 2) write benchmark scripts, 3) configure test parameters, 4) validate results, with specific commands at each step.
Remove all boilerplate meta-sections ('When to Use', 'Example Triggers', 'Capabilities') and replace with actionable content—these sections waste tokens describing the skill rather than teaching it.
Include at least one complete, copy-paste-ready benchmark suite example with expected output format and validation criteria.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler and boilerplate. It explains nothing Claude doesn't already know, repeats the phrase 'benchmark suite creator' excessively, and provides zero substantive information about how to actually create benchmark suites. | 1 / 3 |
Actionability | There is no concrete guidance whatsoever—no code, no commands, no specific steps, no examples of benchmark configurations. Every section is vague and abstract, describing what the skill supposedly does rather than instructing how to do anything. | 1 / 3 |
Workflow Clarity | No workflow is defined. The skill claims to provide 'step-by-step guidance' but contains zero actual steps. There are no sequences, no validation checkpoints, and no process to follow. | 1 / 3 |
Progressive Disclosure | The content is a flat, uninformative page with no references to detailed materials, no links to examples or configuration files, and no meaningful structure beyond generic placeholder headings. | 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
c8a915c
- 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.