[curriculum-eval] side-quest-17-07-repo-poisoning.md: cognitive_load — 1234 words and concept overload
Maintainers usually reply within 3 days
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 78/100
- Issue type
- Documentation
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- github-actions, javascript, markdown
- Domain
- content, documentation
Research direction
Read workshop/side-quest-17-07-repo-poisoning.md and review its Learning Objectives, exercises, and defence sections. Reduce the page to 800 words or fewer, move the specified defences into a table or new side quest, remove repeated links, and add a Checkpoint with at least four mapped items. Run npx --yes markdownlint-cli2 "**/*.md".
Written by the indexing model from the issue text.
Description
File: workshop/side-quest-17-07-repo-poisoning.md
Overall Score: 5.0 / 10.0 (corpus mean: 6.1)
Flagged Dimensions:
| Dimension | Score | Benchmark | Delta |
|---|---|---|---|
| cognitive_load | low (1234 words, concept_overload flagged) | ≤ 800 words, ≤ 15 concepts | −4 words/100 over |
| active_learning | low | density ≥ 3 | negative |
| checkpoint_quality | 0.0 (no Checkpoint heading; page ends with two exercises) |
≥ 4 items | −10 |
Root Cause (≤ 2 sentences):
The page covers the attack, rationale, and four distinct defences (read-only permissions, PR routing, path restriction, network limits) plus two exercises. Heavy inline doc links per heading add extraneous load.
Evidence (quoted from the file):
"## ✏️ Exercise: Spot the Dangerous Frontmatter" ... "## ✏️ Exercise: Harden Your Workflow"
Learning Science Rationale:
Cognitive Load Theory (Sweller) and the segmenting principle suggest splitting multi-defence content so each part fits working memory; adding a checkpoint supports retrieval practice and verifies the stated learning objectives.
Improvement Prompt (for an agent):
Edit workshop/side-quest-17-07-repo-poisoning.md: cut to ≤ 800 words by merging "Why This Matters" into the intro and moving the "Limit network destinations" and "Restrict which paths can change" defences into a short table or a new side quest; move repeated hyperlinks to first use only. Add a final "## :white_check_mark: Checkpoint" with ≥ 4 checklist items mapped to the Learning Objectives. Run `npx --yes markdownlint-cli2 "**/*.md"`.
Expected Score After Fix: 6.8 / 10.0
Generated by 🔬 Curriculum Quality Evaluator · copilot · auto · ~36 AIC · ⌖ ~1 AIC · ⊞ 5K · ◷
- expires on Nov 7, 2026, 7:04 AM UTC
- Dominant language
- JavaScript
- Stars
- 58
- Forks
- 40
- Avg merge
- 4d 4h
- Merged PRs (30d)
- 8
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
-
curriculum documentation quality
Difficulty 2/5 1-3 hours Newbie friendliness 77/100
githubnext/gh-aw-workshop#5437 ·
Maintainers usually reply within 3 days
-
curriculum documentation quality
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
githubnext/gh-aw-workshop#5436 ·
Maintainers usually reply within 3 days
-
curriculum documentation quality
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
githubnext/gh-aw-workshop#5434 ·
Maintainers usually reply within 3 days
-
curriculum documentation quality
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
githubnext/gh-aw-workshop#5433 ·
Maintainers usually reply within 3 days
-
documentation
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
githubnext/gh-aw-workshop#5427 ·
Maintainers usually reply within 3 days
All issues in githubnext/gh-aw-workshop
Similar issues
-
stringify escapes leading digits in pseudo-class arguments (:nth-child(1) becomes :nth-child(\31 ))Open
Difficulty 2/5 1-3 hours Newbie friendliness 83/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
digitalbazaar/forge#1170 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
getgrav/grav-plugin-form#664 ·
-
bug web-ui
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
jenkinsci/jenkins#27705 · 3 comments ·
Maintainers usually reply within 1 day