Dev Issue
hmislk/hmis
Run a GitHub issue through its full lifecycle end-to-end: investigate, discuss the approach, gather test context (department/data), implement, rebuild + local redeploy, verify with Playwright and…
Set a repo up to prove engineering-task work actually works before it ships.
$ npx skills add AI-Builder-Club/skills --skill verifier-setup -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install AI-Builder-Club/skills verifier-setup --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/AI-Builder-Club/skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/verifier-setup .claude/skills/verifier-setup && 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 "verifier-setup" agent skill from https://github.com/AI-Builder-Club/skills/tree/main/skills/verifier-setup into .claude/skills/verifier-setup/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "verifier-setup", 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/AI-Builder-Club/skills/tree/main/skills/verifier-setupType 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 AI-Builder-Club/skills --skill verifier-setup -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install AI-Builder-Club/skills verifier-setup --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/AI-Builder-Club/skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/verifier-setup .agents/skills/verifier-setup && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "verifier-setup" agent skill from https://github.com/AI-Builder-Club/skills/tree/main/skills/verifier-setup into .agents/skills/verifier-setup/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "verifier-setup", 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 AI-Builder-Club/skills --skill verifier-setup -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install AI-Builder-Club/skills verifier-setup --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/AI-Builder-Club/skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/verifier-setup .cursor/skills/verifier-setup && 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 "verifier-setup" agent skill from https://github.com/AI-Builder-Club/skills/tree/main/skills/verifier-setup into .cursor/skills/verifier-setup/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "verifier-setup", 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/AI-Builder-Club/skills.git --path skills/verifier-setup--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 AI-Builder-Club/skills --skill verifier-setup -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install AI-Builder-Club/skills verifier-setup --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/AI-Builder-Club/skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/verifier-setup .gemini/skills/verifier-setup && 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 "verifier-setup" agent skill from https://github.com/AI-Builder-Club/skills/tree/main/skills/verifier-setup into .gemini/skills/verifier-setup/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "verifier-setup", 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 AI-Builder-Club/skills verifier-setupInstalls 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 AI-Builder-Club/skills --skill verifier-setup -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/AI-Builder-Club/skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/verifier-setup .github/skills/verifier-setup && 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 "verifier-setup" agent skill from https://github.com/AI-Builder-Club/skills/tree/main/skills/verifier-setup into .github/skills/verifier-setup/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "verifier-setup", 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 AI-Builder-Club/skills --skill verifier-setup -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install AI-Builder-Club/skills verifier-setup --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/AI-Builder-Club/skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/verifier-setup .opencode/skills/verifier-setup && 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 "verifier-setup" agent skill from https://github.com/AI-Builder-Club/skills/tree/main/skills/verifier-setup into .opencode/skills/verifier-setup/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "verifier-setup", 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.
verifier-setupSet a repo up to prove engineering-task work actually works before it ships.
Verifier Setup is an agent skill from AI-Builder-Club/skills. Set a repo up to prove engineering-task work actually works before it ships. Investigates the repo, ensures a one-command dev stack (dev-local) exists, asks whether verification runs locally or in a sandbox (crabbox), confirms/installs the driver (the playwright-cli skill for web by default). Outputs three artifacts: a committed /verify skill (per-task verification SOP — spawn a verifier sub-agent → drive the app → screenshot/video proof → open a PR with the proof embedded), the /dev-local skill + script, and the…
Its SKILL.md is about 2.1k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including assets (for example `assets/verify.template.md`).
It sits in Testing & QA, covering Operations and SOPs, Pull requests and Subagents. It works with Playwright. The repository describes itself as: Codebase harness + loop engineer.
7 steps, taken from the step headings in SKILL.md.
Read from SKILL.md and the folder at commit 917780c. It shows what the files ask for, not the result of running them.
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.
Shell commands in SKILL.md call:
ghFrom the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md. Its commands use gh, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Verifier Setup loads about 2.1k tokens when it runs. Until then it costs about 172 tokens; SKILL.md has 1,059 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.
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.
Without a licence we can't republish the file, so here is its outline and opening line. It has 1,059 words (~2,082 tokens).
“Goal: leave the repo able to prove an engineering task works before it ships — run once, and it wires up everything the per-task /verify loop needs.”
SKILL.md and 1 other file (assets) in skills/verifier-setup of AI-Builder-Club/skills.
Open the folder on GitHubat commit 917780c
Verifier Setup 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 |
|---|---|---|---|---|---|---|
| Verifier Setup this skillAI-Builder-Club/skills | 1.3k | — | ~2.1k | Automated safety check: Pass | None | |
| Dev Issuehmislk/hmis | 236 | — | ~5.1k | Automated safety check: Pass | GPL-3.0 | |
| Playwright Screen Recordingliaohch3/claude-tap | 3.3k | — | ~714 | Automated safety check: Pass | MIT | |
| Bangle Followup Operatorbangle-io/bangle-io | 1.2k | — | ~991 | Automated safety check: Pass | AGPL-3.0 | |
| QAKiln-AI/Kiln | 5.2k | — | ~3.6k | Automated safety check: Pass | Custom licence | |
| Take Screenshotsankitvgupta/exo | 495 | — | ~1.2k | Automated safety check: Pass | Custom licence |
hmislk/hmis
Run a GitHub issue through its full lifecycle end-to-end: investigate, discuss the approach, gather test context (department/data), implement, rebuild + local redeploy, verify with Playwright and…
liaohch3/claude-tap
Records headless Playwright sessions as .webm videos to show a bug fix working or to give pull request reviewers visual evidence.
bangle-io/bangle-io
Operate recurring Bangle.io agent follow-ups after a thread has already started.
Kiln-AI/Kiln
Multi-agent, browser-driven QA pass over a branch or PR — scope it, plan it, fan out one subagent per testing area in its own isolated sandbox, compile a severity-ranked markdown report.
ankitvgupta/exo
Capture screenshots of the Exo Electron app workflows using Playwright in demo mode.
lablup/backend.ai-webui
Record Playwright e2e tests as one GIF per test case (video → ffmpeg palette GIF) and return a markdown table for a PR description.
AI-Builder-Club/skills
Create animated flow diagrams from articles, workflow notes, architecture sketches, or process descriptions using a JSON specification and a local Python/Pillow renderer.
AI-Builder-Club/skills
Generate TikTok/Shorts-style karaoke captions using MLX Whisper, ASS subtitles, and FFmpeg libass.
AI-Builder-Club/skills
Delegate tasks to ANY CLI agent (claude, codex, aider, ...) running in a detached tmux session, with a race-safe done-signal protocol and multi-turn iteration.
AI-Builder-Club/skills
Spin up a new loop (domain) in a file-based knowledge base — bootstrap the substrate if it's missing, gather the loop's charter, scaffold domains/<loop/README.md, then do ONE real test run and…
AI-Builder-Club/skills
Scaffold an isolated CLOUD dev box per agent (via crabbox + Daytona) for any codebase — the parallel-safe counterpart to dev-local-setup.
AI-Builder-Club/skills
A skill your agent uses when deciding WHERE to point SEO effort, not how to write a page.
Works with
Set a repo up to prove engineering-task work actually works before it ships. Verifier Setup is an agent skill from AI-Builder-Club/skills. Set a repo up to prove engineering-task work actually works before it ships.
Verifier Setup fits situations like: someone says set up verification; make this repo verifiable; scaffold a verify skill; set up the verifier.
Run `npx skills add AI-Builder-Club/skills --skill verifier-setup -a claude-code`. Or copy the skill folder (skills/verifier-setup in AI-Builder-Club/skills) into .claude/skills/verifier-setup in your project. Claude Code loads it when a task matches its description.
Run `npx skills add AI-Builder-Club/skills --skill verifier-setup -a codex`. Or copy the skill folder (skills/verifier-setup in AI-Builder-Club/skills) into .agents/skills/verifier-setup in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add AI-Builder-Club/skills --skill verifier-setup -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/verifier-setup, .gemini/skills/verifier-setup, .github/skills/verifier-setup and .opencode/skills/verifier-setup in your project.
Going by SKILL.md and its folder, Verifier Setup needs the command-line tools its instructions call (gh). Our summary lists: Node.js; Docker.
SKILL.md contains no URLs. Its commands use gh, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
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.
No licence was found for Verifier Setup or its repository. Without one, default copyright applies: ask the author before reusing or redistributing it.
About 2.1k tokens (SKILL.md is roughly 8.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Verifier Setup: Dev Issue (hmislk/hmis, 236 stars), Playwright Screen Recording (liaohch3/claude-tap, 3.3k stars), Bangle Followup Operator (bangle-io/bangle-io, 1.2k stars) and QA (Kiln-AI/Kiln, 5.2k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
AI-Builder-Club (a GitHub organization) maintains it in AI-Builder-Club/skills, which has 1,288 GitHub stars. The repository holds 11 skills in this directory. The repository was last updated on September 15, 2026.
Source: AI-Builder-Club/skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.