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

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

Closed Beginner friendly
  • Is something wrong?
#4,495 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
75/100
Issue type
Documentation
Clarity
Clearly specified
Activity status
Active
Tech stack
github, javascript, yaml
Domain
documentation

Research direction

Start by reading 05-agentic-workflows-intro.md and locate “Activity 2 — agentic or standard?” and Activity 3. Add a short exercise between them that directs learners to a sample .lock.yml and asks them to find the safe-outputs guardrail. Done when the quantitative scores stay flat or improve and the existing activities and final checklist remain intact.

Written by the indexing model from the issue text.

Description

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
Dominant language
JavaScript
Stars
53
Forks
35
Avg merge
13h 50m
Merged PRs (30d)
14

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.