Agent skill

Verify

by team-attention in team-attention/hoyeon

Run a full implementation verification pass after code or data changes.

MITAuto-check passedTesting & QA

Install Verify

skills CLI

$ npx skills add team-attention/hoyeon --skill verify -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install team-attention/hoyeon verify --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/team-attention/hoyeon.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/verify .claude/skills/verify && rm -rf skills-src

Use ~/.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/

Paste into Claude Code

Install the "verify" agent skill from https://github.com/team-attention/hoyeon/tree/main/skills/verify into .claude/skills/verify/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "verify", 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

$skill-installer install https://github.com/team-attention/hoyeon/tree/main/skills/verify

Type 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.

skills CLI

$ npx skills add team-attention/hoyeon --skill verify -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install team-attention/hoyeon verify --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/team-attention/hoyeon.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/verify .agents/skills/verify && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "verify" agent skill from https://github.com/team-attention/hoyeon/tree/main/skills/verify into .agents/skills/verify/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "verify", 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.

skills CLI

$ npx skills add team-attention/hoyeon --skill verify -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install team-attention/hoyeon verify --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/team-attention/hoyeon.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/verify .cursor/skills/verify && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "verify" agent skill from https://github.com/team-attention/hoyeon/tree/main/skills/verify into .cursor/skills/verify/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "verify", 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

$ gemini skills install https://github.com/team-attention/hoyeon.git --path skills/verify

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add team-attention/hoyeon --skill verify -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install team-attention/hoyeon verify --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/team-attention/hoyeon.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/verify .gemini/skills/verify && rm -rf skills-src

Use ~/.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/

Paste into Gemini CLI

Install the "verify" agent skill from https://github.com/team-attention/hoyeon/tree/main/skills/verify into .gemini/skills/verify/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "verify", 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.

GitHub CLI

$ gh skill install team-attention/hoyeon verify

Installs 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).

skills CLI

$ npx skills add team-attention/hoyeon --skill verify -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/team-attention/hoyeon.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/verify .github/skills/verify && rm -rf skills-src

Use ~/.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/

Paste into GitHub Copilot

Install the "verify" agent skill from https://github.com/team-attention/hoyeon/tree/main/skills/verify into .github/skills/verify/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "verify", 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.

skills CLI

$ npx skills add team-attention/hoyeon --skill verify -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install team-attention/hoyeon verify --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/team-attention/hoyeon.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/verify .opencode/skills/verify && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "verify" agent skill from https://github.com/team-attention/hoyeon/tree/main/skills/verify into .opencode/skills/verify/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "verify", 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: verify
GitHub stars: 173
Token cost: ~1.2k tokens
SKILL.md length: 578 words
Files: 1
Skills in repo: 36
Repo updated: May 21, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

Run a full implementation verification pass after code or data changes.

Works in 7 steps: Define Mission → Inspect Repo Verification Surface → Run Command Verification → …
The user asks to verify
SKILL.md covers Role, Workflow, Report Artifact Shape and Verdict Policy
Calls pnpm

What it does

Verify is an agent skill from team-attention/hoyeon. Run a full implementation verification pass after code or data changes. Use when the user asks to verify, QA, smoke test, run checks, validate a feature, inspect a local app in the browser, capture screenshots, or turn discovered QA issues into regression tests/checklists with user approval.

Its SKILL.md is about 1.2k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Testing & QA, covering QA and bug reports. It works with pnpm. The repository describes itself as: Requirements-first Harness — derive, verify, execute. The licence is MIT.

When your agent uses it

The user asks to verify
Validate a feature
Inspect a local app in the browser
Capture screenshots

Example prompts

“/verify”

Workflow steps

7 steps, taken from the step headings in SKILL.md.

Define Mission
Inspect Repo Verification Surface
Run Command Verification
Run Browser QA
Classify Findings
Update Verification Assets With Approval
Report

What it can do on your machine

Read from SKILL.md and the folder at commit 7cff032. 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
Shell commands in SKILL.md call:
- pnpm
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use pnpm, which can reach the network depending on how they are called.
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

Verify loads about 1.2k tokens when it runs. Until then it costs about 75 tokens; SKILL.md has 578 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~75
When it runs · the whole SKILL.md, loaded when a task matches: ~1.2k

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

The full file from team-attention/hoyeon at commit 7cff032, republished under its MIT licence (© team-attention). 578 words, ~1,216 tokens.

Download SKILL.mdSave it as .claude/skills/verify/SKILL.md (or your agent's skills folder).

name: verify
description: Run a full implementation verification pass after code or data changes. Use when the user asks to verify, QA, smoke test, run checks, validate a feature, inspect a local app in the browser, capture screenshots, or turn discovered QA issues into regression tests/checklists with user approval.

verify

Use this skill as a quality gate after implementation. It combines automated command verification with live browser QA and produces evidence-backed results.

Role

You are a verification agent, not an implementation agent.

Default behavior:

Run static and command checks.
Use chromux for browser QA when available.
Capture screenshots and concrete evidence.
Report pass/fail, risks, and reproducible issues.
Do not change production code while verifying.

Allowed after explicit user approval:

Add or update regression tests.
Add or update verification scripts.
Add or update .hoyeon/verify/* profile/checklist/report artifacts.
Record known issues and reproduction steps.

Do not fix product code in this skill. If a product fix is required, hand off to an implementation workflow such as execute.

Workflow

1. Define Mission

Extract the verification target from the user request:

Feature or behavior being verified.
Expected outcome.
Relevant app URL, command, or route.
Any specific user acceptance criteria.

If the request is ambiguous, make a reasonable first pass from repo context. Ask only when the missing detail prevents verification.

2. Inspect Repo Verification Surface

Read the smallest useful context:

package.json
existing test/e2e scripts
existing verification scripts
.hoyeon/verify/profile.json or .hoyeon/verify/checklist.md if present
app startup docs or env hints only when needed

Prefer existing repo commands over inventing new ones.

3. Run Command Verification

Run applicable checks, usually in this order:

install/dependency sanity if needed
lint/static analysis
typecheck
build
unit/integration tests
existing e2e or smoke scripts

For JavaScript/TypeScript repos, common commands are:

pnpm lint
pnpm typecheck
pnpm build
pnpm test
pnpm test:e2e
pnpm verify

Do not assume all commands exist. Inspect scripts first.

4. Run Browser QA

Use chromux when available. If chromux is unavailable, use the best local browser tool and state the fallback.

Browser QA should exercise the actual user flow, not only page load:

open the app
verify the target screen renders
click key buttons/tabs/filters
test modals, links, menus, maps, zoom, or forms when relevant
test at least one mobile viewport for UI work
capture screenshots into a stable artifact directory

Default screenshot directory:

text

artifacts/screenshots/

If the repo has .hoyeon/verify/profile.json, follow its URL, command, and scenario hints.

Show full SKILL.md (228 more words)Show less

5. Classify Findings

Classify every issue:

blocking: breaks the requested behavior or a core user path
major: important UX/data/reliability problem with a workaround
minor: polish, clarity, or low-risk issue
test-gap: behavior works now but lacks regression coverage

For each finding include:

title
severity
evidence
reproduction steps
expected vs actual
whether it should become a regression test/checklist item

6. Update Verification Assets With Approval

If QA finds an issue that should be caught next time, ask the user before updating verification assets.

Approval-gated updates may include:

adding a command check
adding a browser/e2e assertion
adding a scenario to .hoyeon/verify/checklist.md
updating .hoyeon/verify/profile.json
recording a known issue under .hoyeon/verify/runs/<timestamp>/

Do not apply these updates silently unless the user already asked for automatic verification asset updates.

7. Report

Final response should be concise and evidence-backed:

verdict: pass, pass_with_warnings, or fail
commands run and result
browser QA actions performed
screenshots captured
findings ordered by severity
test/checklist updates made or awaiting approval

If checks were not run, say exactly why.

Report Artifact Shape

When writing artifacts, prefer:

text

.hoyeon/verify/
  profile.json
  checklist.md
  runs/
    YYYY-MM-DD-HHMMSS/
      report.md
      findings.json
      command-log.md
      screenshots/

Keep .hoyeon/verify/latest-report.md as a copy or short pointer to the newest run when useful.

Verdict Policy

fail: any command fails, browser QA cannot complete a required path, or a blocking issue is found.
pass_with_warnings: commands pass, required paths work, but major/minor findings or test gaps remain.
pass: commands pass, browser QA passes, and no material findings remain.

Files

Just SKILL.md in skills/verify of team-attention/hoyeon.

Open the folder on GitHubat commit 7cff032

Compare with similar skills

Verify 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.

Verify compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Verify this skillteam-attention/hoyeon	173	—	~1.2k	Automated safety check: Pass	MIT	4 mo ago
DeerFlow Smoke Testbytedance/deer-flow	83k	—	~2.5k	Automated safety check: Notes	MIT	today
OpenWork Desktop CDP Driverdifferent-ai/openwork	24k	—	~465	Automated safety check: Pass	Custom licence	today
Desktop Dual Repo TestEynzof/Hermes-CN-Desktop	1.7k	—	~1.8k	Automated safety check: Pass	Custom licence	17 days ago
Ya Runkzahel/yepanywhere	533	—	~957	Automated safety check: Pass	MIT	today
OpenWork Electron Browser Automationdifferent-ai/openwork	24k	—	~780	Automated safety check: Pass	Custom licence	today

Similar skills

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.
83k GitHub stars~2.5k tokensUpdated today
Testing & QAAuto-check: notes
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.
24k GitHub stars~465 tokensUpdated today
Testing & QAAuto-check passed
Desktop Dual Repo Test
Eynzof/Hermes-CN-Desktop
A skill your agent uses when starting or verifying Hermes Agent CN Desktop with the latest Hermes-CN-Desktop and Hermes-CN-Core branches — dev smoke test (pnpm tauri:dev), packaged beta/release…
1.7k GitHub stars~1.8k tokensUpdated 17 days ago
Testing & QAAuto-check passed
Ya Run
kzahel/yepanywhere
Launch and drive Yep Anywhere — an isolated dev server plus real browser interaction — and run the repository's check suite.
533 GitHub stars~957 tokensUpdated today
Testing & QAAuto-check passed
OpenWork Electron Browser Automation
different-ai/openwork
Attaches OpenCode browser tools to the OpenWork Electron dev app through CDP to explore its UI, send a composer task and debug, not to give test verdicts.
24k GitHub stars~780 tokensUpdated today
Testing & QAAuto-check passed
Run SEO Office
AgriciDaniel/seo-os
A skill your agent uses when asked to run, boot, start, dev-serve, smoke-test, or drive the SEO Office app, or to confirm a change works end-to-end in the real running app (UI → orchestrator → brain…
134 GitHub stars~1.1k tokensUpdated 3 mo ago
Testing & QAAuto-check passed

More from team-attention/hoyeon

All 36 skills in this repo

Skill Session Analyzer
team-attention/hoyeon
This skill should be used when the user asks to "analyze session", "evaluate skill execution", "check session logs", provides a session ID with a skill path, or wants to verify that a skill executed…
173 GitHub stars~1.9k tokensUpdated 4 mo ago
Auto-check: notes
Browser Work
team-attention/hoyeon
Recon-first browser automation. An agent skill from team-attention/hoyeon.
173 GitHub stars~1.9k tokensUpdated 4 mo ago
Auto-check passed
Check
team-attention/hoyeon
This skill should be used when the user wants to verify their changes before pushing, or update the project's rule checklists.
173 GitHub stars~1.8k tokensUpdated 4 mo ago
Auto-check: notes
Compound
team-attention/hoyeon
This skill should be used when the user says "/compound", "compound this", "document learnings", "save what we learned", or after completing a PR.
173 GitHub stars~1.1k tokensUpdated 4 mo ago
Auto-check: notes
QA
team-attention/hoyeon
Systematically QA test any application — web apps, native macOS apps, Electron apps, CLI tools, interactive REPLs, or anything on screen.
173 GitHub stars~2.6k tokensUpdated 4 mo ago
Auto-check: notes
Dev Scan
team-attention/hoyeon
Collect diverse opinions on technical topics from developer communities.
173 GitHub starsUsed in 1 repo~5k tokens
Auto-check passed

Works with

pnpm

Questions about Verify

What does Verify do?

Run a full implementation verification pass after code or data changes. Verify is an agent skill from team-attention/hoyeon. Run a full implementation verification pass after code or data changes.

When should I use Verify?

Verify fits situations like: the user asks to verify; validate a feature; inspect a local app in the browser; capture screenshots.

How do I install Verify in Claude Code?

Run `npx skills add team-attention/hoyeon --skill verify -a claude-code`. Or copy the skill folder (skills/verify in team-attention/hoyeon) into .claude/skills/verify in your project. Claude Code loads it when a task matches its description.

How do I install Verify in Codex?

Run `npx skills add team-attention/hoyeon --skill verify -a codex`. Or copy the skill folder (skills/verify in team-attention/hoyeon) into .agents/skills/verify in your project. Codex loads it when a task matches its description.

Can I use Verify 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 team-attention/hoyeon --skill verify -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/verify, .gemini/skills/verify, .github/skills/verify and .opencode/skills/verify in your project.

What does Verify need to run?

Going by SKILL.md and its folder, Verify needs the command-line tools its instructions call (pnpm).

Does Verify 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 Verify 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 Verify use?

Verify is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Verify use?

About 1.2k tokens (SKILL.md is roughly 4.9k 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 Verify?

Skills that share tags, products or a category with Verify: DeerFlow Smoke Test (bytedance/deer-flow, 83k stars), OpenWork Desktop CDP Driver (different-ai/openwork, 24k stars), Desktop Dual Repo Test (Eynzof/Hermes-CN-Desktop, 1.7k stars) and Ya Run (kzahel/yepanywhere, 533 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Verify?

team-attention (a GitHub organization) maintains it in team-attention/hoyeon, which has 173 GitHub stars. The repository holds 36 skills in this directory. The repository was last updated on May 21, 2026.

Source: team-attention/hoyeon on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Verify

Facts

At a glance

What it does

When your agent uses it

Example prompts

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

verify

Role

Workflow

1. Define Mission

2. Inspect Repo Verification Surface

3. Run Command Verification

4. Run Browser QA

5. Classify Findings

6. Update Verification Assets With Approval

7. Report

Report Artifact Shape

Verdict Policy

Files

Compare with similar skills

Similar skills

More from team-attention/hoyeon

Related

Questions about Verify