competition-submit-check

Verify competition platform submission capability with browser automation and blocker diagnostics.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/olliecrow/codex --skill competition-submit-check
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: competition-submit-check
Source: https://github.com/olliecrow/codex/tree/main/skills/competition-submit-check
Command: npx skills add https://github.com/olliecrow/codex --skill competition-submit-check

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill automates the verification of your ability to submit entries to online competition platforms, diagnosing any issues that prevent successful submission.

Core Features & Use Cases

  • Capability Verification: Checks if the submission process is functional without performing an actual submission.
  • Blocker Diagnostics: Identifies and explains specific reasons why a submission might fail (e.g., authentication, site changes, missing artifacts).
  • Use Case: Before investing significant time in preparing a submission for a platform like AMMChallenge, use this Skill to confirm that your account is active, the submission form is accessible, and the process is ready to go.

Quick Start

Use the competition-submit-check skill to verify submission capability for AMMChallenge.

Frequently Asked Questions about competition-submit-check

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

FAQPage Schema
How do I verify my competition submission process without actually submitting?

You can verify competition submission capability by running a non-destructive browser automation check that validates session state and artifact accessibility without performing a real submission.

Why does my automated competition submission fail on AMMChallenge?

Automated competition submission may fail due to authentication issues, site changes, or missing artifacts; running blocker diagnostics identifies and explains the specific reason preventing a successful submission.

Do I need Playwright to automate competition submission checks?

Yes, Playwright is required for browser automation to handle authentication, manage session state, and validate artifacts when verifying competition submission capability.

Can I diagnose submission blockers for Highload competition platforms?

Yes, you can diagnose submission blockers for Highload and similar competition platforms by automating the end-to-end submission process to identify authentication or site access issues.

What is a non-destructive capability check for competition entries?

A non-destructive capability check validates that your account is active and the submission form is accessible, confirming the end-to-end process is functional without submitting an actual entry.

How do I check if my account is ready for a competition submission?

You can check if your account is ready by verifying authentication, confirming the submission form is accessible, and validating that required artifacts are present before preparing your competition entry.