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

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

Closed Beginner friendly
#4,784 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
74/100
Issue type
Documentation
Clarity
Clearly specified
Activity status
Active
Tech stack
github-actions, markdown
Domain
documentation

Research direction

Read workshop/side-quest-17-07-repo-poisoning.md and follow its four defence subsections and the “Spot the Dangerous Frontmatter” exercise. Move detail on network allowed-domains and protected-files to links to the gh-aw docs, and add a short try-it action after each defence. Keep the checkpoint at four or more items, meet the stated word and concept limits, then run markdownlint.

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

Flagged Dimensions:

Dimension Score Benchmark Delta
cognitive_load 5.8 ≥ 8 −2.2
active_learning 2.7 ≥ 7 −4.3

Root Cause (≤ 2 sentences):
The page introduces 23 concepts (permissions, safe-outputs, protected-files, allowed-domains, attack model) in 1234 words with density 0.81. Four defences are explained in prose before any learner activity.

Evidence (quoted from the file):

How AW Defends Against It (four subsections before the first exercise at 'Spot the Dangerous Frontmatter')

Learning Science Rationale:
Cognitive Load Theory and the segmenting principle (Mayer) recommend learner-paced chunks; interleaving explanation with an action after each defence reduces intrinsic load and improves transfer.

Improvement Prompt (for an agent):

Edit workshop/side-quest-17-07-repo-poisoning.md: reduce to ≤ 900 words and ≤ 15 new concepts by moving detail on network allowed-domains and protected-files to links to the gh-aw docs; place a short 'try it' code/checklist action after each defence subsection. Keep the checkpoint with ≥ 4 items. Run markdownlint.

Expected Score After Fix: 6.2 / 10.0

Generated by 🔬 Curriculum Quality Evaluator · copilot · auto · 27 AIC · ⌖ 0.765 AIC · ⊞ 10.4K · ◷

  • expires on Oct 21, 2026, 4:41 AM UTC
Dominant language
JavaScript
Stars
55
Forks
36
Avg merge
2d 6h
Merged PRs (30d)
18

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.