Vibe Testing

This skill should be used when the user asks to "test my specs", "validate my design docs", "find gaps in my architecture", "stress-test the spec", "vibe test", "pressure test the docs", or mentions spec validation before implementation begins.

24 stars 2 forksTesting & QA

Install

skills CLI (Claude Code, Cursor, Codex and more)

npx skills add knot0-com/vibe-testing --skill vibe-testing

Manual install

git clone --depth 1 https://github.com/knot0-com/vibe-testing.git /tmp/vibe-testing
mkdir -p ~/.claude/skills
cp -r /tmp/vibe-testing/. ~/.claude/skills/vibe-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

# Vibe Testing

## Overview

Vibe testing validates specification documents by simulating real-world scenarios against them using LLM reasoning. Instead of writing code or test harnesses, write **natural-language scenarios** that exercise cross-cutting slices of the spec surface — then trace execution step-by-step, flagging gaps, conflicts, and ambiguities.

**Core principle:** If a realistic user scenario cannot be fully traced through the specs, the specs are incomplete.

**Best used:** After specs are written, before implementation begins.

## When to Use

- Spec docs exist but no implementation yet — validate before building
- After major spec changes — regression-test for new gaps
- Before implementation planning — find blocking gaps early
- Specs span multiple documents — test cross-doc coherence
- Designing for multiple deployment contexts — test each context separately

**When NOT to use:**

- Single-file specs with obvious scope — just review manually
- Implementation bugs — use actual tests
- API contract validation — use schema validation tools

## Core Method

```
1. GATHER — Read all spec docs in the target directory
2. SCENARIOS — Write 3-5 vibe test cases (personas + goals + environments)
3. SIMULATE — Trace each scenario step-by-step against the specs
4. CLASSIFY — Tag findings as GAP / CONFLICT / AMBIGUITY
5. SEVERITY — Rate as BLOCKING / DEGRADED / COSMETIC
6. REPORT — Produce gap summary + spec coverage matrix
```

## Writing a Vibe Test Case

Read the full skill on GitHub

Details

Skill name: vibe-testing
Repository: knot0-com/vibe-testing
License: MIT
Repo updated: 22 March 2026
Listed in: heilcheng/awesome-agent-skills

FAQ

What does the Vibe Testing skill do?

How do I install the Vibe Testing skill?

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

Is Vibe Testing popular?

It lives in knot0-com/vibe-testing, which has 24 GitHub stars and 2 forks, and is included in 1 curated skill list.

Related skills

Premortem

b1rdmania/claude-premortem-skill

Run a premortem on any plan, launch, product, hire, strategy, or decision. Imagines it failed 6 months from now, works backward to find every reason why, then produces a revised plan. Triggers include "premortem this", "premortem my", "what could kill this", "stress test this plan", "find the blind spots", "poke holes in this", "where will this break", "am I missing anything", "what could go wrong", "future-proof this", "devil's advocate this".

Testing & QA

Trip Planner

skywain/trip-planner-skill

End-to-end international trip planning: turns "I want to go to X for N days" into a verified, bookable plan — route skeleton across cities, flight price scans (international + domestic legs), train-vs-fly decisions, hour-by-hour daily timelines with opening hours, dwell times, holiday collisions and tappable turn-by-turn map links (小时级行程+地图导航+离线KML), hotel shortlists by neighborhood, budget rollup, and a booking checklist with deep links. Use this whenever the user asks to plan a trip, vacation, itinerary or honeymoon, compare flight dates/prices, pick between cities or routes, schedule a trav

Testing & QA

Molt Dex

ReSo7200/molt-dex

Reverse-engineer and assess Android apps, from unobfuscated to heavily obfuscated, using a staged, evidence-first pipeline built on apktool, adb and scrcpy. Use when the user wants to understand how an APK is built, what it does, where its secrets and misconfigurations are, or wants to drive an app on a device to observe its behaviour. Dynamic testing (anything that touches a running system or backend) is authorization-gated and must be in scope.

Testing & QA

Econometrics

xiaomihu1992/econometrics-skill

Causal inference and applied econometric analysis on tabular data, from uploaded-data diagnostics and cleaning advice to treatment-effect estimation and publication-grade applied research design. Use for policy impact, ATE/ATT/LATE/ITT, OLS, propensity scores, IV/2SLS, DID/event studies, RDD, robustness checks, falsification tests, identification memos, 因果推断, 政策评估, 数据清洗建议, 稳健性检验, and 异质性分析.

Testing & QA

Sketch Narrator

qingyabailu-git/SketchNarrator

从中文主题、文案、视频链接、本地音视频或参考角色制作带自然配音、真实音频时间、分区笔迹和内部成片 QA 的完整手绘讲解视频。适用于素材转口播、黑板讲解、白板科普、故事口播和系列 IP 手绘视频；不用于纯 AI 视频模型生成或复杂 Web 工作台建设。

Testing & QA

Pc Control

AnubhavChaturvedi-GitHub/PC-Automation

Hands on the local Mac for any agent - system state (battery, volume, brightness, IP), app launch/quit, open websites and YouTube, media and browser control via keystrokes, screenshots, clipboard, notifications, TTS, and honest mic/speaker hardware tests. Use whenever the user asks to control the computer, change volume or brightness, open an app or site, play or pause media, check battery/IP/running apps, take a screenshot, or test the mic or speakers. Rebuilt from the PC-Automation repo: the agent is the intent brain; this skill is only the hands.

Testing & QA

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