validating-solutions

Stress-test model solutions against brute-force oracles and evaluate test suite strength with wrong-answer solutions.

1|Updated Sep 3, 2026
One-click install
npx skills add https://github.com/nudetiger/competitive-programming-problem-preparer --skill validating-solutions-nudetiger
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: validating-solutions
Source: https://github.com/nudetiger/competitive-programming-problem-preparer/tree/main/skills/validating-solutions
Command: npx skills add https://github.com/nudetiger/competitive-programming-problem-preparer --skill validating-solutions-nudetiger

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Competitive programming problem setters need proof that their model solution is correct and that their test data actually catches wrong or slow submissions. This Skill automates that validation: it stress-tests the intended solution against a brute-force oracle and attacks the test suite with a small zoo of plausible WA/TLE solutions. ## Core Features & Use Cases - Stress Testing: Runs the model solution against a brute-force oracle for many rounds, mixing tiny N with the largest N the brute can handle, and flags any mismatch. - Solution Zoo: Authors a small set of deliberately wrong (greedy WA, slower-complexity TLE) and alternative accepted solutions, each annotated with @tag, @expect, @algorithm, and @complexity metadata in the C++ header. - Verdict Matrix: Compiles and runs every solution on generated tests, comparing stdout against expected answers to expose wrong answers that exit codes alone would hide. - Use Case: After writing a model solution and test generators for a Polygon problem, use this Skill to confirm the brute and model agree, verify a plausible greedy fails on official tests, and decide whether the suite needs a killer test. ## Quick Start Ask the AI to stress-test the model solution against the brute force and check whether the current test suite catches a greedy wrong-answer solution.

Frequently Asked Questions about validating-solutions

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

FAQPage Schema
How do I stress test a competitive programming solution against a brute force?

Run the model solution and the brute-force oracle on many randomly generated small inputs and compare outputs. This Skill runs a configurable number of rounds (default 80), mixing tiny N with the largest N the brute can still finish, and stops on any mismatch.

How to check if my test data is strong enough for a programming problem?

Write a small zoo of plausible wrong solutions, such as a contestant-style greedy or a slower complexity class, and run them against the suite. If a wrong solution survives all tests, the suite needs a killer test that exposes it.

What verdict tags does Polygon use for solutions?

Solutions are tagged as main, accepted, wrong-answer, time-limit-exceeded, time-limit-exceeded-or-accepted, memory-limit-exceeded, presentation-error, or failed. Tags must come from measured runs: a correct solution that TLEs on full tests is uploaded as TO, never OK.

Does this skill generate test data or validators?

No. Test generation, checkers, and validators belong to the preparing-tests skill. This skill only validates solutions against an existing suite and reports gaps back when a wrong solution survives.

Why does my wrong-answer solution pass all the tests?

A surviving WA solution means the test suite lacks a case that distinguishes it from the correct algorithm. The fix is to add a killer test targeting the wrong approach, not to modify the wrong solution so it fails existing tests.