stress-test-config
Stress Test Config - Auto-activating skill for Performance Testing. Triggers on: stress test config, stress test config 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 stress-test-configActivation
22%This description is severely underdeveloped, functioning more as a label than a useful skill description. It fails to explain what concrete actions the skill performs and relies on a templated format that provides minimal information for skill selection. The repeated trigger term and lack of specific capabilities make it difficult for Claude to confidently choose this skill over alternatives.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Generates stress test configuration files, defines load patterns, configures concurrent user simulations, and sets performance thresholds'
Include a proper 'Use when...' clause with explicit triggers, e.g., 'Use when the user needs to create or modify stress test configurations, set up load testing parameters, or configure performance benchmarks'
Expand trigger terms to include natural variations users might say: 'load test setup', 'performance test config', 'stress testing', 'concurrent users', 'throughput testing'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description contains no concrete actions - only 'Auto-activating skill for Performance Testing' which is vague and abstract. No specific capabilities like 'generate load configurations', 'define test scenarios', or 'configure concurrent users' are mentioned. | 1 / 3 |
Completeness | The 'what' is essentially missing - we only know it relates to 'Performance Testing' but not what it actually does. The 'when' is weakly implied through 'Triggers on' but lacks explicit guidance like 'Use when...' with clear scenarios. | 1 / 3 |
Trigger Term Quality | Contains 'stress test config' as a trigger term (repeated twice), which is a reasonable keyword users might say. However, it misses common variations like 'load test', 'performance config', 'stress testing configuration', '.yaml', or 'test parameters'. | 2 / 3 |
Distinctiveness Conflict Risk | Being part of 'Performance Testing skill category' and mentioning 'stress test config' provides some specificity, but 'Performance Testing' is broad enough to potentially conflict with other testing-related skills like load testing, benchmark testing, or general test configuration skills. | 2 / 3 |
Total | 6 / 12 Passed |
Implementation
0%This skill content is essentially a placeholder template with no actual substance. It contains only meta-descriptions of what a skill should do rather than any actionable guidance on stress test configuration. The content fails to provide any concrete information about k6, JMeter, load patterns, thresholds, or any other stress testing concepts mentioned in the tags.
Suggestions
Add concrete code examples for stress test configurations (e.g., k6 scripts with ramping VUs, JMeter test plans with thread groups and assertions)
Include specific stress test parameters and patterns: ramp-up strategies, duration settings, threshold definitions, and common load profiles
Provide a clear workflow: 1) Define test scenarios, 2) Configure load parameters, 3) Set pass/fail thresholds, 4) Run and validate results
Add example configuration files with annotations explaining key settings (e.g., stages, thresholds, checks in k6)
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that provides no actual information about stress test configuration. Phrases like 'provides automated assistance' and 'follows industry best practices' are meaningless filler that Claude doesn't need. | 1 / 3 |
Actionability | There is zero concrete guidance - no code examples, no configuration snippets, no specific commands, no actual stress test parameters or patterns. The content describes what the skill supposedly does rather than instructing how to do anything. | 1 / 3 |
Workflow Clarity | No workflow is provided whatsoever. There are no steps for creating stress test configurations, no validation checkpoints, and no process for iterating on test parameters or analyzing results. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of vague descriptions with no structure for actual learning. There are no references to detailed materials, no examples to follow, and no clear organization of stress testing concepts. | 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.