New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Verify

by whiteguo233 in whiteguo233/OpenBiliClaw

Drive a real serve-api process against isolated project roots to verify backend/web changes end-to-end

MITAuto-check passed

Install Verify

skills CLI
$ npx skills add whiteguo233/OpenBiliClaw --skill verify -a claude-code

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

GitHub CLI
$ gh skill install whiteguo233/OpenBiliClaw 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/whiteguo233/OpenBiliClaw.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/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/

Facts

Skill name
verify
GitHub stars
3.4k
Token cost
~539 tokens
SKILL.md length
236 words
Files
1
Skills in repo
9
Repo updated
First seen
Licence
MIT

At a glance

Drive a real serve-api process against isolated project roots to verify backend/web changes end-to-end

  • Works in 5 steps: Isolated project root: mktemp -d… → Craft the backend state you need via… → Launch (background, stdin must be closed… → …
  • Tasks that involve End-to-end testing
  • Calls curl; needs OPENAI_API_KEY and ANTHROPIC_API_KEY

What it does

Verify is an agent skill from whiteguo233/OpenBiliClaw. Drive a real serve-api process against isolated project roots to verify backend/web changes end-to-end

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

The repository describes itself as: 本地私有、开源的自进化跨平台 AI 内容发现 Agent：先理解你，再主动从 B站、小红书、抖音、YouTube、X、知乎、Reddit、微博等平台与开放 Web 寻找内容。（支持 deepseek harness 插件） | Local-first open-source cross-platform AI content discovery…. The licence is MIT.

When your agent uses it

  • Tasks that involve End-to-end testing

Example prompts

  • “/verify”

Requirements

  • A credential in OPENAI_API_KEY
  • A credential in ANTHROPIC_API_KEY

Workflow steps

5 steps, taken from the first numbered list in SKILL.md.

  1. Isolated project root: mktemp -d /tmp/obc-verify.XXXXXX, put a minimal
  2. Craft the backend state you need via config/data, not mocks
  3. Launch (background, stdin must be closed or it hangs)
  4. Probe with curl --noproxy '*' — the local proxy/TUN hijacks loopback
  5. Clean up: kill the PIDs, confirm nothing listens on the ports

What it can do on your machine

Read from SKILL.md and the folder at commit 2d8fe41. 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:

    • curl

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use curl, 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 these keys or tokens, usually read from environment variables:

    • OPENAI_API_KEY
    • ANTHROPIC_API_KEY
    • GOOGLE_API_KEY
    • GEMINI_API_KEY

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Verify loads about 539 tokens when it runs. Until then it costs about 27 tokens; SKILL.md has 236 words of instructions outside code blocks.

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

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 whiteguo233/OpenBiliClaw at commit 2d8fe41, republished under its MIT licence (© whiteguo233). 236 words, ~539 tokens.

Download SKILL.mdSave it as .claude/skills/verify/SKILL.md (or your agent's skills folder).
name
verify
description
Drive a real serve-api process against isolated project roots to verify backend/web changes end-to-end

Verifying OpenBiliClaw backend changes end-to-end

Port 8420 is the user's production backend — never restart or reuse it. Spin up throwaway serve-api instances on spare ports (846x) against isolated project roots instead, and always kill them when done.

Recipe

  1. Isolated project root: mktemp -d /tmp/obc-verify.XXXXXX, put a minimal config.toml + empty data/ inside, point OPENBILICLAW_PROJECT_ROOT at it. data_dir = "data" resolves against that root.

  2. Craft the backend state you need via config/data, not mocks:

    • Configured but uninitialized: any provider section with a dummy api_key (registry build does not call the network at startup).
    • Degraded (llm_registry_unavailable): all provider keys empty and launch with env -u OPENAI_API_KEY -u ANTHROPIC_API_KEY -u GOOGLE_API_KEY -u GEMINI_API_KEY — ambient keys silently un-degrade it.
    • Initialized (profile ready): copy the real data/memory/soul.json into the tmp root's data/memory/ before launch. is_profile_ready() == "soul memory layer has data", loaded at startup (don't hot-drop the file into a running instance and expect it to flip).

  3. Launch (background, stdin must be closed or it hangs):

    bash
    OPENBILICLAW_PROJECT_ROOT=/tmp/obc-verify.XXX/a \
  nohup .venv/bin/openbiliclaw serve-api --host 127.0.0.1 --port 8461 \
  > /tmp/obc-verify.XXX/a/server.log 2>&1 < /dev/null &

    Ready in ~5-8s. Use the main repo's .venv/bin/openbiliclaw.

  4. Probe with curl --noproxy '*' — the local proxy/TUN hijacks loopback otherwise. curl -D - for redirect headers, /api/health to confirm the state you crafted (status, profile_ready), server.log for the "started in degraded mode" line.

  5. Clean up: kill the PIDs, confirm nothing listens on the ports (lsof -nP -iTCP:846x -sTCP:LISTEN), rm -rf the tmp roots. Zombie temp serve-api instances have corrupted real user data before — never skip this.

© whiteguo233, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .claude/skills/verify of whiteguo233/OpenBiliClaw.

Open the folder on GitHubat commit 2d8fe41

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
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Verify this skillwhiteguo233/OpenBiliClaw3.4k—~539Automated safety check: PassMIT
Web Application Testinganthropics/skills180k51 repos~966Automated safety check: PassApache-2.0
Electron App Automationvercel-labs/agent-browser44k5 repos~1.7kAutomated safety check: PassApache-2.0
OpenHarness End-to-End EvalsHKUDS/OpenHarness16k1 repos~2.1kAutomated safety check: NotesMIT
Write and Verify Playwright Testsappsmithorg/appsmith41k—~2.9kAutomated safety check: NotesApache-2.0
playwright-cli Browser Automationgithub/gh-aw5.4k23 repos~2.8kAutomated safety check: PassMIT

Similar skills

  • Web Application Testing

    anthropics/skills

    Official

    Tests local web applications with Python Playwright scripts, checking frontend behavior, capturing screenshots and reading browser console logs.

    180k GitHub starsUsed in 51 repos~966 tokens
    Testing & QAAuto-check passed

  • Electron App Automation

    vercel-labs/agent-browser

    Official

    Automates Electron desktop apps such as VS Code, Slack or Discord by connecting agent-browser to their Chrome DevTools Protocol port.

    44k GitHub starsUsed in 5 repos~1.7k tokens
    Productivity & AutomationAuto-check passed

  • OpenHarness End-to-End Evals

    HKUDS/OpenHarness

    Validates OpenHarness features by running real multi-turn agent loops with live LLM calls against an unfamiliar codebase, checking actual tool execution.

    16k GitHub starsUsed in 1 repo~2.1k tokens
    Testing & QAAuto-check: notes

  • Write and Verify Playwright Tests

    appsmithorg/appsmith

    Writes a Playwright end-to-end test from a prompt, runs it against a live Appsmith deployment and retries with fixes up to three times until it passes.

    41k GitHub stars~2.9k tokensUpdated today
    Testing & QAAuto-check: notes

  • playwright-cli Browser Automation

    github/gh-aw

    Official

    Drives a real browser from the command line with playwright-cli to open pages, interact, mock requests, save state and work with Playwright tests.

    5.4k GitHub starsUsed in 23 repos~2.8k tokens
    Testing & QAAuto-check passed

  • Cucumber and Playwright E2E Tests

    langgenius/dify

    Guides changes and reviews of the Cucumber and Playwright end-to-end suite under `e2e/`: feature files, step definitions, support code, tags, locators and assertions.

    158k GitHub stars~682 tokensUpdated today
    Testing & QAAuto-check passed

More from whiteguo233/OpenBiliClaw

All 9 skills in this repo

  • Release

    whiteguo233/OpenBiliClaw

    A skill your agent uses when releasing a version, bumping project versions, or pushing release tags.

    3.4k GitHub stars~680 tokensUpdated today
    Auto-check passed

  • Add Platform Source

    whiteguo233/OpenBiliClaw

    Add, repair, or validate an OpenBiliClaw platform source across fetching, account signals, discovery, and user surfaces.

    3.4k GitHub stars~1.9k tokensUpdated today
    Auto-check passed

  • Openbiliclaw Adapter

    whiteguo233/OpenBiliClaw

    Use OpenBiliClaw's versioned Agent Bridge CLI to read multi-source recommendations, profile state, dialogue, probes, saved lists, and submit explicit feedback.

    3.4k GitHub stars~2.2k tokensUpdated today
    Auto-check passed

  • Writing Specs

    whiteguo233/OpenBiliClaw

    A skill your agent uses when authoring a spec or implementation plan, or planning multi-task work.

    3.4k GitHub stars~1.1k tokensUpdated today
    Auto-check passed

  • System Steward

    whiteguo233/OpenBiliClaw

    管理订阅源与系统配置，所有改动逐项向用户说明并等待批准

    3.4k GitHub stars~238 tokensUpdated today
    Auto-check passed

  • Taste Companion

    whiteguo233/OpenBiliClaw

    默认对话伙伴，陪聊口味与推荐，可读写记忆、查询推荐与观看数据

    3.4k GitHub stars~296 tokensUpdated today
    Auto-check passed

Questions about Verify

What does Verify do?

Drive a real serve-api process against isolated project roots to verify backend/web changes end-to-end. Verify is an agent skill from whiteguo233/OpenBiliClaw.

When should I use Verify?

Verify fits situations like: tasks that involve End-to-end testing.

How do I install Verify in Claude Code?

Run `npx skills add whiteguo233/OpenBiliClaw --skill verify -a claude-code`. Or copy the skill folder (.claude/skills/verify in whiteguo233/OpenBiliClaw) 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 whiteguo233/OpenBiliClaw --skill verify -a codex`. Or copy the skill folder (.claude/skills/verify in whiteguo233/OpenBiliClaw) 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 whiteguo233/OpenBiliClaw --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 (curl) and credentials named OPENAI_API_KEY, ANTHROPIC_API_KEY, GOOGLE_API_KEY and GEMINI_API_KEY. Our summary lists: A credential in OPENAI_API_KEY; A credential in ANTHROPIC_API_KEY.

Does Verify access the network?

SKILL.md contains no URLs. Its commands use curl, which can reach the network depending on how they are called. 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 539 tokens (SKILL.md is roughly 2.2k 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: Web Application Testing (anthropics/skills, 180k stars), Electron App Automation (vercel-labs/agent-browser, 44k stars), OpenHarness End-to-End Evals (HKUDS/OpenHarness, 16k stars) and Write and Verify Playwright Tests (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 Verify?

whiteguo233 (a GitHub user) maintains it in whiteguo233/OpenBiliClaw, which has 3,401 GitHub stars. The repository holds 9 skills in this directory. The repository was last updated on October 8, 2026.

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