Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

[curriculum-eval] 05-agentic-workflows-intro.md: active_learning — prose-based activities undercounted, missing in-context self-checks

Open Beginner friendly
#3,896 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
1/5
Estimated time
Under an hour
Newbie friendliness
94/100
Issue type
Documentation
Clarity
Clearly specified
Activity status
Active
Tech stack
github-actions, markdown
Domain
documentation

Research direction

Open workshop/05-agentic-workflows-intro.md and review the three existing activities, including the Activity 1 prediction, Activity 2 Task A and B reveals, and Activity 3 task-brief exercise. Add the specified standalone self-check checklist line after each activity, then verify each appears in context and remains separate from the final Checkpoint section.

Written by the indexing model from the issue text.

Description

curriculum documentation quality

File: workshop/05-agentic-workflows-intro.md
Overall Score: 5.43 / 10.0 (corpus mean: 6.09)
Corrected Overall Score (after fixing the checkpoint/scaffolding regex bug reported separately): 8.18 / 10.0 — active_learning remains the residual gap.

Flagged Dimensions:

Dimension Score Benchmark Delta
active_learning 2.4 density ≥ 3 (code blocks + checklist items per 100 words) -0.6 (density 0.72; only 2 code blocks + 0 checklist items across 1107 words)
cognitive_load 8.5 ≤800 words -1.5 (1107 words)

Root Cause (≤ 2 sentences):
The page contains three genuinely interactive prediction/reveal activities ("Activity 1", "Activity 2", "Activity 3"), but they are authored entirely as prose with <details> reveal blocks and a single fenced comment-only code block, so the automated activity_density metric (which only counts fenced code blocks and - [ ] checklist lines) undercounts the real interactivity present. The result is a page that reads as interactive to a human but scores as passive to the rubric.

Evidence (quoted from the file):

"Activity 1 — identify the parts: Open any .lock.yml file in your repo and find the on: key. That is the compiled trigger that came from your frontmatter."

"Now check your prediction: did you name both files and identify which one Actions runs (.lock.yml)?"

This is a real hands-on activity (open a file, find a key, self-check), but it has no checklist item and only a comment-only code fence, so it contributes almost nothing to the activity_density score.

Learning Science Rationale:
Mayer's active-processing principle predicts that generative activities (predict-then-reveal, retrieve-then-check) support learning regardless of format, but the rubric's activity_density proxy (code blocks + checklists per 100 words) is a narrow operationalization that misses prose-based generative activities. Independent of the scoring artifact, converting these activities into an explicit self-check checklist item each would both genuinely reinforce retrieval practice (testing effect) and make the existing interactivity legible to the assessment tool — a low-cost win that improves both real pedagogy and measured quality.

Improvement Prompt (for an agent):

In workshop/05-agentic-workflows-intro.md, add a one-line self-check checklist item immediately after each of the three existing activities, so the interactivity already present is captured explicitly:

1. After "Now check your prediction: did you name both files and identify which one Actions runs (`.lock.yml`)?" (end of Activity 1), add:
   - [ ] I named both files and identified that `.lock.yml` is what GitHub Actions runs

2. After the Task A and Task B reveal blocks in Activity 2, add:
   - [ ] I correctly classified both Task A (standard) and Task B (agentic) before revealing the answers

3. After Activity 3's task-brief writing exercise, add:
   - [ ] I wrote a one-sentence task brief and compared it against the example

Keep these as standalone checklist lines (not merged into the final Checkpoint section) so they read as in-context self-checks during the activity, not duplicate the final checkpoint items.

Expected Score After Fix: ≈8.5 / 10.0 (activity_density rises from 0.72 toward ~1.3 with three added checklist lines across 1107 words; combined with the companion checkpoint/scaffolding regex fix already applied in the corrected baseline).

Generated by 🔬 Curriculum Quality Evaluator · copilot · auto · 147.3 AIC · ⌖ 18.6 AIC · ⊞ 9K · ◷

  • expires on Sep 28, 2026, 9:51 AM UTC
Dominant language
JavaScript
Stars
49
Forks
20
Avg merge
7h 12m
Merged PRs (30d)
26

Getting set up

We have not checked this project's setup files yet. Start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from githubnext/gh-aw-workshop

All issues in githubnext/gh-aw-workshop

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.