Verify logo

Verify

OrganizationPopular
landing-ai
verify

Verify ade changes end-to-end — seed a store offline, run the CLI, drive generated artifacts in a browser.

Overview

Publisherlanding-ai
Repositoryade-cli
Skill nameverify
Stars
2.4K
Forks
257
Bundled files
Instructions only
LicenseApache-2.0
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 landing-ai 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.

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.
    https://github.com/landing-ai/ade-cli/tree/main/.claude/skills/verify
  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/landing-ai/ade-cli.git /tmp/ade-cli
mkdir -p .claude/skills
cp -r /tmp/ade-cli/.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 ade

Build/run: uv sync, then uv run ade …. Tests are offline (fake transport); verification means driving the real CLI against a real store.

Seeding a parsed doc without the network

parse needs the API, so seed the store directly — write what parse would have written (see parse.py::write_artifacts for the exact set): parse.json (raw ParseResponse), parse.md, elements.json ({"job_id", "elements": elements.project(response)}), meta.json (state: "parsed", job_id matching parse.json's metadata.job_id — the generation gate in refs.live_parse rejects mismatches).

A ready-made seeder that also draws a matching invoice PNG (so boxes visibly align) was used for the view verification — pattern: build markdown piecewise so every element's range is exact, reuse tests/parse_fixtures.py shapes.

Point the CLI at the seeded store with ADE_HOME=<dir>.

Driving view.html

The in-app browser refuses file:// — serve the doc dir instead: python3 -m http.server 8742 --bind 127.0.0.1 in $ADE_HOME/docs/<doc-id>/, then browse http://127.0.0.1:8742/view.html. Deep links: append #element=<id>. Selection state is inspectable via JS: document.querySelectorAll('.sel') (both panes share data-id). Rebuilds are fingerprint-gated — --json reports built: true|false; touching the source or changing --dpi forces a rebuild.

Frequently asked questions

What does the Verify AI skill do?

Verify ade changes end-to-end — seed a store offline, run the CLI, drive generated artifacts in a browser.

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/landing-ai/ade-cli/tree/main/.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 landing-ai under the Apache-2.0 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 👇