Testing

Validate and choose proportionate test proof for tests, CI, coverage, evals, and closeout evidence: map changed files to repo-native commands, place checks at commit, push, and pull-request gates, classify pass/fail/blocked ownership, and preserve trace/regression artifacts. Use when users ask what tests or gates to run, how to design coverage, why validation failed, or what proof supports a claim.

9 stars 4 forksTesting & QA

Install

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add jscraik/Agent-Skills --skill testing
Manual install
git clone --depth 1 https://github.com/jscraik/Agent-Skills.git /tmp/Agent-Skills
mkdir -p ~/.claude/skills
cp -r /tmp/Agent-Skills/Skills/agent-ops/testing ~/.claude/skills/testing

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# Testing

Select the smallest real proof that exercises the changed behavior, then widen only as the repo contract and risk surface require.

## When To Use

- Choose validation for code, docs, config, workflow, skill, or eval changes.
- Fix failing tests, classify validation ownership, or design coverage.
- Design or audit a repository's test layers and local/CI gate placement.
- Prove completion before handoff, PR, merge, release, or closeout claims.

## Inputs

- Target repo, changed files, nearest instructions, claim under test, repo
  command contracts, wrapper working directory, environment or credential
  materialization, prior failures, and known blockers.

## Outputs

- Exact commands with pass, fail, or blocked outcomes.
- Failure ownership plus the evidence artifact: log, trace, schema output, eval fixture, package receipt, or workflow-closeout receipt.
- Coverage gaps and next minimal diagnostic.
- When delivery is in scope, the validated report path, delivery receipt path,
  and exact command that checked each artifact.

## Workflow

1. Read the repo instructions and command contracts.
2. Inspect the changed behavior, existing tests or fixtures, and the canonical
   wrapper that owns them. Identify what is already proved, what rejection or
   boundary behavior is missing, and whether the wrapper changes into a package
   root or rewrites paths.
3. Name the exact invariant and proof lane: structural, deterministic behavior,
Read the full skill on GitHub

Details

Skill name
testing
Path
Skills/agent-ops/testing/SKILL.md
License
Apache-2.0
Repo updated
16 November 2026

FAQ

What does the Testing skill do?

Validate and choose proportionate test proof for tests, CI, coverage, evals, and closeout evidence: map changed files to repo-native commands, place checks at commit, push, and pull-request gates, classify pass/fail/blocked ownership, and preserve trace/regression artifacts. Use when users ask what tests or gates to run, how to design coverage, why validation failed, or what proof supports a claim.

How do I install the Testing skill?

skills CLI (Claude Code, Cursor, Codex and more): npx skills add jscraik/Agent-Skills --skill testing. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Testing popular?

It lives in jscraik/Agent-Skills, which has 9 GitHub stars and 4 forks.

Related skills

1password

9

jscraik/Agent-Skills

Plan, diagnose, and validate 1Password CLI workflows. Use when tasks need op CLI sign-in, secret references, op run, op inject, item reads, env injection, or service-account secret access.

Security

Agentation

9

jscraik/Agent-Skills

Audit, validate, and troubleshoot Agentation integrations in frontend apps. Use when annotations, MCP registration, endpoint sync, webhook delivery, or watch mode readiness are failing.

AI, LLMs & Agents

Agents Md

9

jscraik/Agent-Skills

Use when reviewing, creating, shrinking, or refactoring AGENTS.md and directly linked instruction guidance for stale or conflicting rules against current model documentation, scoped routing, deduplication, or progressive disclosure.

AI, LLMs & Agents

Pilot Event Replay

9

TeoSlayer/pilot-skills

Record and replay event streams for debugging, testing, and audit purposes. Use this skill when: 1. You need to capture event streams for later analysis 2. You need to replay events to test downstream consumers 3. You need to debug event-driven workflows 4. You need to audit event history with timestamps Do NOT use this skill when: - You need real-time event forwarding (use pilot-event-bus instead) - You need long-term storage with rotation (use pilot-event-log instead) - You need filtering before recording (use pilot-event-filter first)

Testing & QA

Murphyjitsu

5

EquiStamp/CFAR-Claude-Skills

CFAR rationality technique for bulletproofing plans by systematically imagining failure modes and creating defenses. Combines Murphy's Law with pre-mortem analysis. Use when the user: (1) has a plan they want to stress-test, (2) wants to identify what could go wrong before it does, (3) needs to build a more robust plan, (4) wants to practice pre-mortem thinking, or (5) is about to start a project and wants to anticipate obstacles. Triggers: "murphyjitsu", "what could go wrong", "pre-mortem", "stress test my plan", "inner simulator", "surprise-o-meter", "failure modes", "plan review", "CFAR".

Testing & QA

Pilot Quality Assurance Pipeline Setup

9

TeoSlayer/pilot-skills

Deploy a quality assurance pipeline with 3 agents that automate test generation, execution, and reporting. Use this skill when: 1. User wants to set up an automated QA or testing pipeline 2. User is configuring an agent as part of a test automation workflow 3. User asks about automating test generation, execution, or quality reporting across agents Do NOT use this skill when: - User wants to run a single test suite (use pilot-task-parallel instead) - User wants a one-off alert notification (use pilot-alert instead)

Testing & QA

Browse the most popular Claude skills, all testing & qa skills, or write your own with the skills generator.