Test Quality Analysis
CheckedHelps with testing, analysis as part of testing, debugging, and quality assurance workflows.
Install on your platform
Showing Claude Code. One command installs this skill into any of the agents below.
- 1
Run this in your project
terminal$ npx skills add secondsky/claude-skills --skill test-quality-analysis -a claude-code Uses the open-source
skillsCLI and needs Node.js. Add-gto install it for your user instead of this project.
What we know about this skill
Publisher
secondsky
Taken from the source listing. We haven't verified who controls this account.
Install target
Live repository
Not pinned. Installing fetches whatever the repository holds at the time you run the command.
Automated safety checks
This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.
Declares what it does: passed
SKILL.md parses and declares a name and a description.
SKILL.md exists, its frontmatter parses, and it declares a name and a description.
No undeclared network calls: passed
Makes no network calls.
Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.
No obfuscated payloads: passed
No encoded or obfuscated payloads.
No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.
No credential access: passed
Reads no keys, tokens, keychains or credential files.
Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.
No pipe-to-shell installers: passed
No pipe-to-shell or download-and-run installers.
No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.
Pinned to a commit: passed
Scanned secondsky/claude-skills at 8837836131.
The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.
- Commit
- 8837836131
- Scanned
- 1 file, 175 lines
About this skill
What it does
This skill provides expert knowledge for analyzing and improving test quality within a software development workflow. It helps identify common testing problems like overmocking, fragile tests, flaky tests, and poor assertions – often referred to as “test smells.” The skill focuses on detecting these issues and suggesting fixes to improve the correctness, reliability, maintainability, performance, coverage, and isolation of your tests.
When to use it
- When reviewing existing test suites for potential improvements.
- During code reviews to identify and address testing anti-patterns.
- To diagnose why tests are failing intermittently (flaky tests).
- When refactoring tests that break frequently with minor code changes (fragile tests).
Key capabilities
- Test Smell Detection: Identifies overmocking, fragile tests, flaky tests, and poor assertions.
- Problem Explanation: Provides descriptions of the issues caused by each test smell.
- Code Examples: Illustrates bad coding practices and suggests improved alternatives.
- Focus Areas: Guides users to focus on correctness, reliability, maintainability, performance, coverage, and isolation in their testing efforts.
Example prompts
- "Analyze this test code for potential overmocking issues: [paste test code here]"
- "Why is this test fragile? [paste test code here]"
- "How can I fix this flaky test? [paste test code here]"
Tips & gotchas
- The skill identifies "test smells," which are indicators of potential problems, not guaranteed errors. Further investigation may be needed.
- The detection threshold for overmocking is generally more than 3-4 mocks.