New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Test Quality Inspector

by bobmatnyc in bobmatnyc/claude-mpm

Verify that a test is actually testing what it claims to test: semantic correctness, mutation-style reasoning, and mock hygiene for any language or framework

Apache-2.0Auto-check passed

Install Test Quality Inspector

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

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install bobmatnyc/claude-mpm test-quality-inspector --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/bobmatnyc/claude-mpm.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/universal-testing-test-quality-inspector .claude/skills/test-quality-inspector && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
test-quality-inspector
GitHub stars
155
Token cost
~1.6k tokens
SKILL.md length
695 words
Files
6 (incl. references)
Skills in repo
51
Repo updated
First seen
Licence
Apache-2.0

At a glance

Verify that a test is actually testing what it claims to test: semantic correctness, mutation-style reasoning, and mock hygiene for any language or framework

  • Works in 5 steps: Read the Test → Read the Implementation → Apply the Five Checks → …
  • SKILL.md covers Overview, When to Use, Arguments and Five-Step Inspection Process, plus 4 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Test Quality Inspector is an agent skill from bobmatnyc/claude-mpm. Verify that a test is actually testing what it claims to test: semantic correctness, mutation-style reasoning, and mock hygiene for any language or framework

Its SKILL.md is about 1.6k tokens, which your agent loads only when the skill is triggered. The skill folder holds 6 other files, including reference files (for example `metadata.json`, `references/checks.md` and `references/mock-hygiene.md`). Compatibility notes: claude-code

The repository describes itself as: Claude Multi-Agent Project Manager — multi-channel orchestration, GitHub-first SDK mode, and plugin system for Claude. The licence is Apache-2.0.

Example prompts

  • “/test-quality-inspector”

Requirements

  • Compatibility (from SKILL.md): claude-code

Workflow steps

5 steps, taken from the step headings in SKILL.md.

  1. Read the Test
  2. Read the Implementation
  3. Apply the Five Checks
  4. Produce a Verdict
  5. Suggest Fixes

What it can do on your machine

Read from SKILL.md and the folder at commit 25203d3. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

  • Compatibility

    claude-code

    From compatibility in the SKILL.md frontmatter.

Context cost

Test Quality Inspector loads about 1.6k tokens when it runs, and up to ~8.3k if it reads all its reference files. Until then it costs about 45 tokens; SKILL.md has 695 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~45
When it runs · the whole SKILL.md, loaded when a task matches
~1.6k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~8.3k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from bobmatnyc/claude-mpm at commit 25203d3, republished under its Apache-2.0 licence (© bobmatnyc). 695 words, ~1,618 tokens.

Download SKILL.mdSave it as .claude/skills/test-quality-inspector/SKILL.md (or your agent's skills folder). This skill also uses 5 other files; get the full folder from GitHub.
name
test-quality-inspector
description
Verify that a test is actually testing what it claims to test: semantic correctness, mutation-style reasoning, and mock hygiene for any language or framework
compatibility
claude-code
user-invocable
true
disable-model-invocation
false
version
1.0.0
category
testing
license
Apache-2.0
tags
testing, quality-assurance, test-review, mutation-testing, mocking, semantic-correctness
progressive_disclosure.references
checks.md, verdicts.md, mock-hygiene.md, mutation-reasoning.md

Test Quality Inspector

Overview

A passing test is not the same as a good test. This skill inspects tests for semantic correctness — whether the test actually verifies the behavior it claims to verify, not just whether it runs without error.

Apply this skill to any test file or suite, in any language or framework.

When to Use

Activate when:

  • Reviewing a PR that includes new or modified tests
  • A test passes but a bug still shipped
  • Test names feel mismatched to their assertions
  • Mocks seem unusually extensive
  • Coverage numbers look good but confidence is low
  • Preparing to refactor and needing to trust the test harness

Arguments

This skill accepts optional arguments:

  • File path: path/to/test_file.py — inspect a specific file
  • Test name pattern: test_user_* — inspect tests matching the pattern
  • No args: inspect all tests in the current context or most recently discussed test

Five-Step Inspection Process

Step 1: Read the Test

Read the test file completely. Identify:

  • The test name and any docstring or description
  • What the test sets up (fixtures, mocks, data)
  • What action it performs (the "act")
  • What it asserts (the "assert")
  • What it does NOT assert
Step 2: Read the Implementation

Find and read the actual code being tested. Identify:

  • The function/method signature
  • All return values and side effects
  • Branches and edge cases in the implementation
  • What could realistically go wrong
Step 3: Apply the Five Checks

Run all five checks. See checks.md for detailed guidance.

Check 1 — Name-to-Assertion Alignment Does the test name describe what the assertions actually verify? A test named test_returns_empty_list_when_no_results that only asserts len(result) == 0 without checking the type is subtly misleading.

Check 2 — Meaningful Assertions (No Tautologies) Would the assertion pass even if the implementation returned garbage? Examples of hollow assertions:

  • assert result is not None when the function always returns an object
  • assert len(result) >= 0 (always true for lists)
  • assertTrue(True)

Check 3 — Mutation Failure Check If the implementation were deliberately broken in the most obvious way (wrong return value, off-by-one, missing branch), would this test catch it? Mentally apply one mutation at a time and ask: does the test fail?

Check 4 — Edge Case Coverage If the test name references edge cases ("when empty", "when None", "at boundary"), verify those conditions are actually set up in the arrange phase and exercised in the act phase.

Check 5 — Mock Hygiene Are mocks replacing so much real behavior that the test no longer exercises the code under test? Signs of hollow mocking:

  • The function under test is itself mocked
  • All dependencies are stubbed with hardcoded return values that match the assertion exactly
  • No real logic runs between the mock setup and the assertion
Show full SKILL.md (257 more words)Show less
Step 4: Produce a Verdict

Issue one of four verdicts with specific evidence. See verdicts.md for verdict criteria and templates.

VerdictMeaning
CORRECTTest accurately names its behavior, assertions are meaningful, would catch real bugs
MISLEADINGTest passes but the name or description does not match what is actually asserted
INCOMPLETETest covers some of the claimed behavior but misses important assertions or edge cases
BROKENTest would not catch an obvious bug in the code it claims to test
Step 5: Suggest Fixes

For any verdict other than CORRECT, provide:

  • The specific line(s) causing the issue
  • A concrete example of how to fix it
  • If applicable, an example of a bug the current test would fail to catch

Quick Check Summary

Would this test FAIL if I:
  - Changed the return value to None?        → Check assertions
  - Removed the main branch logic?           → Check coverage
  - Swapped two arguments in the call?       → Check specificity
  - Deleted the function entirely?           → Check mock depth
  - Added a new edge case to the spec?       → Check name accuracy

Red Flags — STOP and Inspect

Stop and apply full inspection when:

  • Test has no assertions (or only assert True)
  • Every dependency is mocked
  • Assertion checks a value that the mock itself returns
  • Test name mentions a condition that doesn't appear in the arrange phase
  • Test passes with an empty implementation
  • Multiple behaviors tested in one test with a vague name

Navigation

  • Checks Reference — Detailed guide for all five checks with examples in Python, JavaScript, Go, and Java
  • Verdicts and Templates — Verdict criteria, evidence format, and report templates
  • Mock Hygiene — When mocking is appropriate vs. when it hollows out a test
  • Mutation Reasoning — How to apply mutation-testing mindset without a mutation framework
  • universal-testing-test-driven-development — Write tests correctly from the start
  • universal-debugging-verification-before-completion — Verify your own work before claiming completion
  • universal-testing-testing-anti-patterns — Broader catalog of test design mistakes

© bobmatnyc, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 5 other files (references) in .claude/skills/universal-testing-test-quality-inspector of bobmatnyc/claude-mpm.

  • SKILL.md
  • metadata.json
  • references/checks.md
  • references/mock-hygiene.md
  • references/mutation-reasoning.md
  • references/verdicts.md

Open the folder on GitHubat commit 25203d3

Compare with similar skills

Test Quality Inspector next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Test Quality Inspector compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Test Quality Inspector this skillbobmatnyc/claude-mpm155—~1.6kAutomated safety check: PassApache-2.0
ActualizeNeoLabHQ/context-engineering-kit1.7k—~932Automated safety check: PassGPL-3.0
Skill InspectorNVIDIA/SkillSpector20k—~1.8kAutomated safety check: PassApache-2.0
Is This Actually Goodmohitagw15856/pm-claude-skills1.4k—~884Automated safety check: PassMIT
InspectorQinghongLin/data2story-skill156—~3.1kAutomated safety check: NotesMIT
Actual Budgetsundial-org/awesome-openclaw-skills663—~1.6kAutomated safety check: PassNone

Similar skills

  • Actualize

    NeoLabHQ/context-engineering-kit

    Reconcile the project's FPF state with recent repository changes

    1.7k GitHub stars~932 tokensUpdated 1 mo ago
    Knowledge ManagementAuto-check passed

  • Skill Inspector

    NVIDIA/SkillSpector

    Official

    Decides whether an agent skill is safe to install by combining a SkillSpector static scan with the agent's own source review, ending in APPROVE, CAUTION or REJECT.

    20k GitHub stars~1.8k tokensUpdated today
    SecurityAuto-check passed

  • Is This Actually Good

    mohitagw15856/pm-claude-skills

    Get an honest verdict on whether something you made is actually good — not the reflexive 'this is great!' but a real, criteria-based judgment.

    1.4k GitHub stars~884 tokensUpdated yesterday
    Auto-check passed

  • Inspector

    QinghongLin/data2story-skill

    Run sentence-level traceability verification on a Data2Story blog (verify.py - verifier.json), then emit the in-page Inspector panel (the reader-facing runnable verifier) + the verify/ artifacts…

    156 GitHub stars~3.1k tokensUpdated 3 mo ago
    Auto-check: notes

  • Actual Budget

    sundial-org/awesome-openclaw-skills

    Query and manage personal finances via the official Actual Budget Node.js API.

    663 GitHub stars~1.6k tokensUpdated 7 mo ago
    Business, Finance & HRAuto-check passed

  • Unity Inspector

    Besty0728/Unity-Skills

    Advise on Unity Inspector authoring UX

    1.8k GitHub stars~462 tokensUpdated yesterday
    Game DevelopmentAuto-check passed

More from bobmatnyc/claude-mpm

All 51 skills in this repo

  • Build MCP Server

    bobmatnyc/claude-mpm

    Create high-quality MCP servers that enable LLMs to effectively interact with external services.

    155 GitHub stars~2k tokensUpdated 1 mo ago
    Auto-check passed

  • Env Manager

    bobmatnyc/claude-mpm

    Environment variable validation, synchronization, and management across local development, CI/CD, and deployment platforms

    155 GitHub stars~2k tokensUpdated 1 mo ago
    Auto-check: notes

  • Session Analyzer

    bobmatnyc/claude-mpm

    Debug and teach agentic coding: a deterministic-first session timeline + cost report, with optional narrative polish and a standalone JSX visualiser.

    155 GitHub stars~2.2k tokensUpdated 1 mo ago
    Auto-check passed

  • Software Patterns

    bobmatnyc/claude-mpm

    Decision framework for architectural patterns including DI, SOA, Repository, Domain Events, Circuit Breaker, and Anti-Corruption Layer.

    155 GitHub stars~1.8k tokensUpdated 1 mo ago
    Auto-check passed

  • Verification Before Completion

    bobmatnyc/claude-mpm

    Run verification commands and confirm output before claiming success

    155 GitHub starsUsed in 2 repos~1k tokens
    Auto-check passed

  • Dependency Audit

    bobmatnyc/claude-mpm

    Dependency audit and cleanup workflow for maintaining healthy project dependencies.

    155 GitHub stars~3.5k tokensUpdated 1 mo ago
    Auto-check passed

Questions about Test Quality Inspector

What does Test Quality Inspector do?

Verify that a test is actually testing what it claims to test: semantic correctness, mutation-style reasoning, and mock hygiene for any language or framework. Test Quality Inspector is an agent skill from bobmatnyc/claude-mpm.

How do I install Test Quality Inspector in Claude Code?

Run `npx skills add bobmatnyc/claude-mpm --skill test-quality-inspector -a claude-code`. Or copy the skill folder (.claude/skills/universal-testing-test-quality-inspector in bobmatnyc/claude-mpm) into .claude/skills/test-quality-inspector in your project. Claude Code loads it when a task matches its description.

How do I install Test Quality Inspector in Codex?

Run `npx skills add bobmatnyc/claude-mpm --skill test-quality-inspector -a codex`. Or copy the skill folder (.claude/skills/universal-testing-test-quality-inspector in bobmatnyc/claude-mpm) into .agents/skills/test-quality-inspector in your project. Codex loads it when a task matches its description.

Can I use Test Quality Inspector in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add bobmatnyc/claude-mpm --skill test-quality-inspector -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/test-quality-inspector, .gemini/skills/test-quality-inspector, .github/skills/test-quality-inspector and .opencode/skills/test-quality-inspector in your project.

What does Test Quality Inspector need to run?

SKILL.md names no scripts, command-line tools or credentials: Test Quality Inspector is instructions for the agent only. Compatibility (from SKILL.md): claude-code.

Does Test Quality Inspector access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Test Quality Inspector safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Test Quality Inspector use?

Test Quality Inspector is published under the Apache-2.0 licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Test Quality Inspector use?

About 1.6k tokens (SKILL.md is roughly 6.5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 6.7k tokens, read only when the agent opens those files.

What are the alternatives to Test Quality Inspector?

Skills that share tags, products or a category with Test Quality Inspector: Actualize (NeoLabHQ/context-engineering-kit, 1.7k stars), Skill Inspector (NVIDIA/SkillSpector, 20k stars), Is This Actually Good (mohitagw15856/pm-claude-skills, 1.4k stars) and Inspector (QinghongLin/data2story-skill, 156 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Test Quality Inspector?

bobmatnyc (a GitHub user) maintains it in bobmatnyc/claude-mpm, which has 155 GitHub stars. The repository holds 51 skills in this directory. The repository was last updated on August 31, 2026.

Source: bobmatnyc/claude-mpm on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.