Verification logo

Verification

Community
JasonxzWen
verification

Load when claiming completion requires the repository's actual deterministic build, type, lint, test, diff, smoke, and artifact gates; use diagnose while a failure's root cause is unknown.

Overview

PublisherJasonxzWen
Repositoryharness-hub
Skill nameverification
Stars
71
Forks
0
Bundled files
Instructions only
LicenseMIT
Links
  • 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 JasonxzWen on GitHub. Read the source before you install it.

Installation

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

1

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.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
  4. 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.
2

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/JasonxzWen/harness-hub.git /tmp/harness-hub
mkdir -p .claude/skills
cp -r /tmp/harness-hub/skills/verification .claude/skills/verification
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Verification 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 Verification 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 Verification 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.

Verification

Verification is evidence collection, not a generic command recipe or a verdict generator.

Discover The Gates

Discover the project's actual gates from repository instructions, package/task manifests, CI configuration, existing scripts, and nearby tests. Do not invent commands, coverage thresholds, or required tools. Prefer the same entry points maintainers and CI already use.

Classify checks by the accepted task boundary:

  • targeted behavior tests for the changed surface
  • nearest relevant suite
  • build, type, lint, format, schema, or generated-artifact checks
  • broader repository validation when blast radius warrants it
  • smoke or manual checks that prove the real user path
  • Git diff/status checks for unintended files and whitespace errors

Run independent read-only checks in parallel only when they do not compete for mutable artifacts.

Execute And Record

For every applicable gate, record:

  • exact command or reproducible manual procedure
  • exit status and concise result
  • scope covered
  • whether evidence is fresh for the current checkout

Report a required gate that cannot run as unavailable or unknown, with the missing dependency or access. Do not translate absence of evidence into a pass.

Deterministic failures cannot be waived by Agent judgment. If the root cause is unclear, use diagnose; if a confirmed code behavior needs a test-led fix, use tdd. Re-run affected gates after any mutation.

Artifact And Diff Checks

Inspect produced artifacts when correctness depends on rendering, packaging, generated files, migrations, or browser behavior. A successful command is not evidence that the artifact itself is usable.

Before completion, review current Git status and diff for:

  • unintended or missing changes
  • stale generated output
  • accidental credentials or project-specific data
  • incomplete renames and stale references
  • whitespace errors

Handoff

Return the smallest truthful verification table:

GateEvidenceResult
Project-defined checkExact command/procedure and scopepass / fail / unavailable or unknown

State residual risk and the highest-signal next action. Do not commit, push, publish, merge, or modify remote state merely because verification passed.

Frequently asked questions

What does the Verification AI skill do?

Load when claiming completion requires the repository's actual deterministic build, type, lint, test, diff, smoke, and artifact gates; use diagnose while a failure's root cause is unknown.

Why use Verification on TypingMind?

Because you install it once and use it with any model. Verification 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 Verification in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/JasonxzWen/harness-hub/tree/main/skills/verification. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Verification?

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 Verification?

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

Is the Verification AI skill free?

Yes. It is published on GitHub by JasonxzWen 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

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇