File: workshop/04-github-actions-intro.md
Overall Score: 5.39 / 10.0 (corpus mean: 6.15)
Flagged Dimensions:
| Dimension |
Score |
Benchmark |
Delta |
| active_learning |
3.9 |
≥ 3 density |
-6.1 (below cap, not yet at ceiling) |
| cognitive_load |
6.8 |
≤ 15 new concepts |
new_concepts 28 (-6.5 pts vs ideal, ~2× budget) |
Root Cause (≤ 2 sentences):
This is the workshop's first Actions primer and packs 28 new concepts (trigger, job, step, runner, action, on, jobs, runs-on, self-hosted runners, the classic-vs-agentic comparison table, etc.) into only 756 words — a concept density nearly double the 15-concept ideal even though the word count itself is within budget, meaning the page is terse rather than long, but still risks overwhelming a learner new to CI/CD with unfamiliar terminology delivered in rapid succession.
Evidence (quoted from the file):
A GitHub Actions workflow is a YAML file in .github/workflows/ that tells GitHub: when to run (on) what to run (jobs) how each job executes (steps)
| Concept | Classic Actions | Agentic Workflow | ... (5-row comparison table introduced immediately after the primer, before the terms are practiced)
Learning Science Rationale:
Sweller's Cognitive Load Theory holds that novices need worked examples and one schema at a time before comparison tables are introduced; here the classic-vs-agentic comparison table (a 5-row abstraction layered on top of 5 already-new primitives: trigger/job/step/runner/action) is presented before the learner has practiced identifying those primitives in a real file, front-loading extraneous load. The page does include a "Label a sample workflow" activity, which is good design, but it arrives after — not before — the abstract comparison table, reversing the concrete-before-abstract sequencing that Cognitive Load Theory recommends for novice schema construction.
Improvement Prompt (for an agent):
Edit workshop/04-github-actions-intro.md to reduce simultaneous new-concept load and improve sequencing:
1. Move the "Label a sample workflow" hands-on activity (currently under "## Label a sample workflow") to appear immediately after the "Quick Refresher" section and its annotated YAML example, and BEFORE the "Why This Matters for Agentic Workflows" comparison table. Learners should practice identifying trigger/job/runner/step/action in a concrete example before encountering the abstract classic-vs-agentic comparison.
2. In the "Why This Matters for Agentic Workflows" table, reduce from 4 rows to the 2-3 most essential comparisons (e.g. keep Trigger and Steps rows, consider folding Runner and Output into a single sentence) to cut concept count without losing the core insight.
3. Keep the existing "Try it: Explore a real workflow" activity and checkpoint unchanged.
4. Run `npx --yes markdownlint-cli2 "workshop/04-github-actions-intro.md"` after editing and fix any lint errors.
Expected Score After Fix: 6.4 / 10.0
Generated by 🔬 Curriculum Quality Evaluator · copilot · auto · 62.1 AIC · ⌖ 23.2 AIC · ⊞ 9.5K · ◷
File:
workshop/04-github-actions-intro.mdOverall Score:
5.39 / 10.0(corpus mean:6.15)Flagged Dimensions:
3.9-6.1(below cap, not yet at ceiling)6.828(-6.5pts vs ideal, ~2× budget)Root Cause (≤ 2 sentences):
This is the workshop's first Actions primer and packs 28 new concepts (trigger, job, step, runner, action,
on,jobs,runs-on, self-hosted runners, the classic-vs-agentic comparison table, etc.) into only 756 words — a concept density nearly double the 15-concept ideal even though the word count itself is within budget, meaning the page is terse rather than long, but still risks overwhelming a learner new to CI/CD with unfamiliar terminology delivered in rapid succession.Evidence (quoted from the file):
Learning Science Rationale:
Sweller's Cognitive Load Theory holds that novices need worked examples and one schema at a time before comparison tables are introduced; here the classic-vs-agentic comparison table (a 5-row abstraction layered on top of 5 already-new primitives: trigger/job/step/runner/action) is presented before the learner has practiced identifying those primitives in a real file, front-loading extraneous load. The page does include a "Label a sample workflow" activity, which is good design, but it arrives after — not before — the abstract comparison table, reversing the concrete-before-abstract sequencing that Cognitive Load Theory recommends for novice schema construction.
Improvement Prompt (for an agent):
Expected Score After Fix:
6.4 / 10.0