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

已关闭 适合新手
  • 哪里不对？
#4,966 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
2/5
预计耗时
半天
新手友好度
85/100
Issue 类型
文档
描述清晰度
描述清楚
活跃度
活跃
技术栈
markdown, node.js
领域
content

调研方向

要编辑的文件是 workshop/side-quest-17-07-repo-poisoning.md；阅读它以定位被标记的长篇散文和 YAML 片段。按照提示删减到 ≤900 词，用学习者立即执行的动作重组防御，并保留所需章节。当它通过 npx --yes markdownlint-cli2 "workshop/side-quest-17-07-repo-poisoning.md" 并保留检查点项时完成。

由索引模型根据 Issue 内容生成。

描述

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 ≥ 9 (≤ 800 words, ≤ 15 concepts) −3.2
active_learning 2.7 ≥ 10 (density ≥ 3) −7.3

(checkpoint_quality 0.0 / scaffolding 5.0 are rubric artifacts — see the separate rubric-regex issue.)

Root Cause (≤ 2 sentences):
The page packs 1234 words, 23 new concepts and 9 H2 sections (attack explanation, three defences, two exercises, author guidance) into one side quest, giving an activity density of only 0.81. Long explanatory prose and large YAML snippets precede the first exercise at line 125.

Evidence (quoted from the file):

Objectives: "Explain what repository poisoning is...", "Identify dangerous permissions: and toolsets: values...", "Apply the three gh-aw defences: contents: read, safe-outputs: create-pull-request, and network.allowed-domains."

Learning Science Rationale:
Sweller's Cognitive Load Theory predicts that intrinsic load rises with the number of interacting elements; 23 new concepts before the first practice activity exceeds working-memory capacity. Segmenting (Mayer) and interleaving short practice after each defence would move learners from reading to doing earlier.

Improvement Prompt (for an agent):

Edit workshop/side-quest-17-07-repo-poisoning.md. Cut it to ≤ 900 words and ≤ 15 new concepts: tighten "The Attack" and "Why This Matters" to a short paragraph each, and move the long YAML snippets under "How AW Defends Against It" into one compact before/after example. Introduce each of the three defences with a 1-line explanation followed immediately by a one-step learner action (a code block plus checklist item). Keep the Learning Objectives, the ":clipboard: Before You Start" section and the ":white_check_mark: Checkpoint" section (≥ 4 verifiable items). No numbered headings. Run `npx --yes markdownlint-cli2 "workshop/side-quest-17-07-repo-poisoning.md"`.

Expected Score After Fix: 6.5 / 10.0 (≈ 8.0 once the rubric regex fix lands)

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

  • expires on Oct 26, 2026, 3:44 AM UTC
主要语言
JavaScript
星标
56
派生
40
平均合并
2 天 14 小时
30 天内合并 PR
13

环境准备

在 Codespaces 中打开

在浏览器里用你自己的 GitHub 账号启动这个项目的开发容器。

  • 没有 Dockerfile 或 Docker Compose 文件
  • 没有 Pull Request 模板
  • 没有贡献指南

从这里开始

  1. 先读完整个 Issue，再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库，在一个分支上完成修改。
  4. 提交 Pull Request，并在描述里引用这个 Issue 编号。

githubnext/gh-aw-workshop 的其他 Issue

查看 githubnext/gh-aw-workshop 的全部 Issue

相似的 Issue

更多 JavaScript Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。