Menú
Validate statement samples and sample files for competitive programming problems. Ensures the expected outputs in problem statements match the actual solution output.
Define and enforce project-wide quality standards for agent and skill documents. Use when creating, reviewing, or refactoring files under agents/ and skills/ to keep structure, terminology, and output contracts consistent.
Audit std/brute assumptions with MCP evidence, including worst/average complexity risk and stress readiness.
Audit statement, tutorial, and samples for consistency and publication readiness before packaging.
Build multi-profile stress tests from brute complexity and constraints, then execute with traceable evidence.
Verify final tests with hard quality gates: integrity, consistency, validator, limit semantics, and wrong-solution kill.
Use before coding to decide whether a problem idea is judgeable, implementable, and verifiable.
| name | problem-validate |
| description | Validate statement samples and sample files for competitive programming problems. Ensures the expected outputs in problem statements match the actual solution output. |
| disable-model-invocation | false |
Use this skill to enforce sample correctness before final test generation.
Use when:
stress_test_run has passed and the next step is sample verification;problem_validate or sample mismatch.problem_validate against statement samples and sample files.decision: go / no_goblocking_issues: validation blockers that must be fixednext_actions: exact re-validation steps after fixesproblem_generate_tests while validation is failing.go: all selected validation types pass without unresolved mismatches.no_go: any selected validation type fails, or validation evidence is incomplete.For tool examples, detailed output schemas, error recovery playbooks, and comparison rules, see reference.md.