[curriculum-eval] side-quest-17-07-repo-poisoning.md: cognitive_load — 23 concepts and 1,234 words in one page

Open Beginner friendly
  • Is something wrong?
#5,360 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 3 days

Nobody has claimed this yet.

Assessment

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

Research direction

Start with workshop/side-quest-17-07-repo-poisoning.md and check its current length, concept count, exercise placement, and Checkpoint against the evaluator's findings. Refactor the page to at most 900 words and 15 new concepts, keep the named sections and valid links, and update workshop/README.md if you add a file. Run markdownlint; done when the retained content matches the Checkpoint and the page meets the stated limits.

Written by the indexing model from the issue text.

Description

curriculum documentation quality

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 5.8 (1,234 words, 23 concepts) ≤ 800 words, ≤ 15 concepts −4.2
active_learning 2.7 (density 0.81) ≥ 3 density −7.3

(missing_checkpoint dismissed: the page has a 6-item Checkpoint; scorer false positive.)

Root Cause (≤ 2 sentences):
The page covers the attack, four distinct defences (read-only permissions, PR-routed writes, protected paths, network restriction), two exercises and an author summary in one sitting. 23 new concepts are 8 above the benchmark.

Evidence (quoted from the file):

"Repository poisoning is what happens when a misdirected agent with write access commits changes an attacker designed — not changes the workflow author intended."

Learning Science Rationale:
Sweller's Cognitive Load Theory and Miller's 7±2 limit predict that learners cannot integrate 20+ novel terms in one sitting; worked-example and segmenting principles favour pairing each defence with its own short practice. The existing "Spot the Dangerous Frontmatter" exercise is the strongest part, but it arrives only after four defences have been presented.

Improvement Prompt (for an agent):

Refactor workshop/side-quest-17-07-repo-poisoning.md to ≤ 900 words and ≤ 15 new concepts. Option: keep the attack, the "Spot the Dangerous Frontmatter" exercise and the two most important defences (contents: read, safe-outputs create-pull-request) in this page; move the protected-files and network-allowed-domains defences into a short second side quest, or into collapsed <details> blocks. Put a quick frontmatter-spotting activity directly after each defence instead of at the end. Keep :clipboard: Before You Start and :white_check_mark: Checkpoint (≥ 4 verifiable items), update the Checkpoint to match the retained content, keep links valid and update workshop/README.md if a file is added. Run markdownlint.

Expected Score After Fix: 5.8 / 10.0 with current scorer (≈ 8.3 after the scorer fix)

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

  • expires on Nov 6, 2026, 3:32 AM UTC
Dominant language
JavaScript
Stars
58
Forks
40
Avg merge
4d 4h
Merged PRs (30d)
8

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.