workshop-submit-to-latamboard

Package benchmark run outputs into submission folders and create GitHub pull requests.

8|Updated Sep 12, 2025
One-click install
npx skills add https://github.com/surus-lat/benchy --skill workshop-submit-to-latamboard
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: workshop-submit-to-latamboard
Source: https://github.com/surus-lat/benchy/tree/main/.workshop/skills/workshop-submit-to-latamboard
Command: npx skills add https://github.com/surus-lat/benchy --skill workshop-submit-to-latamboard

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill streamlines the process of packaging benchmark run outputs into a standardized submission format and opening a pull request, ensuring your results are ready for review without manual file management.

Core Features & Use Cases

  • Automated Packaging: Bundles run manifests, model outcomes, and configurations into the required submission directory structure.
  • PR Automation: Integrates with the GitHub CLI to automate the creation of submission pull requests against the main repository.
  • Use Case: After completing a benchmarking task in the workshop, use this skill to package your results and submit them for evaluation by the organizers.

Quick Start

Invoke the workshop-submit-to-latamboard skill to package your latest benchmark run and open a submission pull request on GitHub.

Frequently Asked Questions about workshop-submit-to-latamboard

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

FAQPage Schema
How do I submit benchmark results to a GitHub repository?

Packaging benchmark results involves bundling run manifests, model outcomes, and configurations into a standardized submission directory structure before opening a pull request for review.

Do I need the GitHub CLI to automate benchmark submission pull requests?

Yes, you need the GitHub CLI installed and local access to benchmark output directories to generate and push the submission manifests required for creating the pull request.

Can I use this to package benchy outputs for workshop evaluation?

Yes, this operates within the benchy benchmarking workshop context to package structured extraction task outputs and automate their submission for evaluation.

What is the best way to automate GitHub PR creation for benchmarking tasks?

Automating GitHub PR creation for benchmarking involves packaging run manifests and configurations into a standardized folder, then using the GitHub CLI to push and open the submission PR.

Why does my benchmark submission require a standardized folder structure?

A standardized folder structure is required so that run manifests, model outcomes, and configurations are consistently bundled and easily parsed during the result evaluation process.

What files are included when packaging benchmark outputs for submission?

Packaging benchmark outputs bundles run manifests, model outcomes, and configurations into the required submission directory structure to prepare your results for review without manual file management.