running-smoke-tests
This skill runs smoke tests to verify critical application functionality. It executes pre-defined test suites that check system health, authentication, core features, and external integrations. Use this skill after deployments, upgrades, or significant configuration changes to ensure the application is operational. Trigger this skill using the terms "smoke test" or "st".
93
53%
Does it follow best practices?
Impact
97%
1.04xAverage score across 15 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./backups/skills-migration-20251108-070147/plugins/testing/smoke-test-runner/skills/smoke-test-runner/SKILL.mdQuality
Discovery
100%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 is a strong skill description that clearly communicates what the skill does (runs smoke tests checking system health, authentication, core features, and integrations), when to use it (after deployments, upgrades, or configuration changes), and provides explicit trigger terms. It uses proper third-person voice throughout and is concise without unnecessary padding.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'runs smoke tests', 'executes pre-defined test suites', and specifies what is checked: 'system health, authentication, core features, and external integrations'. | 3 / 3 |
Completeness | Clearly answers both 'what' (runs smoke tests verifying system health, authentication, core features, integrations) and 'when' (after deployments, upgrades, or configuration changes) with explicit trigger terms ('smoke test' or 'st'). | 3 / 3 |
Trigger Term Quality | Includes natural trigger terms users would say: 'smoke test', 'st', 'deployments', 'upgrades', 'configuration changes'. The explicit mention of abbreviation 'st' and the full term 'smoke test' covers common user language well. | 3 / 3 |
Distinctiveness Conflict Risk | Has a clear niche focused specifically on smoke testing with distinct triggers ('smoke test', 'st'). Unlikely to conflict with general testing, unit testing, or integration testing skills due to the specific scope and trigger terms. | 3 / 3 |
Total | 12 / 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 essentially a description of what smoke testing is rather than an actionable skill that teaches Claude how to perform smoke tests. It lacks any concrete code, commands, test definitions, or executable guidance. The content is padded with explanations of concepts Claude already understands and provides no actual implementation.
Suggestions
Replace the abstract descriptions with actual executable test code or commands (e.g., specific curl commands for health checks, authentication test scripts, database connectivity checks).
Define the actual smoke test suite: what specific tests are run, what endpoints are hit, what constitutes pass/fail for each test category (health, auth, core features, integrations).
Remove the 'Overview', 'When to Use', 'Best Practices', and 'Integration' sections entirely — they explain concepts Claude already knows and add no actionable value.
Add a concrete output format showing what the test results report should look like (e.g., a pass/fail table with test names, status, and error details).
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is verbose and explains concepts Claude already knows (what smoke tests are, when to use them, best practices like 'focus on critical flows'). The 'Overview', 'When to Use', 'Best Practices', and 'Integration' sections are all filler that restate the description without adding actionable value. | 1 / 3 |
Actionability | There is no concrete code, no actual test commands, no test suite definition, no executable examples. The skill describes what it would do in abstract terms ('execute the smoke test suite') but never shows how. There are no actual tests, scripts, or commands to run. | 1 / 3 |
Workflow Clarity | The workflow is entirely abstract: 'execute tests, report results.' There are no actual steps Claude can follow, no validation checkpoints, no error handling, and no concrete sequence of operations. The numbered steps are descriptions of intent, not actionable workflow steps. | 1 / 3 |
Progressive Disclosure | The content is organized into sections with headers, which provides some structure. However, there are no references to external files, no bundle files to support the content, and the inline content is mostly filler rather than appropriately split material. | 2 / 3 |
Total | 5 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Commit
13d35b8
- 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.