Agent skill

Verify

by theopenco in theopenco/llmgateway

Build, launch, and drive the LLM Gateway stack in an isolated worktree environment to verify API, gateway, dashboard, playground, or screenshot changes.

Custom licenceAuto-check passedDevelopment

Install Verify

skills CLI
$ npx skills add theopenco/llmgateway --skill verify -a claude-code

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

GitHub CLI
$ gh skill install theopenco/llmgateway 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/theopenco/llmgateway.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/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
1.7k
Token cost
~1k tokens
SKILL.md length
512 words
Files
1
Skills in repo
19
Repo updated
First seen
Licence
Custom licence

At a glance

Build, launch, and drive the LLM Gateway stack in an isolated worktree environment to verify API, gateway, dashboard, playground, or screenshot changes.

  • Works in 3 steps: Follow the local-stack skill. → Reuse the worktree's exported… → Confirm the selected ports are free.…
  • Locally reproducing a change
  • SKILL.md covers Isolate the workspace, Build and launch, Drive and capture and Clean up
  • Calls pnpm and docker

What it does

Verify is an agent skill from theopenco/llmgateway. Build, launch, and drive the LLM Gateway stack in an isolated worktree environment to verify API, gateway, dashboard, playground, or screenshot changes. Use when locally reproducing a change, launching services on offset ports, taking seeded-data screenshots, or checking a workflow end to end.

Its SKILL.md is about 1k 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 Development, covering Git worktrees, Model routing and gateways and Microservices. It works with Docker and pnpm. The repository describes itself as: Route, manage, and analyze your LLM requests across multiple providers with a unified API interface.

When your agent uses it

  • Locally reproducing a change
  • Launching services on offset ports
  • Taking seeded-data screenshots
  • Checking a workflow end to end

Example prompts

  • “/verify”

Requirements

  • Docker

Workflow steps

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

  1. Follow the local-stack skill.
  2. Reuse the worktree's exported STACK_SUFFIX, database URLs, Redis ports, app
  3. Confirm the selected ports are free. Never start or reset the default shared

What it can do on your machine

Read from SKILL.md and the folder at commit 414b1b9. 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
    • docker

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

  • Network

    No URLs in SKILL.md. Its commands use pnpm and docker, 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 1k tokens when it runs. Until then it costs about 75 tokens; SKILL.md has 512 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
~1k

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 512 words (~1,019 tokens).

“Use the repository's current implementation and AGENTS.md as the source of truth. Do not reuse ports, containers, credentials, or commands remembered from another worktree.”

— opening of SKILL.md by theopenco, Custom licence
name
verify

Read the full SKILL.md on GitHub

Files

Just SKILL.md in .agents/skills/verify of theopenco/llmgateway.

Open the folder on GitHubat commit 414b1b9

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 skilltheopenco/llmgateway1.7k—~1kAutomated safety check: PassCustom licence
LLM Gatewaysickn33/agentic-awesome-skills47k1 repos~2.1kAutomated safety check: PassMIT
Worktree StackLanternOps/breeze131—~1.2kAutomated safety check: NotesAGPL-3.0
Devcontainer Devstacklok/toolhive-studio170—~3.8kAutomated safety check: NotesApache-2.0
Tnr Dev Serverstudie-tech/TheNinjaRPG104—~2.5kAutomated safety check: NotesNone
Debugging Local Task Agent RunsPostHog/posthog40k—~2.1kAutomated safety check: NotesCustom licence

Similar skills

  • LLM Gateway

    sickn33/agentic-awesome-skills

    Deploy an API gateway for LLM traffic with load balancing, rate limiting, key management, semantic caching, fallback routing, and cost tracking.

    47k GitHub starsUsed in 1 repo~2.1k tokens
    Backend & APIsAuto-check passed
  • Worktree Stack

    LanternOps/breeze

    A skill your agent uses when an agent needs a running, seeded, Playwright-ready Breeze stack for the current git worktree.

    131 GitHub stars~1.2k tokensUpdated today
    DevelopmentAuto-check: notes
  • Devcontainer Dev

    stacklok/toolhive-studio

    Spin up and interact with ToolHive Studio's containerized dev environment (Xvfb + noVNC + DinD).

    170 GitHub stars~3.8k tokensUpdated today
    Agent WorkflowsAuto-check: notes
  • Tnr Dev Server

    studie-tech/TheNinjaRPG

    Run a TheNinjaRPG dev server locally from any git worktree, provision disposable test users, and call tRPC endpoints as those users.

    104 GitHub stars~2.5k tokensUpdated today
    DevelopmentAuto-check: notes
  • Official

    Debug the output of local PostHog task runs — the wizard cloud-run path that executes inside a Docker sandbox under the local Temporal process-task workflow (the wizard that integrates PostHog, then…

    40k GitHub stars~2.1k tokensUpdated today
    DevelopmentAuto-check: notes
  • Starts a Dozzle dev server on a port derived from the current worktree so you can test by hand in a browser, without disturbing instances started elsewhere.

    15k GitHub stars~747 tokensUpdated today
    DevelopmentAuto-check passed

More from theopenco/llmgateway

All 19 skills in this repo
  • Blog

    theopenco/llmgateway

    Write and validate an LLM Gateway marketing blog post in the repository's current house style, including structured frontmatter and a gpt-image-2 OpenGraph image.

    1.7k GitHub stars~2.2k tokensUpdated today
    Auto-check passed
  • Model Benchmarks

    theopenco/llmgateway

    Run and report repository model or provider-mapping benchmarks.

    1.7k GitHub stars~1.1k tokensUpdated today
    Auto-check: notes
  • Skill Authoring

    theopenco/llmgateway

    Create, update, and audit repository-local agent skills against the current LLM Gateway codebase.

    1.7k GitHub stars~662 tokensUpdated today
    Auto-check passed
  • Security Audit

    theopenco/llmgateway

    Security best practices, vulnerability review, and full security audits for LLM Gateway.

    1.7k GitHub stars~1.8k tokensUpdated today
    Auto-check passed
  • Changelog

    theopenco/llmgateway

    Write a new LLM Gateway changelog entry. An agent skill from theopenco/llmgateway.

    1.7k GitHub stars~2k tokensUpdated today
    Auto-check passed
  • Knowledge Base

    theopenco/llmgateway

    Write a new LLM Gateway docs Knowledge base page under apps/docs/content/(product)/learn with light and dark dashboard screenshots.

    1.7k GitHub stars~1.7k tokensUpdated today
    Auto-check passed

Works with

Questions about Verify

What does Verify do?

Build, launch, and drive the LLM Gateway stack in an isolated worktree environment to verify API, gateway, dashboard, playground, or screenshot changes. Verify is an agent skill from theopenco/llmgateway. Build, launch, and drive the LLM Gateway stack in an isolated worktree environment to verify API, gateway, dashboard, playground, or screenshot changes.

When should I use Verify?

Verify fits situations like: locally reproducing a change; launching services on offset ports; taking seeded-data screenshots; checking a workflow end to end.

How do I install Verify in Claude Code?

Run `npx skills add theopenco/llmgateway --skill verify -a claude-code`. Or copy the skill folder (.agents/skills/verify in theopenco/llmgateway) 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 theopenco/llmgateway --skill verify -a codex`. Or copy the skill folder (.agents/skills/verify in theopenco/llmgateway) 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 theopenco/llmgateway --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 and docker). Our summary lists: Docker.

Does Verify access the network?

SKILL.md contains no URLs. Its commands use docker, 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 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 Verify use?

About 1k tokens (SKILL.md is roughly 4.1k 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: LLM Gateway (sickn33/agentic-awesome-skills, 47k stars), Worktree Stack (LanternOps/breeze, 131 stars), Devcontainer Dev (stacklok/toolhive-studio, 170 stars) and Tnr Dev Server (studie-tech/TheNinjaRPG, 104 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Verify?

theopenco (a GitHub organization) maintains it in theopenco/llmgateway, which has 1,675 GitHub stars. The repository holds 19 skills in this directory. The repository was last updated on October 7, 2026.

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