grade-submission

Orchestrate end-to-end grading of dev-2026 student submissions via issues.

Updated Apr 15, 2026
One-click install
npx skills add https://github.com/YangYuS8/dev-2026-grading --skill grade-submission
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: grade-submission
Source: https://github.com/YangYuS8/dev-2026-grading/tree/main/.opencode/skills/grade-submission
Command: npx skills add https://github.com/YangYuS8/dev-2026-grading --skill grade-submission

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill acts as the central orchestrator for dev-2026 submissions grading. It reads a submitted issue, identifies the target task repository, routes to the correct per-task grading skill, posts the grading results back to the issue, updates the grades CSV, and closes the issue.

Core Features & Use Cases

  • Orchestrates the end-to-end grading workflow by extracting required fields from the issue body (username, task repo, submission URL, notes) and selecting the appropriate assessment skill.
  • Automates result dissemination and record-keeping by posting results to the issue and updating results/grades.csv.
  • Handles partial submissions and error cases with clear status reporting and graceful fallbacks.

Quick Start

Use this skill by issuing /grade <issue-number>, to grade a student submission end-to-end.

Frequently Asked Questions about grade-submission

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

FAQPage Schema
How do I automate grading student submissions from GitHub issues?

You can automate grading student submissions from GitHub issues by issuing a single command. This orchestrator extracts submission data from the issue, routes it to the correct per-task assessment skill, updates the grades CSV, and posts feedback automatically.

What is the workflow for routing GitHub submissions to per-task grading skills?

Routing submissions to per-task grading skills works by extracting the username, task repo, and submission URL from the issue body, then selecting the corresponding assessment skill. The workflow clones the repository, executes grading, and updates the grades CSV.

How do I update a grades CSV file automatically after grading submissions?

Updating a grades CSV file automatically after grading submissions is built into the end-to-end orchestration workflow. Once the selected per-task grading skill completes its assessment, the orchestrator automatically records the results in the CSV file and posts feedback to the issue.

Does the submission grading orchestration handle partial submissions or errors?

The submission grading orchestration does handle partial submissions and errors through clear status reporting and graceful fallbacks. If an issue arises during repository cloning or skill execution, the workflow reports the error status instead of failing silently.

What information needs to be in a GitHub issue for the grading orchestration to work?

For the grading orchestration to work, the GitHub issue body must contain the username, task repository, submission URL, and any notes. The orchestrator extracts these required fields to identify the target repository and select the appropriate per-task assessment skill.

Can I grade multiple dev-2026 tasks across different repositories using one workflow?

You can grade multiple dev-2026 tasks across different repositories using this single orchestration workflow. It identifies the target task repository from the issue data and dynamically selects the corresponding per-task grading skill to execute the assessment end-to-end.