Workshop sim repairs: skill cue, billing gate, mobile path (#1748)

* Initial plan

* Fix workshop simulation top-3 repairs: skill cue, billing gate, mobile path

Co-authored-by: pelikhan <4175913+pelikhan@users.noreply.github.com>

---------

Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com>
Co-authored-by: pelikhan <4175913+pelikhan@users.noreply.github.com>

Author: Copilot

workshop/01-prerequisites.md

@@ -20,6 +20,9 @@ If you are familiar with terminals, use your usual setup. We will go over the re
 
 If you choose the GitHub UI path, you can complete the main workshop steps in your browser and still run a real workflow from the Actions tab.
 
+> [!TIP]
+> On a mobile device or using GitHub Copilot (CCA/Agents tab) with no access to a terminal? Choose the **GitHub UI path** — no installation or terminal is required. You will create your repository on github.com and author workflows directly from the Copilot or Agents tab in your browser.
+
 ![Setup path decision diagram: choose between Codespace and Local Terminal based on your environment](images/01-setup-path-decision.svg)
 
 ## Verify AI engine access
@@ -41,3 +44,6 @@ Choose your adventure.
 <!-- journey: local -->
 **Next:** Open [Set Up Your Local Terminal](02b-setup-local.md).
 <!-- /journey -->
+<!-- journey: ui,copilot -->
+**Next:** On [github.com/new](https://github.com/new), create a public repository named `my-agentic-workflows`. Check **Add a README file** and click **Create repository**. Then continue to [GitHub UI Path — No Installation Needed](06c-install-ui.md).
+<!-- /journey -->

workshop/02a-setup-codespace.md

@@ -2,6 +2,9 @@
 <!-- page-adventure: setup -->
 # Set Up a Codespace _(recommended for new users)_
 
+> [!NOTE]
+> On a mobile device or working entirely in the browser without a terminal? This path opens a terminal inside your browser. If you cannot use a terminal at all, switch to the [GitHub UI path](06c-install-ui.md) instead.
+
 ## 🎯 What You'll Do
 
 You'll launch a GitHub Codespace for this workshop, open the built-in terminal, and land in a ready-to-use environment for the next step.

workshop/07c-your-first-workflow-copilot.md

@@ -20,22 +20,24 @@ Open your practice repository in the GitHub Copilot app and start a session in *
 Paste this prompt:
 
 ```text
-Initialize this repository for GitHub Agentic Workflows using https://raw.githubusercontent.com/github/gh-aw/main/install.md
-
-Then create a workflow for GitHub Agentic Workflows using https://raw.githubusercontent.com/github/gh-aw/main/create.md
+Using the agentic-workflows skill, initialize this repository for GitHub Agentic Workflows using https://raw.githubusercontent.com/github/gh-aw/main/install.md
+and then create a workflow using https://raw.githubusercontent.com/github/gh-aw/main/create.md
 
 The workflow must:
 - Be named "Daily Report Status"
 - Support manual runs with `workflow_dispatch`
 - Use `contents: read`, `issues: read`, and `copilot-requests: write`
-- Allow at most one comment and at most one new issue through [safe outputs](https://github.github.com/gh-aw/reference/safe-outputs/)
+- Allow at most one comment and at most one new issue through safe outputs (https://github.github.com/gh-aw/reference/safe-outputs/)
 - Search open issues for the issue with the most 👍 reactions and comment:
   "This issue has the most community support! We'll prioritise it in our next planning session."
 - Create an issue titled "Community Voting Test" and post the same comment if no open issues exist
 
 Run `gh aw compile` in the session workspace, fix any errors, commit the source and generated lock file (plus any initialized skill files), and open a pull request. Show me the diff before merging.
 ```
 
+> [!NOTE]
+> The `agentic-workflows` skill is installed as part of initialization. If the skill is not yet available in your repository, the agent falls back to the install and create URLs above and the skill becomes available for future sessions after the pull request is merged.
+
 The agent runs validation in its isolated session workspace. You do not need a terminal for this path.
 Before you approve the merge, the agent presents the file changes in its session response for you to review.
 

workshop/07d-confirm-model-access.md

@@ -82,6 +82,9 @@ Catching a billing or authentication problem here saves debugging time in Step 8
 3. Confirm you receive a reply. Any response means the model is accessible.
 4. If you see an error, revisit the billing path above before continuing.
 
+> [!IMPORTANT]
+> Do not continue to Step 8 if you received an error instead of a response. Fix the billing or authentication issue now — model-access errors will cause Step 8 to fail and are much harder to diagnose mid-run.
+
 ## ✅ Checkpoint
 
 - [ ] I confirmed the first workflow uses GitHub Copilot