[curriculum-eval] 04-github-actions-intro.md: checkpoint_quality — 25 new concepts, no checkpoint on the only Actions primer in the core path

[github-actions]

File: workshop/04-github-actions-intro.md
Overall Score: 5.4 / 10.0 (corpus mean: 6.1)

Flagged Dimensions:

Dimension	Score	Benchmark	Delta
checkpoint_quality	0.0	10.0	−10.0
cognitive_load	7.5	10.0	−2.5
active_learning	4.6	10.0	−5.4
scaffolding	5.0	10.0	−5.0

Root Cause (≤ 2 sentences):
This step introduces 25 new concepts (triggers, jobs, steps, runners, workflow files, YAML keys, matrix strategy, and more) with no closing checkpoint, meaning learners receive no confirmation they have retained the foundational Actions vocabulary that the rest of the workshop depends on. As the only Actions primer in the core path, its 0.0 checkpoint score is especially high-risk: a learner who skips or misunderstands this page carries knowledge gaps into every subsequent step.

Evidence (quoted from the file):

"After this step, you'll be able to read any classic GitHub Actions workflow file."

The page asserts a learning outcome but provides no mechanism — no quiz, no checkpoint, no retrieval task — to confirm the learner has actually achieved it before advancing to step 05.

Learning Science Rationale:
Bloom's Taxonomy (Understand level) predicts that declarative knowledge of YAML keys and workflow primitives requires both exposure and retrieval practice to consolidate into usable schema. A 645-word page with 25 new terms and no checkpoint relies entirely on recognition memory; without active recall (e.g., "name the three parts of a workflow job"), the concepts decay rapidly and do not transfer to the Apply-level tasks in steps 07–08. Adding a 4-item checkpoint converts passive recognition into active recall.

Improvement Prompt (for an agent):

In workshop/04-github-actions-intro.md, add a "## :white_check_mark: Checkpoint" section at the end with at least 4 specific, verifiable items. Each item should test one of the core Actions concepts introduced in the step (trigger, job, step, runner). Phrase each as something the learner can verify without running code — for example: "- [ ] I can name the three top-level YAML keys used in every workflow file (on, jobs, steps)" or "- [ ] I understand that each job runs on its own fresh runner machine." Additionally, consider splitting the 25 new concepts by moving the matrix, concurrency, and environment-variable sub-topics into brief links or a side quest, reducing the core concept list to 15 or fewer.

Expected Score After Fix: 7.1 / 10.0

Warning

Firewall blocked 1 domain

The following domain was blocked by the firewall during workflow execution:

• awmgmcpg

To allow these domains, add them to the network.allowed list in your workflow frontmatter:

network:
  allowed:
    - defaults
    - "awmgmcpg"

See Network Configuration for more information.

Generated by 🔬 Curriculum Quality Evaluator · 78.6 AIC · ⌖ 6.91 AIC · ⊞ 6.2K · ◷

• expires on Aug 8, 2026, 1:11 PM UTC

[github-actions]

This issue was automatically closed because it expired on 2026-08-08T13:11:59.559Z.

Closed by Workflow