running-smoke-tests

tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill 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".

49%

Overall

Validation — 81%

Implementation — 7%

Activation — 85%

SKILL.md

Review

Evals

Validation

81%

Warnings & errors only

Criteria	Description	Result
metadata_version	'metadata' field is not a dictionary	Warning
license_field	'license' field is missing	Warning
body_output_format	No obvious output/return/format terms detected; consider specifying expected outputs	Warning

	Total	13 / 16 Passed

Implementation

This skill content describes what smoke testing is and when to use it, but fails to provide any actionable implementation details. It lacks executable code, actual test commands, configuration examples, or references to test suite definitions. The content reads like documentation about the concept rather than instructions Claude can follow.

Suggestions

Add executable commands showing how to actually run the smoke test suite (e.g., `pytest tests/smoke/ -v` or a specific script path)

Include the actual test suite configuration or reference a file containing test definitions that Claude should execute

Remove conceptual explanations ('What is a smoke test', 'When to use') and replace with concrete implementation: test file locations, expected output formats, and pass/fail criteria

Add error handling guidance: what to do when specific tests fail, how to interpret results, and next steps for common failure scenarios

Dimension	Reasoning	Score
Conciseness	The content is verbose and explains concepts Claude already knows (what smoke tests are, when to use them). It describes rather than instructs, with sections like 'How It Works' and 'When to Use' that add little actionable value.	1 / 3
Actionability	No concrete code, commands, or executable guidance is provided. The skill describes what will happen conceptually but never shows actual test commands, configuration files, or how to define/run the test suite.	1 / 3
Workflow Clarity	The 'How It Works' section lists abstract steps without any actual implementation details. There are no validation checkpoints, no error handling guidance, and no concrete sequence Claude can follow to execute tests.	1 / 3
Progressive Disclosure	The content is organized into logical sections with clear headers, but it's a monolithic description without references to actual test configurations, scripts, or detailed documentation that would be needed for implementation.	2 / 3
	Total	5 / 12 Passed

Activation

85%

This is a well-crafted skill description that clearly explains what the skill does (smoke testing for critical functionality) and when to use it (after deployments/upgrades). The description uses proper third-person voice and provides explicit trigger terms. The main weakness is limited trigger term coverage - it could benefit from additional natural language variations users might employ.

Suggestions

Expand trigger terms to include common variations like 'sanity check', 'health check', 'verify deployment', 'post-deployment test', or 'system verification'

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, executes test suites checking health/auth/features/integrations) AND when (after deployments, upgrades, or configuration changes) with explicit trigger terms provided.	3 / 3
Trigger Term Quality	Includes explicit triggers 'smoke test' and 'st', but missing common variations users might say like 'sanity check', 'health check', 'verify deployment', or 'post-deployment test'.	2 / 3
Distinctiveness Conflict Risk	Clear niche focused specifically on smoke testing with distinct triggers ('smoke test', 'st') and specific use cases (post-deployment verification); unlikely to conflict with general testing or other skills.	3 / 3
	Total	11 / 12 Passed

Reviewed

18 days ago

Table of Contents

Validation Implementation Activation

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.