Validate Test logo

Validate Test

OrganizationPopular
wrtnlabs
validate-test

Validate test coverage against providers (read-only)

Overview

Publisherwrtnlabs
Repositoryautobe
Skill namevalidate-test
Stars
1.4K
Forks
156
Bundled files
Instructions only
LicenseAGPL-3.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 wrtnlabs on GitHub. Read the source before you install it.

Installation

Install the Validate Test 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/wrtnlabs/autobe/tree/main/internals/template/realize/.claude/skills/validate-test
  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/wrtnlabs/autobe.git /tmp/autobe
mkdir -p .claude/skills
cp -r /tmp/autobe/internals/template/realize/.claude/skills/validate-test .claude/skills/validate-test
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Validate Test 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 Validate Test 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 Validate Test 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.

Validate Test Infrastructure

Validate that test infrastructure properly covers providers and interfaces. This skill only checks for discrepancies - it does NOT modify any files.

Purpose

Compare interface/provider implementations with test coverage and report:

  • ✅ Matching items
  • ❌ Mismatching items (needs fix)
  • ⚠️ Items requiring review

Workflow

┌─────────────────────────────────────┐
│  Step 1: Read Interfaces            │
│  /src/api/structures/ (ICreate)     │
└───────────────┬─────────────────────┘
                │
                ▼
┌─────────────────────────────────────┐
│  Step 2: Read Test Files            │
│  /test/prepare/                     │
│  /test/generate/                    │
│  /test/features/api/                │
└───────────────┬─────────────────────┘
                │
                ▼
┌─────────────────────────────────────┐
│  Step 3: Compare & Report           │
│  - Missing prepare functions        │
│  - Missing generate functions       │
│  - Missing test scenarios           │
│  - Empty implementations            │
└─────────────────────────────────────┘

Step 1: Extract ICreate Interfaces

bash
grep -r "export type ICreate\|\.ICreate" src/api/structures/ --include="*.ts"

List all interfaces that need test data generators.


Step 2: Read Test Files

bash
# Prepare functions
find test/prepare -name "prepare_random_*.ts" -type f

# Generate functions
find test/generate -name "generate_random_*.ts" -type f

# Feature tests
find test/features/api -name "*.ts" -type f

Step 3: Validation Checks

3.1 prepare_random Coverage

For each ICreate interface:

  • ✅ prepare_random_* function exists
  • ❌ Function missing
  • ❌ Function returns empty {}

3.2 generate_random Coverage

For each prepare_random function:

  • ✅ generate_random_* function exists (1:1 mapping)
  • ❌ Function missing
  • ❌ Orphan generate without prepare

3.3 Test Scenario Coverage

For each entity:

  • ✅ Create test exists
  • ✅ Read test exists
  • ✅ Update test exists
  • ✅ Delete test exists
  • ❌ Missing CRUD tests
  • ⚠️ Missing edge case tests

3.4 Test Quality

  • ✅ Uses prepare_random (not hardcoded data)
  • ✅ Uses generate_random (not direct API calls)
  • ❌ Uses typia.random with empty type
  • ❌ Hardcoded UUIDs
  • ⚠️ Missing assertions

Output Format

markdown
# Validation Report: Test Infrastructure

## Summary
- ICreate interfaces: X
- prepare_random functions: Y
- generate_random functions: Z
- Test files: W

## ✅ Valid Items
- [Prepare] `prepare_random_entity` - All fields generated
- [Generate] `generate_random_entity` - Properly calls API
- [Test] `test_entity_create` - Complete assertions

## ❌ Issues Found
- [Missing Prepare] `another_entity` - No prepare function for ICreate
- [Missing Generate] `another_entity` - No generate function
- [Empty Prepare] `prepare_random_thing.ts` - Returns `{}`
- [Orphan Generate] `generate_random_old.ts` - No matching prepare function

## ⚠️ Warnings
- [Missing Test] `entity` - No delete test scenario
- [Edge Case] `entity` - No validation error test
- [Edge Case] `entity` - No unauthorized access test

## Recommendation
Run `/fix-test` to fix the issues above.

Important

This skill is READ-ONLY.

  • Does NOT modify any files
  • Does NOT run any build commands
  • Only reports discrepancies

To fix issues, use /fix-test skill.

Frequently asked questions

What does the Validate Test AI skill do?

Validate test coverage against providers (read-only)

Why use Validate Test on TypingMind?

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

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/wrtnlabs/autobe/tree/main/internals/template/realize/.claude/skills/validate-test. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Validate Test?

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 Validate Test?

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

Is the Validate Test AI skill free?

Yes. It is published on GitHub by wrtnlabs under the AGPL-3.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 👇