OpenWork Desktop CDP Driver
different-ai/openwork
Drives a running OpenWork desktop window over CDP from the shell to evaluate JS, take screenshots, start sessions and send prompts for hand checks.
Resolves a reported discrepancy, defect, or regression by gathering expected versus actual behavior and passing the report into bounded shared execution, or by placing known larger or inconclusive…
Install Dough Bug Fixing
$ npx skills add terryyin/lizard --skill dough-bug-fixing -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install terryyin/lizard dough-bug-fixing --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-bug-fixing .claude/skills/dough-bug-fixing && 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-bug-fixing" agent skill from https://github.com/terryyin/lizard/tree/master/.agents/skills/dough-bug-fixing into .claude/skills/dough-bug-fixing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "dough-bug-fixing", 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-bug-fixingType 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-bug-fixing -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install terryyin/lizard dough-bug-fixing --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-bug-fixing .agents/skills/dough-bug-fixing && 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-bug-fixing" agent skill from https://github.com/terryyin/lizard/tree/master/.agents/skills/dough-bug-fixing into .agents/skills/dough-bug-fixing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "dough-bug-fixing", 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-bug-fixing -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install terryyin/lizard dough-bug-fixing --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-bug-fixing .cursor/skills/dough-bug-fixing && 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-bug-fixing" agent skill from https://github.com/terryyin/lizard/tree/master/.agents/skills/dough-bug-fixing into .cursor/skills/dough-bug-fixing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "dough-bug-fixing", 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-bug-fixing--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-bug-fixing -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install terryyin/lizard dough-bug-fixing --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-bug-fixing .gemini/skills/dough-bug-fixing && 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-bug-fixing" agent skill from https://github.com/terryyin/lizard/tree/master/.agents/skills/dough-bug-fixing into .gemini/skills/dough-bug-fixing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "dough-bug-fixing", 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-bug-fixingInstalls 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-bug-fixing -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-bug-fixing .github/skills/dough-bug-fixing && 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-bug-fixing" agent skill from https://github.com/terryyin/lizard/tree/master/.agents/skills/dough-bug-fixing into .github/skills/dough-bug-fixing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "dough-bug-fixing", 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-bug-fixing -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-bug-fixing --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-bug-fixing .opencode/skills/dough-bug-fixing && 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-bug-fixing" agent skill from https://github.com/terryyin/lizard/tree/master/.agents/skills/dough-bug-fixing into .opencode/skills/dough-bug-fixing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "dough-bug-fixing", 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-bug-fixing- GitHub stars
- 2.5k
- Token cost
- ~3.7k tokens
- SKILL.md length
- 1,811 words
- Files
- 2 (incl. scripts)
- Skills in repo
- 19
- Repo updated
- First seen
- Licence
- Custom licence
At a glance
Resolves a reported discrepancy, defect, or regression by gathering expected versus actual behavior and passing the report into bounded shared execution, or by placing known larger or inconclusive…
- Works in 6 steps: Reproduce before repair. Treat the… → Stable observable boundary. If the… → Useful expected-versus-actual assertion.… → …
- Unexpected behavior
- SKILL.md covers Stay in request authority, Admit the accepted mission, Gather the report and Investigate in an exploration…, plus 3 more sections
- Runs JavaScript scripts from its folder
What it does
Dough Bug Fixing is an agent skill from terryyin/lizard. Resolves a reported discrepancy, defect, or regression by gathering expected versus actual behavior and passing the report into bounded shared execution, or by placing known larger or inconclusive work first in this project's product backlog. Use for a bug report, defect, regression, broken or unexpected behavior, a mismatch between intended and actual results, or a larger or inconclusive bug that needs a first-priority story. Do not use for the word "fix" alone, a reporting-only request, or refinement-only work.
Its SKILL.md is about 3.7k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including scripts.
It sits in Testing & QA, covering Debugging and 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
- Unexpected behavior
- A mismatch between intended and actual results
- Inconclusive bug that needs a first-priority story
- The word fix alone
Example prompts
- “Use the dough-bug-fixing skill to resolve a reported discrepancy, defect, or regression by gathering expected versus actual behavior and passing the…”
- “/dough-bug-fixing”
Requirements
- Node.js
Workflow steps
6 steps, taken from the first numbered list in SKILL.md.
- Reproduce before repair. Treat the likely defect as a hypothesis until a
- Stable observable boundary. If the report matches an existing E2E
- Useful expected-versus-actual assertion. Assert observable output such as
- Absence needs a product contract. An absence assertion requires a product
- Smallest repair and related verification. After a confirmed failing
- Shared refactoring. Keep the existing pre-commit refactoring obligation.
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
Ships 1 file in scripts/ (JavaScript), which the agent can run.
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 Bug Fixing loads about 3.7k tokens when it runs. Until then it costs about 134 tokens; SKILL.md has 1,811 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); the scripts in this folder 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 1,811 words (~3,664 tokens).
“Gather the supplied report and investigate it without repairing the product. Close any standalone exploration workspace before invoking shared execution for an authorized bounded repair. Return an evidence-backed disposition to the coordinator. Route known larger work and incomplete or inconclusive…”
- name
- dough-bug-fixing
Files
SKILL.md and 1 other file (scripts) in .agents/skills/dough-bug-fixing of terryyin/lizard.
- SKILL.md
- scripts/retained-artifacts.mjs
Open the folder on GitHubat commit d5228c1
Compare with similar skills
Dough Bug Fixing 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 Bug Fixing this skillterryyin/lizard | 2.5k | — | ~3.7k | Automated safety check: Pass | Custom licence | |
| OpenWork Desktop CDP Driverdifferent-ai/openwork | 24k | — | ~465 | Automated safety check: Pass | Custom licence | |
| Issue Trackingstatic-web-server/static-web-server | 2.4k | — | ~1.5k | Automated safety check: Pass | Apache-2.0 | |
| Pipensx Bug Report Triagei3sey/pipensx | 221 | — | ~1.5k | Automated safety check: Notes | GPL-3.0 | |
| Structured Bug ReportsDonchitos/Claude-Code-Game-Studios | 26k | — | ~2.5k | Automated safety check: Notes | MIT | |
| Bug ReproducerAnastasiyaW/codex-claude-code-config | 154 | — | ~4.1k | Automated safety check: Pass | MIT |
Similar skills
Issue Tracking
static-web-server/static-web-server
Triage, reproduce, debug, and fix issues in the Static Web Server (SWS) project — bug reports, regressions, root-cause analysis, minimal fixes with regression tests, v2 backports, and security…
Pipensx Bug Report Triage
i3sey/pipensx
Decodes QR-code bug report photos and screenshots from the pipensx app into a log, then triages crashes and update, download or install failures.
Structured Bug Reports
Donchitos/Claude-Code-Game-Studios
Turns a description into a structured bug report, or scans code for likely bugs, then verifies and closes reports through four modes.
Bug Reproducer
AnastasiyaW/codex-claude-code-config
Find likely software bugs in a codebase, rank concrete bug candidates, and prove or reject them with focused regression tests before proposing a fix.
Plugin Testing
glittercowboy/plugin-freedom-system
Validates audio plugins through automated tests, pluginval, or manual DAW testing.
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 Bug Fixing
What does Dough Bug Fixing do?
Resolves a reported discrepancy, defect, or regression by gathering expected versus actual behavior and passing the report into bounded shared execution, or by placing known larger or inconclusive…. Dough Bug Fixing is an agent skill from terryyin/lizard. Resolves a reported discrepancy, defect, or regression by gathering expected versus actual behavior and passing the report into bounded shared execution, or by placing known larger or inconclusive work first in this project's product backlog.
When should I use Dough Bug Fixing?
Dough Bug Fixing fits situations like: unexpected behavior; A mismatch between intended and actual results; inconclusive bug that needs a first-priority story; the word fix alone.
How do I install Dough Bug Fixing in Claude Code?
Run `npx skills add terryyin/lizard --skill dough-bug-fixing -a claude-code`. Or copy the skill folder (.agents/skills/dough-bug-fixing in terryyin/lizard) into .claude/skills/dough-bug-fixing in your project. Claude Code loads it when a task matches its description.
How do I install Dough Bug Fixing in Codex?
Run `npx skills add terryyin/lizard --skill dough-bug-fixing -a codex`. Or copy the skill folder (.agents/skills/dough-bug-fixing in terryyin/lizard) into .agents/skills/dough-bug-fixing in your project. Codex loads it when a task matches its description.
Can I use Dough Bug Fixing 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-bug-fixing -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-bug-fixing, .gemini/skills/dough-bug-fixing, .github/skills/dough-bug-fixing and .opencode/skills/dough-bug-fixing in your project.
What does Dough Bug Fixing need to run?
Going by SKILL.md and its folder, Dough Bug Fixing needs JavaScript for the scripts in its folder. Our summary lists: Node.js.
Does Dough Bug Fixing 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 Bug Fixing 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. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.
What licence does Dough Bug Fixing use?
Dough Bug Fixing 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 Bug Fixing use?
About 3.7k tokens (SKILL.md is roughly 15k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Dough Bug Fixing?
Skills that share tags, products or a category with Dough Bug Fixing: OpenWork Desktop CDP Driver (different-ai/openwork, 24k stars), Issue Tracking (static-web-server/static-web-server, 2.4k stars), Pipensx Bug Report Triage (i3sey/pipensx, 221 stars) and Structured Bug Reports (Donchitos/Claude-Code-Game-Studios, 26k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Dough Bug Fixing?
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.