[curriculum-eval] side-quest-17-07-repo-poisoning.md: cognitive_load — 23 concepts in 1234 words, 9 sections

Open Beginner friendly
#5,777 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
76/100
Issue type
Documentation
Clarity
Clearly specified
Activity status
Active
Tech stack
github, markdown
Domain
documentation

Research direction

Read workshop/side-quest-17-07-repo-poisoning.md, focusing on “Why This Matters,” “The Attack,” and the four defence sections. Shorten the page to at most 900 words and 15 new concepts, add a brief “Try it” action after each remaining defence, and link to 31-control-network-access.md for network limits. Keep the specified start and checkpoint sections with at least four verifiable items, then run npx --yes markdownlint-cli2 "**/*.md".

Written by the indexing model from the issue text.

Description

curriculum documentation quality

File: workshop/side-quest-17-07-repo-poisoning.md
Overall Score: 4.95 / 10.0 (corpus mean: 6.06)

Flagged Dimensions:

Dimension Score Benchmark Delta
cognitive_load 5.8 ≤ 800 words, ≤ 15 concepts (actual 1234 words, 23 concepts) −4.2
active_learning 2.7 density ≥ 3 (actual 0.81) −7.3

Root Cause (≤ 2 sentences):
The page introduces the attack plus four defences (read-only permissions, PR routing, path restriction, network limits) and two exercises in one sitting. Four code blocks across 1234 words leave activity density at 0.81. (The missing-checkpoint flag is a false positive; the page has a 6-item checkpoint.)

Evidence (quoted from the file):

### Declare read-only permissions / ### Route writes through a pull request / ### Restrict which paths can change / ### Limit network destinations

Four defences are explained in prose before the first exercise.

Learning Science Rationale:
Sweller's Cognitive Load Theory and the worked-example effect suggest interleaving each new concept with a short practice task rather than front-loading all explanation. Mayer's segmenting principle supports the same split. Pairing each defence with a micro-exercise would raise activity density and lower intrinsic load.

Improvement Prompt (for an agent):

Edit workshop/side-quest-17-07-repo-poisoning.md. Reduce to ≤ 900 words and ≤ 15 new concepts: shorten "Why This Matters" and "The Attack", and move "Limit network destinations" to a link into 31-control-network-access.md. After each remaining defence, add a 1–2 line "Try it" action (a frontmatter edit or `gh aw compile` check). Keep the `## :clipboard: Before You Start` and `## :white_check_mark: Checkpoint` sections with ≥ 4 specific, verifiable items (remove the network item if the section moves). Do not number headings; run `npx --yes markdownlint-cli2 "**/*.md"`.

Expected Score After Fix: 7.8 / 10.0 (includes rubric-bug fix; about 5.8 from content changes alone)

Generated by 🔬 Curriculum Quality Evaluator · copilot · auto · ~47 AIC · ⌖ ~1 AIC · ⊞ 5K · ◷

  • expires on Nov 17, 2026, 3:03 AM UTC
Dominant language
JavaScript
Stars
62
Forks
43
Avg merge
11h 26m
Merged PRs (30d)
13

Getting set up

Open in Codespaces

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

  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.