qa-analyst
QA Analyst Agent. 성능 분석, 부하 테스트, 품질 메트릭 분석을 담당합니다. 성능, 부하(load), 분석, 메트릭 관련 요청 시 사용됩니다.
Install with Tessl CLI
npx tessl i github:shaul1991/shaul-agents-plugin --skill qa-analyst79
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Discovery
67%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 adequately covers both what the skill does and when to use it, which is a strength. However, the capabilities listed are somewhat high-level categories rather than specific concrete actions, and the trigger terms could be expanded to include more natural variations users might say. The description uses appropriate third-person voice.
Suggestions
Add more specific concrete actions like 'generate load test reports', 'identify performance bottlenecks', 'analyze response times' instead of general categories
Expand trigger terms to include variations like 'stress test', 'benchmark', 'latency', 'throughput', 'QPS' to improve matching coverage
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (QA/performance analysis) and lists some actions (성능 분석, 부하 테스트, 품질 메트릭 분석), but these are somewhat general categories rather than concrete specific actions like 'generate load test reports' or 'identify bottlenecks'. | 2 / 3 |
Completeness | Clearly answers both 'what' (성능 분석, 부하 테스트, 품질 메트릭 분석을 담당) AND 'when' (성능, 부하, 분석, 메트릭 관련 요청 시 사용됩니다) with explicit trigger guidance. | 3 / 3 |
Trigger Term Quality | Includes relevant keywords (성능, 부하/load, 분석, 메트릭) that users might naturally say, but missing common variations like 'performance testing', 'stress test', 'benchmark', 'QA', or file types that might be analyzed. | 2 / 3 |
Distinctiveness Conflict Risk | The focus on performance and load testing provides some distinctiveness, but '분석' (analysis) and '메트릭' (metrics) are generic terms that could overlap with data analysis or monitoring skills. | 2 / 3 |
Total | 9 / 12 Passed |
Implementation
79%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a solid QA analyst skill with excellent actionability - all commands are executable and metrics are clearly defined with thresholds. The main weakness is the lack of an explicit workflow tying the tools together (e.g., when to use ab vs wrk, how to interpret results and decide next steps). The content is appropriately concise but could benefit from a brief workflow section showing the analysis process end-to-end.
Suggestions
Add a workflow section showing the sequence: initial health check → baseline measurement → load test → analyze results → report, with decision points
Include validation criteria for when to escalate or re-test (e.g., 'If P99 > 500ms, investigate before proceeding')
Consider moving the report template to a separate REPORT_TEMPLATE.md file and referencing it
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Content is lean and efficient with no unnecessary explanations. Every section provides direct, actionable information without explaining basic concepts Claude already knows. | 3 / 3 |
Actionability | Provides fully executable bash commands for all testing scenarios (curl, ab, wrk, docker stats). Commands are copy-paste ready with real endpoint examples. | 3 / 3 |
Workflow Clarity | Individual tools and metrics are clear, but lacks explicit workflow sequencing for conducting a complete performance analysis. No validation checkpoints or feedback loops for interpreting results and iterating. | 2 / 3 |
Progressive Disclosure | Content is well-organized with clear sections and tables, but everything is inline in one file. For a skill of this size (~80 lines), some content like the report template or detailed metric thresholds could be referenced externally. | 2 / 3 |
Total | 10 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
Total | 10 / 11 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.