Verify

CommunityPopular

perminder-klair

verify

Drive a controller/admin-UI change end-to-end from a worktree without touching the live station — isolated controller on a spare port + temp STATE_DIR, worktree Next dev server, Playwright against /admin.

Overview

Publisher	perminder-klair
Repository	`subwave`
Skill name	`verify`
Stars	1.4K
Forks	122
Bundled files	Instructions only
License	MIT
Links	Skill source Repository Homepage

Markdown instructions
A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.
Works with any LLM
AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.
Self-contained
Everything the model needs lives in the instructions — no extra files to sync.
Open source
Published by perminder-klair on GitHub. Read the source before you install it.

Installation

Install the Verify AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

Open the app and go to Plugins → Skills.
Choose "Install from GitHub".
Paste the skill folder URL below and confirm.
https://github.com/perminder-klair/subwave/tree/develop/.claude/skills/verify
Enable the skill in any chat where you want it available.

Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills

git clone --depth 1 https://github.com/perminder-klair/subwave.git /tmp/subwave
mkdir -p .claude/skills
cp -r /tmp/subwave/.claude/skills/verify .claude/skills/verify

Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Verify in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Verify on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Verify is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

Loaded only when it is needed
The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.
Switch models mid-chat
Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Verifying controller + admin-UI changes in isolation

The operator's real station is usually running (docker sub-wave-* containers). Never restart or point tests at it. Boot your own stack from the worktree instead:

Isolated controller (API surface)

bash
cd <worktree>/controller
STATE_DIR=$CLAUDE_JOB_DIR/tmp/state PORT=7791 ADMIN_USER=test ADMIN_PASS=test \
  NODE_ENV=development \
  NAVIDROME_URL=http://localhost:9999 NAVIDROME_USER=x NAVIDROME_PASS=x \
  npx tsx src/server.ts

A fresh STATE_DIR boots clean (seeds sfx/jingles, writes settings.json on first save).
The fake NAVIDROME_* env matters: without it needsSetup is true and the admin shell redirects every page to /onboarding, so UI tests never find their controls.
Drive /settings etc. with curl -u test:test http://localhost:7791/....
To test load-time migrations: stop the server, hand-edit settings.json, restart, GET.
Kill by port (fuser -k 7791/tcp) — a pkill -f "tsx src/server.ts" matches the Bash tool's own wrapper cmdline and kills your shell (exit 144).

Worktree web dev server (UI surface)

bash
cd <worktree>/web
NEXT_PUBLIC_API_URL=http://localhost:7791 npm run dev -- -p 7793

Then Playwright (headless chromium, sync API):

Pre-seed auth before load: ctx.add_init_script("localStorage.setItem('subwave_admin_auth', '<base64 user:pass>')").
Assert state through the controller API after clicking Save, not through sonner toasts.
Admin modals portal into .admin-root; scope input lookups with [role="dialog"].

Frequently asked questions

What does the Verify AI skill do?

Why use Verify on TypingMind?

Because you install it once and use it with any model. Verify is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Verify in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/perminder-klair/subwave/tree/develop/.claude/skills/verify. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Verify?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Verify?

As many as you like. As long as a model supports skills, you can use Verify with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Verify AI skill free?

Yes. It is published on GitHub by perminder-klair under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Auteur

NousResearch

OrganizationPopular

Design and build cinematic, award-level web pages.

Skill Creator

Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a…

E2e Cucumber Playwright

langgenius

OrganizationPopular

Use when writing, changing, or reviewing Cucumber and Playwright tests under `e2e/`, including feature files, step definitions, support code, scenario tags, locators, and assertions. Do not use for…

Channel Message Flows

openclaw

OrganizationPopular

Use when running QA Lab channel message flow evidence.

Overview

Installation

Install in TypingMind

Install in another agent

Use it in TypingMind

Works with any AI model

Skill instructions

Verifying controller + admin-UI changes in isolation

Isolated controller (API surface)

Worktree web dev server (UI surface)

Frequently asked questions

Related AI Skills

Set up your own AI workspace now