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

Open Beginner friendly
  • Is something wrong?
#5,511 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
82/100
Issue type
Documentation
Clarity
Clearly specified
Activity status
Active
Tech stack
javascript, markdown
Domain
content, documentation

Research direction

Start with workshop/side-quest-17-07-repo-poisoning.md and review the sections "The Attack" and "Why This Matters," the defenses, and both exercises. Shorten the page to at most 900 words and 15 new concepts, move the protected-files and network.allowed-domains details to a reference or follow-on page, and place a hands-on frontmatter edit after each defense. Keep checkpoint items verifiable and headings unnumbered; run the stated markdownlint command.

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.1)

Flagged Dimensions:

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

Root Cause (≤ 2 sentences):
The page covers the attack, rationale, defenses (contents: read, safe-outputs, protected-files, network.allowed-domains) and two exercises in one sitting. Long prose sections precede the first hands-on exercise.

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:
Cognitive Load Theory (Sweller) holds that novices exceed working-memory limits when many new elements are introduced before they are practised; the expertise-reversal and worked-example effects suggest interleaving short explanations with immediate practice instead of front-loading theory.

Improvement Prompt (for an agent):

Edit workshop/side-quest-17-07-repo-poisoning.md to ≤ 900 words and ≤ 15 new concepts: shorten "The Attack" and "Why This Matters", move `protected-files` and `network.allowed-domains` details to a linked reference or a follow-on side quest, and interleave a small hands-on frontmatter edit right after each defense is explained. Keep the checkpoint items verifiable, keep headings unnumbered, update workshop/README.md if you add a page, and run npx --yes markdownlint-cli2 "**/*.md".

Expected Score After Fix: 6.5 / 10.0 (before scorer fix)

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

  • expires on Nov 10, 2026, 4:04 AM UTC
Dominant language
JavaScript
Stars
58
Forks
40
Avg merge
1d 22h
Merged PRs (30d)
7

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.