[curriculum-eval] side-quest-17-07-repo-poisoning.md: cognitive_load — 1,234 words and 23 concepts for one attack/defence lesson

Aperta Adatta ai principianti
#5,817 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
2/5
Tempo stimato
1-3 ore
Idoneità per principianti
72/100
Tipo di issue
Documentazione
Chiarezza
Specificata chiaramente
Stato di attività
Attiva
Stack tecnologico
github-actions, javascript, markdown

Direzione di ricerca

Read workshop/side-quest-17-07-repo-poisoning.md and review its existing learning objectives, Before You Start section, examples, and checkpoint. Restructure the lesson around one vulnerable frontmatter example, with three numbered defence steps and verification commands; move extended theory and the enterprise note into <details> blocks. Done means the page is at most 900 words, retains at least four verifiable checkpoint items, and passes the requested markdownlint command.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

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

(checkpoint_quality 0.0 is the regex defect; the page has 6 items.)

Root Cause (≤ 2 sentences):
The page introduces the attack, three separate defences (contents: read, safe-outputs: create-pull-request, network.allowed-domains) and protected-files in one sitting, with only 4 code blocks. Prose dominates over practice.

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) and the worked-example effect suggest that novices learn security patterns best from a short vulnerable/fixed contrast followed by a guided exercise. Presenting three defences at once raises intrinsic load; sequencing them as incremental fixes to one example reduces it and gives each concept a retrieval opportunity.

Improvement Prompt (for an agent):

Edit workshop/side-quest-17-07-repo-poisoning.md to ≤ 900 words. Restructure around ONE vulnerable frontmatter example and apply the three defences as three short numbered steps, each with a before/after code block and a one-line verification command (e.g. gh aw compile). Move extended theory and the enterprise NOTE into <details> blocks. Keep learning objectives, the Before You Start section, and a "## :white_check_mark: Checkpoint" with ≥ 4 verifiable items. No numbered headings; max 3 callouts. Run `npx --yes markdownlint-cli2 "**/*.md"`.

Expected Score After Fix: 6.3 / 10.0 (≈ 8.0+ after the checkpoint regex fix)

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

  • expires on Nov 18, 2026, 3:32 AM UTC
Lingua principale
JavaScript
Stelle
62
Fork
43
Merge medio
11h 26m
PR unite (30g)
13

Preparare l'ambiente

Apri in Codespaces

Avvia il container di sviluppo del progetto nel browser, con il tuo account GitHub.

  • Nessun Dockerfile né file Docker Compose
  • Nessun modello di pull request
  • Nessuna guida per i contributori

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di githubnext/gh-aw-workshop

Tutte le issue di githubnext/gh-aw-workshop

Issue simili

Altre issue su JavaScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.