grading-score-compilation

Aggregate per-student grading JSONs into final_scores.json with per-question statistics.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/AKCqhzdy/dse-subject-grading --skill grading-score-compilation
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: grading-score-compilation
Source: https://github.com/AKCqhzdy/dse-subject-grading/tree/main/skills-v3/grading-score-compilation
Command: npx skills add https://github.com/AKCqhzdy/dse-subject-grading --skill grading-score-compilation

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

It aggregates per-student grading outputs into a single final_scores.json with per-question statistics, enabling efficient reporting, auditing, and performance analysis.

Core Features & Use Cases

  • Aggregate per-student grading JSONs into final_scores.json
  • Compute per-question statistics and overall score distributions
  • Validate consistency between student outputs and questions.json and enforce data integrity
  • Atomically write final_scores.json to support resume-safe operation

Quick Start

Run the grading-score-compilation script after all student JSONs are generated, pointing it at the student outputs, the questions.json, and the subject/year context.

Frequently Asked Questions about grading-score-compilation

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

FAQPage Schema
How do I aggregate per-student grading JSONs into a single final scores file?

Aggregating per-student grading JSONs involves reading individual student output files and compiling them into a single final_scores.json, computing per-question statistics and overall score distributions for your subject and year.

What is the best way to compile per-question grading statistics from multiple student JSON files?

Compiling per-question grading statistics is done by validating each student record against the complete set of leaf-question IDs from questions.json, ensuring total_raw_score equals awarded marks, and aggregating the results atomically.

How does atomic write work when generating final_scores.json for grading workflows?

Atomic write for final_scores.json ensures the aggregated grading data is written completely or not at all, supporting resume-safe operation and preventing corrupted output files if the compilation process is interrupted.

How do I validate grading data consistency between student outputs and questions.json?

Validating grading data consistency requires enforcing that each student record contains the complete set of leaf-question IDs and that the total_raw_score strictly equals the sum of awarded marks before aggregation proceeds.

Can I use this aggregation script if student JSON files are missing some leaf-question IDs?

No, the script enforces that each student record contains the complete set of leaf-question IDs defined in questions.json; missing IDs will cause validation to fail and halt the final_scores.json aggregation process.