Skip to content
TrustedSkillsbeta
Back to all skills

Test Quality Inspector

Checked
bobmatnyc·vlatest·testing·MIT

Automatically assesses test suite quality, identifying gaps, redundancies, and potential improvements based on best practices.

Repository

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

  1. 1

    Run this in your project

    terminal
    $ npx skills add bobmatnyc/claude-mpm-skills --skill test-quality-inspector -a claude-code

  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

bobmatnyc

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.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

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 bobmatnyc/claude-mpm-skills at 718070a7d6.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Commit
718070a7d6
Manifest
universal/testing/test-quality-inspector/SKILL.md
Scanned
5 files, 1,321 lines
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

What it does

The test-quality-inspector skill enables AI agents to evaluate the effectiveness of software testing strategies and identify gaps in coverage. It analyzes existing test suites to determine if they adequately protect against potential failures in your application logic.

When to use it

  • Before deploying a new feature to production to ensure regression tests are sufficient.
  • When code reviews indicate complex logic that may lack adequate unit or integration testing.
  • To audit legacy codebases where test documentation is missing or outdated.
  • During sprint planning to estimate the effort required for comprehensive quality assurance.

Key capabilities

  • Analyzes current test coverage metrics against application requirements.
  • Identifies specific areas of code that are untested or under-tested.
  • Evaluates the robustness of existing testing frameworks and methodologies.
  • Provides actionable insights to improve overall software reliability.

Example prompts

  • "Analyze our current unit tests for the payment processing module and highlight any missing edge cases."
  • "Evaluate the effectiveness of our integration tests regarding the new user authentication flow."
  • "Identify gaps in our test suite that could lead to production failures during high-traffic events."

Tips & gotchas

Ensure your codebase includes sufficient metadata or comments for the AI agent to accurately map tests to specific functions. This skill works best when paired with a well-documented testing framework, as it relies on understanding the relationship between code and test cases to provide meaningful recommendations.