[curriculum-eval] 04-github-actions-intro.md: cognitive_load — 28 new terms packed into a 756-word 5-minute refresher
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 75/100
- Issue type
- Documentation
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- github-actions, markdown
- Domain
- documentation
Research direction
Read workshop/04-github-actions-intro.md, focusing on the annotated workflow example and the surrounding explanation. Add the requested active-recall checklist and reduce or relocate less essential vocabulary while keeping the example. Done when the page introduces at most 15–18 new terms before the checkpoint and includes the Try it activity.
Written by the indexing model from the issue text.
Description
File: workshop/04-github-actions-intro.md
Overall Score: 5.39 / 10.0 (corpus mean: 6.09)
Flagged Dimensions:
| Dimension | Score | Benchmark | Delta |
|---|---|---|---|
| cognitive_load | 6.8 |
≤800 words, ≤15 concepts → 10 | -3.2 |
| active_learning | 3.9 |
density ≥ 3 → 10 | -6.1 |
Root Cause (≤ 2 sentences):
At only 756 words this page introduces 28 new concepts (trigger, on, jobs, steps, runner, action, workflow file, YAML, .github/workflows/, and more Actions vocabulary), the highest concept-to-word ratio among the flagged findings, because it compresses a full Actions primer into a "5 Minutes" refresher with just 4 code blocks to anchor that vocabulary.
Evidence (quoted from the file):
"You'll do a fast refresher on the Actions primitives used in this workshop: triggers, jobs, steps, and workflow files. After this step, you'll be able to read any classic GitHub Actions workflow file." — four distinct new terms are named in a single sentence with only one annotated example following.
Learning Science Rationale:
Sweller's Cognitive Load Theory distinguishes germane load (productive, concept-building effort) from extraneous load (effort wasted on format or sequencing); packing 28 new vocabulary terms into a terse "5 minutes" framing before providing enough annotated repetition to consolidate each term risks extraneous load, since learners must hold many undifferentiated labels in working memory simultaneously rather than building one schema at a time.
Improvement Prompt (for an agent):
Edit workshop/04-github-actions-intro.md to reduce the concept density. Keep the single
annotated example workflow, but add one short "Try it" code block immediately after the
annotated example asking the learner to open a real workflow file in their repo and label
each of the four primitives (trigger, job, runner, step) themselves, turning passive reading
into an active-recall checklist item. Consider moving less essential vocabulary (e.g., detailed
discussion of "action" as distinct from "step") into a linked reference page or a collapsible
<details> aside, so the core page introduces at most 15-18 new terms before the checkpoint.
Expected Score After Fix: 6.5-7.0 / 10.0
Generated by 🔬 Curriculum Quality Evaluator · copilot · auto · 96.9 AIC · ⌖ 19.9 AIC · ⊞ 10.4K · ◷
- expires on Oct 8, 2026, 11:43 PM UTC
- Dominant language
- JavaScript
- Stars
- 52
- Forks
- 26
- Avg merge
- 12h 25m
- Merged PRs (30d)
- 18
Getting set up
Starts the project's dev container in your browser, under your own GitHub account.
- No Dockerfile or Docker Compose file
- No pull request template
- No contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from githubnext/gh-aw-workshop
-
feedback simulation workshop
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
githubnext/gh-aw-workshop#4370 ·
Maintainers usually reply within 1 day
-
feedback simulation workshop
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
githubnext/gh-aw-workshop#4369 ·
Maintainers usually reply within 1 day
-
feedback simulation workshop
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
githubnext/gh-aw-workshop#4368 ·
Maintainers usually reply within 1 day
-
documentation
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
githubnext/gh-aw-workshop#4366 ·
Maintainers usually reply within 1 day
-
documentation
Difficulty 1/5 Under an hour Newbie friendliness 88/100
githubnext/gh-aw-workshop#4365 ·
Maintainers usually reply within 1 day
All issues in githubnext/gh-aw-workshop
Similar issues
-
[Bug] Composer can submit an IME confirmation when keyCode is 229 but isComposing is falsePossibly taken A pull request linked to this issue is open or already merged. Open
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
apache/rocketmq-dashboard#6067 ·
Maintainers usually reply within 4 days
-
severity: low
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
luainkernel/lunatik#1853 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
Maintainers usually reply within 1 day
-
factory-active factory-automatic harness/claude-code task-identify-harness-labels-done task-identify-issue-type-done
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
Maintainers usually reply within 1 day