phase-0-type-judgment

Extract competition problem text from PDFs and classify into A/B/C/D/E/F types.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/SOGERSEN/math-modeling-pipeline --skill phase-0-type-judgment
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: phase-0-type-judgment
Source: https://github.com/SOGERSEN/math-modeling-pipeline/tree/main/phases/phase-0
Command: npx skills add https://github.com/SOGERSEN/math-modeling-pipeline --skill phase-0-type-judgment

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the identification of a competition problem type from a PDF problem statement and generates a structured phase-judgment document to guide downstream phases.

Core Features & Use Cases

  • PDF extraction: Pulls full problem text from the PDF for accurate classification.
  • Problem type classification: Categorizes into A/B/C/D/E/F (and DL) to route phases.
  • Judgment document generation: Outputs a formal phase-judgment artifact including attachments.
  • Attachment management: Lists and makes attachments available for downstream steps.
  • Use Case: A contest workflow uses Phase 0 to route each problem to the appropriate phase chain.

Quick Start

Identify the problem type from the input PDF and produce a structured phase judgment document.

Frequently Asked Questions about phase-0-type-judgment

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

FAQPage Schema
How do I classify competition problem types from a PDF automatically?

This Skill classifies competition problem types from a PDF by extracting the full text and categorizing it into types A/B/C/D/E/F and DL to generate a structured phase-judgment document.

What is phase routing for competition PDF attachments?

Phase routing for competition PDF attachments identifies the problem type and produces a formal phase-judgment artifact that lists attachments to guide downstream workflow phases.

How to generate a structured phase-judgment document from a problem statement?

Generate a structured phase-judgment document from a problem statement by using a YAML frontmatter-driven entry point to process the PDF, classify the problem type, and output the formal artifact.

Does this phase-judgment workflow require specific dependencies or environments?

This phase-judgment workflow requires no external dependencies and is intended for OpenCode-like workflows where downstream phases depend on accurate phase routing and attached problem materials.

Can I manage and list PDF attachments for downstream workflow execution?

You can manage and list PDF attachments for downstream workflow execution because this Skill supports attachment listing and makes attachments available for subsequent steps.