Hacktoberfest 2026：维护者为十月标记出来的 issue，仍然开放、适合新手。 浏览 Hacktoberfest issue

[workshop-sim] Improve: Add worked safe-outputs artifact activity to Step 5

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

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
2/5
预计耗时
1-3 小时
新手友好度
75/100
Issue 类型
文档
描述清晰度
描述清楚
活跃度
活跃
技术栈
github, javascript, yaml
领域
documentation

调研方向

先阅读 05-agentic-workflows-intro.md，并找到“Activity 2 — agentic or standard?”和 Activity 3。在两者之间添加一个简短练习，引导学习者查看一个示例 .lock.yml，并要求他们找出 safe-outputs 防护措施。完成标准是定量评分持平或有所提高，且现有活动和最终检查清单保持完整。

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

描述

feedback simulation workshop

Problem statement

05-agentic-workflows-intro.md has the second-highest conditional dropout (19.6%, 7,717 of 39,460 at-risk runs), dominated by agentic-concept-gap (5,472 failures) and deployment-capability-gap (2,245 failures). The page's active_learning rubric score is only 2.4/10 — the lowest of any top-5 dropout step — even though it already contains three "Activity" blocks and a two-file (.md/.lock.yml) prediction exercise. The activities are mostly reveal/predict exercises without a worked example that ties the abstract "agentic vs. standard" distinction to a concrete artifact the learner can inspect in their own repository.

Proposed change

Add one additional hands-on micro-activity immediately after "Activity 2 — agentic or standard?": have the learner open a real .lock.yml file from a sample agentic workflow (link to an example in githubnext/gh-aw-workshop or a generated sample) and find the specific YAML block that encodes the task brief's safe-outputs guardrail, connecting the abstract safe-outputs term to a concrete repository artifact before Activity 3's task-brief-writing exercise. This increases hands-on activity density (activity_density) without adding conceptual density (no new terms), which should raise active_learning directly.

Failure mode classification

Learning barrier (conceptual density / insufficient scaffolding connecting abstract terms to concrete artifacts — not an access or tooling issue).

Quantitative guardrail

Current scores for 05-agentic-workflows-intro.md:

  • overall_score: 5.43/10
  • Weakest rubric dimensions: checkpoint_quality (0.0/10) and active_learning (2.4/10)
  • Learning KPI index: 2.24/10 (active_learning 2.4, checkpoint_quality 0.0, scaffolding 5.0)

The proposed change adds one concrete, code-block-based activity (raising activity_density and thus active_learning) without adding new vocabulary (so cognitive_load's new_concepts penalty does not worsen) and without removing the existing checklist or prerequisite section (checkpoint_quality and scaffolding unaffected). overall_score and the learning KPI index should therefore improve, not just completion.

Acceptance criteria

  • The shared curriculum quantitative assessment overall_score for 05-agentic-workflows-intro.md stays flat or improves after the change
  • The step's learning KPI index ((2.0 × active_learning + 2.0 × checkpoint_quality + 1.5 × scaffolding) / 5.5) stays flat or improves
  • Hands-on practice, checkpoints, and scaffolding are preserved or strengthened — the three existing activities and the final checklist remain intact
  • The new activity links an abstract term (safe outputs) to a concrete, inspectable .lock.yml artifact and does not introduce new unexplained vocabulary

Suggested owner

copilot coding agent
Related to #4493

Generated by 🔬 Workshop Student Simulator · copilot · auto · 309.7 AIC · ⌖ 14.8 AIC · ⊞ 15.1K · ◷

  • expires on Oct 13, 2026, 8:28 AM UTC
主要语言
JavaScript
星标
53
派生
35
平均合并
1 天 5 小时
30 天内合并 PR
16

环境准备

在 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 摘要。