Adversarial Verify

Community

Archive228

adversarial-verify

Review a diff against the goal spec assuming the code is BROKEN. The reviewer that lives in the maker's head always agrees with itself — this pulls review into a hostile, separate pass. Invoke after every code change before marking work done.

Overview

Publisher	Archive228
Repository	`loopkit`
Skill name	`adversarial-verify`
Stars	755
Forks	124
Bundled files	Instructions only
License	MIT
Links	Skill source Repository

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 Archive228 on GitHub. Read the source before you install it.

Installation

Install the Adversarial 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/Archive228/loopkit/tree/main/skills/adversarial-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/Archive228/loopkit.git /tmp/loopkit
mkdir -p .claude/skills
cp -r /tmp/loopkit/skills/adversarial-verify .claude/skills/adversarial-verify

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

Use it in TypingMind

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

Adversarial Verify

Default stance: the code is broken until proven otherwise. Your job is to find where. Do not be polite. Do not propose fixes. Do not run the code. Just hunt.

Read first

The goal spec (PROMPT.md / the task). What does "done" actually require?
The diff. Every changed line.

The 11 shortcuts agents take to fake "done" — check each

Relaxed tests — assertions weakened or deleted to make red go green.
Swallowed errors — try/except that hides the failure instead of handling it.
Fake renames — a function "fixed" by renaming, behavior unchanged.
Stub returns — hardcoded return values that pass the one test, fail everything else.
Comment-as-fix — the bug is now a TODO.
Happy-path only — 500s, empty inputs, missing files unhandled.
Scope creep — changes unrelated to the goal ("while I was in there").
Invented API — a method/param that doesn't exist in the actual source.
Silent decision — an architectural choice (schema, auth) made without flagging it.
Pass-by-mock — the test mocks the exact thing it claims to verify.
Off-spec done — code works, tests pass, but solves a goal that isn't the one asked.

Output (JSON, no prose)

json
{"passes": false, "failures": [{"line": 42, "shortcut": "swallowed errors", "why": "..."}]}

If it genuinely passes, say so in one line. Most of the time, it doesn't.

Frequently asked questions

What does the Adversarial Verify AI skill do?

Why use Adversarial Verify on TypingMind?

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

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

Which AI models can use Adversarial 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 Adversarial Verify?

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

Is the Adversarial Verify AI skill free?

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

Documentation Lookup

affaan-m

CommunityPopular

Use up-to-date library and framework docs via Context7 MCP instead of training data. Activates for setup questions, API references, code examples, or when the user names a framework (e.g. React,…

Everything Claude Code

affaan-m

CommunityPopular

Development conventions and patterns for everything-claude-code. JavaScript project with conventional commits.

Discord User Post

Post an approved message as the logged-in Discord user through the Discord desktop app. Use for release announcements or other direct user-authored Discord posts; not for OpenClaw channel sends, bots,…

Test Audit

Invoke whenever writing, changing, reviewing, or sweeping tests. Authoring gate for new tests plus audit workflow for low-value, implementation-coupled, or duplicative tests and the test-only…

Overview

Installation

Install in TypingMind

Install in another agent

Use it in TypingMind

Works with any AI model

Skill instructions

Adversarial Verify

Read first

The 11 shortcuts agents take to fake "done" — check each

Output (JSON, no prose)

Frequently asked questions

Related AI Skills

Set up your own AI workspace now