judge-validator

Generate testlib.h-based ICPC validators and checkers or interactors from config.json.

42|1|Updated Apr 28, 2026
One-click install
npx skills add https://github.com/Lumine2024/ICPC-Problem-Creator.skill --skill judge-validator
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: judge-validator
Source: https://github.com/Lumine2024/ICPC-Problem-Creator.skill/tree/main/subskills/judge-validator
Command: npx skills add https://github.com/Lumine2024/ICPC-Problem-Creator.skill --skill judge-validator

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps ICPC problem production teams avoid mismatches between the statement, config.json, generators, and the judging/validation logic that would otherwise break local verification.

Core Features & Use Cases

  • Writes robust validator logic using testlib.h to strictly validate formatting, ranges, EOF handling, and structural constraints.
  • Implements judge components for both normal problems (checker) and interactive problems (interactor) with protocol-accurate command handling and limits.
  • Maintains consistency end-to-end by aligning judge behavior with the statement and the exact fields in config.json, ensuring templates or placeholders are not left behind.

Quick Start

Ask the agent to produce a validator and the appropriate checker/interactor for your workspace, ensuring strict testlib-based validation that matches your statement and config.json.

Frequently Asked Questions about judge-validator

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate ICPC validators using testlib.h for local verification?

ICPC judge components include checkers for normal problems and interactors for interactive problems, both generated with protocol-accurate command handling and limits using testlib.h syntax.

How do I write a checker for interactive problems with testlib?

ICPC judge components include checkers for normal problems and interactors for interactive problems, both generated with protocol-accurate command handling and limits using testlib.h syntax.

Why does my ICPC validator mismatch the problem statement during local verification?

Validator mismatches occur when logic is not aligned end-to-end with the statement and config.json, leaving templates or placeholders behind; generating strict testlib.h validation ensures consistency and resolves these local verification breaks.

Can I use testlib.h checkers for both normal and interactive ICPC problems?

ICPC judge components include checkers for normal problems and interactors for interactive problems, both generated with protocol-accurate command handling and limits using testlib.h syntax.

What do I need to generate ICPC judge components for a local problem workspace?

ICPC judge components include checkers for normal problems and interactors for interactive problems, both generated with protocol-accurate command handling and limits using testlib.h syntax.