eval-summary

Validate readings.ts summaries against Korean Markdown and report issues.

282|23|Updated Jan 3, 2026
One-click install
npx skills add https://github.com/team-attention/stanford-cs146s-kr --skill eval-summary
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: eval-summary
Source: https://github.com/team-attention/stanford-cs146s-kr/tree/main/.claude/skills/eval-summary
Command: npx skills add https://github.com/team-attention/stanford-cs146s-kr --skill eval-summary

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the validation of readings.ts summaries by comparing them to the original Korean Markdown, identifies gaps, and proposes improvements. It helps maintain translation quality and consistency across reading materials.

Core Features & Use Cases

  • Automated summary validation: Compare tldr, learningGoals, chapterSummaries, motivation, and keyTakeaways between original and KR translations.
  • Issue tracking and suggestions: Generate improvement recommendations per issue and request user confirmation before applying changes to readings.ts.
  • Use Case: A maintainer runs /eval-summary week1 to verify all weekly summaries, then iteratively refines readings.ts based on the report.

Quick Start

Run the eval-summary skill for a whole week or a specific reading:

  • /eval-summary week1
  • /eval-summary week1/deep-dive-llms
  • /eval-summary week1/how-openai-uses-codex

Frequently Asked Questions about eval-summary

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

FAQPage Schema
How do I validate Markdown translation summaries against Korean originals?

To validate translation quality, compare readings.ts summary fields against original Korean Markdown to automatically identify gaps, track issues, and propose improvements for translation consistency.

What is the best way to audit readings.ts summary fields for missing content?

You can audit readings.ts summaries by running an evaluation over weekly readings or individual slugs to verify required fields, record quality issues, and output an evaluation-report.json for review.

How do I automatically compare tldr and chapterSummaries fields with source Markdown?

Automated comparison of tldr and chapterSummaries works by scanning readings.ts, verifying required fields exist, and comparing their content directly against the original Korean Markdown to flag discrepancies.

Can I apply suggested corrections to readings.ts without manual review?

No, suggested corrections to readings.ts require user confirmation before applying changes, ensuring you maintain manual oversight of translation quality updates proposed during the evaluation.

Does the readings.ts validation report support individual reading slugs or only weekly batches?

The validation supports both weekly batches and individual reading slugs, allowing you to target an entire week or a specific reading path like week1/deep-dive-llms for issue tracking.

When should I generate an evaluation report for translation quality assurance?

You should generate an evaluation report when maintaining translation consistency across reading materials, identifying gaps in KR translations, or iteratively refining readings.ts summaries based on identified issues.