Dogfood Exploratory QA
vercel-labs/agent-browser
Explores a web app with the agent-browser CLI to find bugs and UX problems, then writes a report with screenshots, repro videos and step-by-step reproduction for each issue.
Plans bounded manual or exploratory observation of requested product behavior when the developer explicitly requests manual testing, exploratory testing, or an active plan slice requires it.
Install Dough Manual Testing
$ npx skills add terryyin/lizard --skill dough-manual-testing -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install terryyin/lizard dough-manual-testing --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/terryyin/lizard.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/dough-manual-testing .claude/skills/dough-manual-testing && rm -rf skills-srcUse ~/.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/
Install the "dough-manual-testing" agent skill from https://github.com/terryyin/lizard/tree/master/.agents/skills/dough-manual-testing into .claude/skills/dough-manual-testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "dough-manual-testing", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/terryyin/lizard/tree/master/.agents/skills/dough-manual-testingType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add terryyin/lizard --skill dough-manual-testing -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install terryyin/lizard dough-manual-testing --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/terryyin/lizard.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/dough-manual-testing .agents/skills/dough-manual-testing && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "dough-manual-testing" agent skill from https://github.com/terryyin/lizard/tree/master/.agents/skills/dough-manual-testing into .agents/skills/dough-manual-testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "dough-manual-testing", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add terryyin/lizard --skill dough-manual-testing -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install terryyin/lizard dough-manual-testing --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/terryyin/lizard.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/dough-manual-testing .cursor/skills/dough-manual-testing && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "dough-manual-testing" agent skill from https://github.com/terryyin/lizard/tree/master/.agents/skills/dough-manual-testing into .cursor/skills/dough-manual-testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "dough-manual-testing", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/terryyin/lizard.git --path .agents/skills/dough-manual-testing--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add terryyin/lizard --skill dough-manual-testing -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install terryyin/lizard dough-manual-testing --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/terryyin/lizard.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/dough-manual-testing .gemini/skills/dough-manual-testing && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "dough-manual-testing" agent skill from https://github.com/terryyin/lizard/tree/master/.agents/skills/dough-manual-testing into .gemini/skills/dough-manual-testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "dough-manual-testing", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install terryyin/lizard dough-manual-testingInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add terryyin/lizard --skill dough-manual-testing -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/terryyin/lizard.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/dough-manual-testing .github/skills/dough-manual-testing && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "dough-manual-testing" agent skill from https://github.com/terryyin/lizard/tree/master/.agents/skills/dough-manual-testing into .github/skills/dough-manual-testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "dough-manual-testing", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add terryyin/lizard --skill dough-manual-testing -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install terryyin/lizard dough-manual-testing --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/terryyin/lizard.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/dough-manual-testing .opencode/skills/dough-manual-testing && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "dough-manual-testing" agent skill from https://github.com/terryyin/lizard/tree/master/.agents/skills/dough-manual-testing into .opencode/skills/dough-manual-testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "dough-manual-testing", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
dough-manual-testing- GitHub stars
- 2.5k
- Token cost
- ~995 tokens
- SKILL.md length
- 459 words
- Files
- 2 (incl. references)
- Skills in repo
- 19
- Repo updated
- First seen
- Licence
- Custom licence
At a glance
Plans bounded manual or exploratory observation of requested product behavior when the developer explicitly requests manual testing, exploratory testing, or an active plan slice requires it.
- Tasks that involve QA and bug reports
- SKILL.md covers Mission, Plan, Prepare and Explore, plus 1 more section
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Dough Manual Testing is an agent skill from terryyin/lizard. Plans bounded manual or exploratory observation of requested product behavior when the developer explicitly requests manual testing, exploratory testing, or an active plan slice requires it. Covers web, CLI, API, desktop, or combined surfaces. Does not run proactively or replace required automated tests.
Its SKILL.md is about 1000 tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including reference files (for example `references/exploration-workspace.md`).
It sits in Testing & QA, covering QA and bug reports. The repository describes itself as: A simple code complexity analyser without caring about the C/C++ header files or Java imports, supports most of the popular languages.
When your agent uses it
- Tasks that involve QA and bug reports
Example prompts
- “Use the dough-manual-testing skill to plan bounded manual or exploratory observation of requested product behavior when the developer explicitly…”
- “/dough-manual-testing”
What it can do on your machine
Read from SKILL.md and the folder at commit d5228c1. 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.
Context cost
Dough Manual Testing loads about 995 tokens when it runs, and up to ~2.5k if it reads all its reference files. Until then it costs about 82 tokens; SKILL.md has 459 words of instructions outside code blocks.
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
Its licence (Custom licence) doesn't allow us to republish the file, so here is its outline and opening line. It has 459 words (~995 tokens).
“Use only on explicit developer request or plan-slice manual testing. No diagnosis, product repair, or unrequested tooling.”
- name
- dough-manual-testing
Files
SKILL.md and 1 other file (references) in .agents/skills/dough-manual-testing of terryyin/lizard.
- SKILL.md
- references/exploration-workspace.md
Open the folder on GitHubat commit d5228c1
Compare with similar skills
Dough Manual Testing 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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Dough Manual Testing this skillterryyin/lizard | 2.5k | — | ~995 | Automated safety check: Pass | Custom licence | |
| Dogfood Exploratory QAvercel-labs/agent-browser | 44k | 8 repos | ~2.7k | Automated safety check: Pass | Apache-2.0 | |
| DeerFlow Smoke Testbytedance/deer-flow | 84k | — | ~2.5k | Automated safety check: Notes | MIT | |
| CodexBar Live QAsteipete/CodexBar | 22k | — | ~1.2k | Automated safety check: Pass | MIT | |
| Diagnose Playwright Failure as Product Bugappsmithorg/appsmith | 41k | — | ~1.5k | Automated safety check: Pass | Apache-2.0 | |
| Acceptance Evidence for Deliverieslobehub/lobehub | 83k | — | ~9.7k | Automated safety check: Pass | Apache-2.0 |
Similar skills
- Official
DeerFlow Smoke Test
bytedance/deer-flow
Walks through an end-to-end smoke test of a DeerFlow deployment: pull the latest code, deploy with Docker or locally, verify services, run health checks and write a report.
CodexBar Live QA
steipete/CodexBar
Runs live QA for the CodexBar app: provider usage matrix checks through its packaged CLI, config validation and menu checks, with 1Password-backed credentials handled safely.
Diagnose Playwright Failure as Product Bug
appsmithorg/appsmith
Investigates a stubbornly failing Playwright test as a possible product bug, using error output, screenshots, traces and server code, and writes a structured bug report.
Acceptance Evidence for Deliveries
lobehub/lobehub
Verifies a delivery end to end by driving the real product on a CLI, web, desktop or iOS Simulator surface, capturing evidence and publishing a round with the lh CLI.
Codex Plugin QA
code-yeongyu/oh-my-openagent
Tests the omo Codex plugin in an isolated CODEX_HOME with a local mock model, proving hooks fired through app-server notifications without touching ~/.codex.
More from terryyin/lizard
All 19 skills in this repoDough Execute Plan
terryyin/lizard
Executes one selected story or bounded retrospective correction through an executable plan, or one authorized planless slice from a selected simple story or a contextual instruction, with…
Dough Product Backlog
terryyin/lizard
Maintains and reprioritizes a product backlog list of canonical story or bounded-correction references, and records necessary blocking story dependencies in canonical homes.
Dough Execution Retrospective
terryyin/lizard
Reviews planned, completed planless quick, or quick-to-planned execution against original intent, aggregate commits, current whole-product architecture, and tests, including after cleanup.
Dough Land
terryyin/lizard
Dough Land lands everything in one reviewed checkout on the authorized remote trunk: commits all of its changes, reconciles and publishes them without force, and refreshes a supplied default…
Dough Story Refinement
terryyin/lizard
Clarifies selected stories before execution planning by establishing goal, scope, and key examples in each story's seed, distinguishing promises from rejection constraints.
Dough Story Wrap Up
terryyin/lizard
Closes one completed feature story, bounded retrospective correction, or context-only planless execution using available execution context.
Related
Categories
Questions about Dough Manual Testing
What does Dough Manual Testing do?
Plans bounded manual or exploratory observation of requested product behavior when the developer explicitly requests manual testing, exploratory testing, or an active plan slice requires it. Dough Manual Testing is an agent skill from terryyin/lizard. Plans bounded manual or exploratory observation of requested product behavior when the developer explicitly requests manual testing, exploratory testing, or an active plan slice requires it.
When should I use Dough Manual Testing?
Dough Manual Testing fits situations like: tasks that involve QA and bug reports.
How do I install Dough Manual Testing in Claude Code?
Run `npx skills add terryyin/lizard --skill dough-manual-testing -a claude-code`. Or copy the skill folder (.agents/skills/dough-manual-testing in terryyin/lizard) into .claude/skills/dough-manual-testing in your project. Claude Code loads it when a task matches its description.
How do I install Dough Manual Testing in Codex?
Run `npx skills add terryyin/lizard --skill dough-manual-testing -a codex`. Or copy the skill folder (.agents/skills/dough-manual-testing in terryyin/lizard) into .agents/skills/dough-manual-testing in your project. Codex loads it when a task matches its description.
Can I use Dough Manual Testing 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 terryyin/lizard --skill dough-manual-testing -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/dough-manual-testing, .gemini/skills/dough-manual-testing, .github/skills/dough-manual-testing and .opencode/skills/dough-manual-testing in your project.
What does Dough Manual Testing need to run?
SKILL.md names no scripts, command-line tools or credentials: Dough Manual Testing is instructions for the agent only.
Does Dough Manual Testing 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 Dough Manual Testing 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 Dough Manual Testing use?
Dough Manual Testing has a licence file (the repository's licence) that doesn't match a standard licence. Read it on GitHub before reusing the skill.
How many tokens does Dough Manual Testing use?
About 995 tokens (SKILL.md is roughly 4k 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 1.5k tokens, read only when the agent opens those files.
What are the alternatives to Dough Manual Testing?
Skills that share tags, products or a category with Dough Manual Testing: Dogfood Exploratory QA (vercel-labs/agent-browser, 44k stars), DeerFlow Smoke Test (bytedance/deer-flow, 84k stars), CodexBar Live QA (steipete/CodexBar, 22k stars) and Diagnose Playwright Failure as Product Bug (appsmithorg/appsmith, 41k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Dough Manual Testing?
terryyin (a GitHub user) maintains it in terryyin/lizard, which has 2,550 GitHub stars. The repository holds 19 skills in this directory. The repository was last updated on October 6, 2026.
Source: terryyin/lizard on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.