# Skills workshop: every step, for Claude and Codex Choose ONE route in class. Keep the same app and model for the without/with comparison. Product steps checked 15 October 2026. ### Before you start · choose one app 1. Choose **Claude** or **Codex** with the buttons above. You only need to complete one route in class. The other is available to repeat at home. 2. Download [exec-summary.zip](exec-summary.zip), [star-feedback.zip](star-feedback.zip), [test-inputs.md](test-inputs.md) and [scorecard.md](scorecard.md). The ZIP links download files, not websites. 3. Keep this guide open in a separate browser tab. Open your chosen app beside it, or switch between windows as you work. 4. Prepare a place to save three answers: **Without skill**, **With skill** and **Edited skill**. A text note is enough. The checkboxes and scorecard on this page save progress in this browser when storage is available; they do not save the AI’s answers. 5. Run the baseline before installation. Stay with the same app and model. A Claude-versus-Codex comparison changes the model as well as the context. **Checkpoint:** You have all four files, this guide, your chosen app, and somewhere to keep your outputs. Allow extra setup time on a new account; do setup before class if possible. ## Claude route ### 1. Open Claude and check access 1. Open a browser and go to [claude.ai](https://claude.ai). Sign in. 2. Open your profile or account menu, then **Settings**. 3. Open **Capabilities**. Turn on **Code execution and file creation**. If it is already on, leave it on. 4. Open **Customize → Skills**. Free accounts are supported; an organization can still restrict access. 5. If `exec-summary` or `star-feedback` is already listed, turn its toggle off for now. Leave unrelated settings the same throughout the comparison. 6. Return to the chat screen. Choose an ordinary chat outside an existing Claude Project, so project instructions do not affect this exercise. **Checkpoint:** You can open the Skills page. Neither workshop skill is enabled. If access is blocked, use the troubleshooting section or pair with a neighbour. ### 2. Run the task without the skill 1. Click **New chat**. Do not use an old conversation. 2. Look at the model selector and note the selected model in your notes. Keep that same model for the next run. 3. Use **Copy Pedala prompt** below. Click the empty message box and paste with **⌘V** on Mac or **Ctrl+V** on Windows. 4. Check that the message starts “Summarise these notes for my manager:” and includes all the call notes. Do not add formatting instructions or a skill name. 5. Click the send arrow. Wait until the answer is finished. 6. Copy the answer into a note called **Without skill**, or keep this conversation open. Do not rely on remembering what it said. 7. Use the scorecard below. Read the answer against each check; record the five scores in the **Without** column for Claude. **Checkpoint:** You have one saved baseline answer and a score out of 5. You have not uploaded or enabled exec-summary yet. **Pedala prompt:** ```text Summarise these notes for my manager: Call notes– Pedala (e-bike subscriptions, Barcelona) – Tuesday - attendees: Marta (CEO), Jordi (ops), us - ~1,200 active subscribers; monthly churn up from 4% to 7% since June!! - Jordi thinks it's repair wait times: avg 6 days now vs 2 days in spring. Their mechanic left in May - Marta more worried about new competitor BiciYa, launched at €29/month vs Pedala €39/month - exit survey: 140 responses, 58% of churned users mention repairs, 22% mention price - runway ~9 months - options discussed: hire 2 mechanics (~€6k/month total), cut price to €32, or partner with a repair shop in Gràcia (no quote yet) - Marta wants a decision before the board meeting on 15 Nov - we owe them a recommendation by next Friday - someone mentioned Valencia expansion but parked (Pedala and BiciYa are fictional companies made up for this exercise.) ``` ### 3. Upload and enable exec-summary 1. Return to **Customize → Skills**. 2. If an exec-summary entry already exists, do not upload a duplicate. Ask a helper to preserve and remove that workshop copy before continuing. If it is a personal skill you need to keep, pair with someone else for this route. 3. Click **+**, then **Create skill**, then **Upload a skill**. Labels can vary slightly between builds. 4. In the file picker, open **Downloads** or the folder where you saved the kit. 5. Select **exec-summary.zip**, then click **Open** to upload. Choose the ZIP, not the extracted Markdown file. 6. Wait for upload or any organization scan to finish. If an error appears, read it before retrying. 7. Find **exec-summary** in the skills list. Switch its toggle **on**. Keep star-feedback off. **Checkpoint:** exec-summary appears in the Skills list and is enabled. A successful upload alone is not the same as an enabled skill. ### 4. Repeat the exact task with the skill 1. Click **New chat** again. Do not continue the baseline chat. 2. Check that the model matches your baseline. Keep other settings unchanged. 3. Copy and paste the **same Pedala prompt** using the button below. Do not add “use the skill” on this first attempt. 4. Send it and wait for the answer to finish. 5. If Claude exposes its work trace, expand it and look for a read of `exec-summary/SKILL.md`. Some builds do not expose every file read; record **unknown** if you cannot tell. 6. Save the answer as **With skill**. Fill the **With** column in the Claude scorecard. 7. Compare the two answers: recommendation, three reasons, word count, source numbers and final next step. A tie is a valid result. **Checkpoint:** You have two answers from fresh chats, the same model and prompt, and two scores. Record whether you observed a skill-file read separately from the score. **the same Pedala prompt:** ```text Summarise these notes for my manager: Call notes– Pedala (e-bike subscriptions, Barcelona) – Tuesday - attendees: Marta (CEO), Jordi (ops), us - ~1,200 active subscribers; monthly churn up from 4% to 7% since June!! - Jordi thinks it's repair wait times: avg 6 days now vs 2 days in spring. Their mechanic left in May - Marta more worried about new competitor BiciYa, launched at €29/month vs Pedala €39/month - exit survey: 140 responses, 58% of churned users mention repairs, 22% mention price - runway ~9 months - options discussed: hire 2 mechanics (~€6k/month total), cut price to €32, or partner with a repair shop in Gràcia (no quote yet) - Marta wants a decision before the board meeting on 15 Nov - we owe them a recommendation by next Friday - someone mentioned Valencia expansion but parked (Pedala and BiciYa are fictional companies made up for this exercise.) ``` ### 5. Open the skill file on your laptop 1. Open **Finder → Downloads** on Mac or **File Explorer → Downloads** on Windows. Find `exec-summary.zip`. 2. **Mac:** double-click the ZIP. **Windows:** right-click it, choose **Extract All**, then **Extract**. 3. Open the extracted folders until you see the file `SKILL.md`. The folder immediately containing that file should be called `exec-summary`. 4. **Mac:** right-click `SKILL.md` → **Open With → TextEdit** (or a plain-text editor). **Windows:** right-click → **Open with → Notepad**. Do not use Word. 5. You should see the raw text, including `---`, `name:` and `description:` near the top. Keep those header lines unchanged. **Checkpoint:** You are editing the actual SKILL.md file in the extracted exec-summary folder, not the ZIP or a formatted preview. ### 6. Change 120 to 60, then save 1. Find the exact line `- 120 words maximum in total. Count before you answer.` under **Rules**. 2. Replace only `120` with `60`. Leave the rest of the file unchanged. 3. Save with **⌘S** on Mac or **Ctrl+S** on Windows. If TextEdit offers a rich-text format, choose **Format → Make Plain Text** before saving. 4. Confirm the filename is still `SKILL.md`, not `SKILL.md.txt` or `SKILL.md.rtf`. On Windows, enable **View → Show → File name extensions** if the ending is hidden. 5. Close the editor, then reopen the file. Check that the saved line now says `60 words maximum`. **Checkpoint:** The saved source file contains the 60-word rule. Changing a local file has not yet updated the skill uploaded to Claude. ### 7. Upload the edited version 1. In Finder or File Explorer, go up one level so you can see the **exec-summary folder**. Select the folder itself, not only SKILL.md. 2. **Mac:** right-click → **Compress “exec-summary”**. **Windows:** right-click → **Compress to ZIP file**, or **Send to → Compressed (zipped) folder**. 3. Rename the new archive `exec-summary-60.zip` so you can distinguish it from the original download. Leave the folder inside it named `exec-summary`. 4. Inspect the new ZIP. It should contain `exec-summary/SKILL.md`. Open the file inside it if needed to confirm the 60-word rule is present. 5. Back in Claude, open **Customize → Skills → exec-summary**. Disable it, then use **… → Delete** and confirm removal of that workshop skill. Your local source file and ZIP remain on your laptop. 6. Use **+ → Create skill → Upload a skill** again. Select `exec-summary-60.zip`. Wait for completion and enable the uploaded skill. **Checkpoint:** Claude has one enabled exec-summary entry containing your new version, rather than two competing copies. ### 8. Test your one-line edit 1. Start another **New chat**. Use the same model and the same Pedala prompt. 2. Send it and save the answer as **Edited skill — 60 words**. 3. Count all words in the answer, including the labels. You can paste the answer into a word-count tool, or use the count-only prompt below as a quick check and verify its result. 4. Compare the answer with the earlier 120-word version. Did it follow the shorter limit and still preserve the key recommendation? 5. Record what changed in the Exercise 2 note. Do not reuse the original word-limit score as the only check; this time your target is **60**. **Checkpoint:** You changed the stored instructions, reinstalled them, and checked the new behavior in a fresh chat. **Pedala prompt:** ```text Summarise these notes for my manager: Call notes– Pedala (e-bike subscriptions, Barcelona) – Tuesday - attendees: Marta (CEO), Jordi (ops), us - ~1,200 active subscribers; monthly churn up from 4% to 7% since June!! - Jordi thinks it's repair wait times: avg 6 days now vs 2 days in spring. Their mechanic left in May - Marta more worried about new competitor BiciYa, launched at €29/month vs Pedala €39/month - exit survey: 140 responses, 58% of churned users mention repairs, 22% mention price - runway ~9 months - options discussed: hire 2 mechanics (~€6k/month total), cut price to €32, or partner with a repair shop in Gràcia (no quote yet) - Marta wants a decision before the board meeting on 15 Nov - we owe them a recommendation by next Friday - someone mentioned Valencia expansion but parked (Pedala and BiciYa are fictional companies made up for this exercise.) ``` **word-count check:** ```text Count the words in the assistant's summary immediately above, including its labels. Report the count only. Do not rewrite the summary. ``` ### 9. Test when the skill activates 1. Keep the edited exec-summary enabled. Open **New chat**, paste the Peru prompt below, and send. 2. Inspect the visible work trace if available. Record **Yes**, **No** or **Unknown** for whether the skill was read. The prediction is **No**. 3. Open another **New chat**. Paste the article prompt below, including its full article, and send. Prediction: **Yes**. 4. Open a third **New chat**. Paste the Barcelona poem prompt and send. Prediction: **No**. 5. Record all three observations. Do not put the tests in one conversation, and do not force a skill name into these test prompts. **Checkpoint:** You tested three separate requests and distinguished expected activation from what you could actually observe. **Peru test:** ```text What's the capital of Peru? ``` **article test:** ```text Can you condense this article into something my boss can read in 30 seconds? Campus bike repair pilot The student services team tested a bike repair desk for 4 weeks. It served 80 students, and 60 booked a second visit. Average turnaround was 2 days, compared with 5 days at the previous provider. The pilot cost €1,600. The team has a €2,000 budget for next month. It has not yet checked whether the provider can handle twice as many bookings. Ana will collect a capacity quote by Friday. The committee must decide on Monday whether to extend the pilot for another month. ``` **poem test:** ```text Write a poem about Barcelona. ``` ## Codex route ### 1. Open a separate local practice folder 1. Open the desktop app you use for **Codex** and sign in. In builds that label the desktop app ChatGPT, choose its **Codex** view. This route uses a local folder, not a cloud task or an ordinary ChatGPT conversation. 2. On your Desktop or in Documents, create an empty folder called **Skills Workshop**. Do not use a work repository or the club website folder. 3. Copy the four kit downloads into that folder: `exec-summary.zip`, `star-feedback.zip`, `test-inputs.md` and `scorecard.md`. Keep both ZIPs uninstalled for the baseline. 4. In Codex, use its open-folder or project picker to select **Skills Workshop**. The exact picker label varies by app build. Confirm the folder shown for your chat is this local folder. 5. Start a **New chat** in that folder. Paste the availability-check prompt below, then send it. This checks for a pre-existing workshop skill without opening its full instructions. 6. If exec-summary or star-feedback is already installed globally or through a plugin, stop and ask a helper to disable that copy before the baseline. A new empty folder does not hide user-wide skills. Restart after changing skill settings. **Checkpoint:** The chat uses your separate Skills Workshop folder, and no active workshop skill is available yet. If the app cannot open local folders, use the optional CLI route at the end or pair with someone whose app can. **availability check:** ```text For this practice folder, list the names and paths of any available skills named exec-summary or star-feedback. Do not read their full instructions or summarize any workshop files. If either is already installed, tell me its location before we run the baseline. Do not change anything. ``` ### 2. Run the baseline before installing 1. Start a **New chat** in the same practice folder. Keep the model and reasoning setting visible in the composer unchanged for all comparison runs; note them down. 2. Copy the Pedala prompt below. Paste it into the empty composer with **⌘V** on Mac or **Ctrl+V** on Windows. 3. Check that it contains the whole call note and no `$exec-summary` mention. Send the message. 4. Wait for the final answer. Save it in a note called **Codex — Without skill**. 5. Complete the **Without** column of the Codex scorecard below. Do not compare its score with Claude’s score as a test of the skill; compare within Codex. **Checkpoint:** Your baseline answer and score exist before the skill is installed. **Pedala prompt:** ```text Summarise these notes for my manager: Call notes– Pedala (e-bike subscriptions, Barcelona) – Tuesday - attendees: Marta (CEO), Jordi (ops), us - ~1,200 active subscribers; monthly churn up from 4% to 7% since June!! - Jordi thinks it's repair wait times: avg 6 days now vs 2 days in spring. Their mechanic left in May - Marta more worried about new competitor BiciYa, launched at €29/month vs Pedala €39/month - exit survey: 140 responses, 58% of churned users mention repairs, 22% mention price - runway ~9 months - options discussed: hire 2 mechanics (~€6k/month total), cut price to €32, or partner with a repair shop in Gràcia (no quote yet) - Marta wants a decision before the board meeting on 15 Nov - we owe them a recommendation by next Friday - someone mentioned Valencia expansion but parked (Pedala and BiciYa are fictional companies made up for this exercise.) ``` ### 3. Ask Codex to install the local skill 1. Start a separate **New chat** in Skills Workshop for setup. Copy the install prompt below and send it. 2. Read any requested action before approving it. The intended changes are a local Git initialization if needed and the practice folder’s `.agents/skills` files. No remote, account connection or global installation is required. 3. Wait for the folder tree. Check for exactly `.agents/skills/exec-summary/SKILL.md`, with no extra nested exec-summary folder. A dot at the start of `.agents` makes it hidden in many file browsers. 4. Open the shown SKILL.md file or its diff to confirm it contains the original **120-word** limit. Do not change it yet. 5. Start a fresh Codex chat in the same folder. If skill discovery has not updated, fully quit and reopen the app, then reopen Skills Workshop and start a new chat. **Checkpoint:** The skill exists in the project’s discovery folder. The setup conversation is not used for the measured summary run. **local-install prompt:** ```text In this practice folder only, install the workshop executive-summary skill. 1. Confirm this is the Skills Workshop folder I selected. If it is not, stop and tell me. 2. If it is not already a Git repository, initialize it with git init. Do not create a commit or remote. 3. Extract exec-summary.zip. Copy the included exec-summary folder into .agents/skills/ so the final file is .agents/skills/exec-summary/SKILL.md. Do not create a second nested exec-summary folder. 4. If that destination already exists, stop and tell me rather than overwriting it. 5. Show the final folder tree. Do not write a summary, change other settings, or install the skill globally. ``` ### 4. Repeat the identical summary task 1. In the fresh chat, select the same model and reasoning setting as your baseline. 2. Paste the exact same Pedala prompt below, without adding a skill mention. Send it. 3. Look in the visible activity for a read of `.agents/skills/exec-summary/SKILL.md`. Record activation as unknown if the UI does not expose enough evidence. 4. Save the final answer as **Codex — With skill**. Complete the **With** scorecard column. 5. If it did not activate, keep that result. In a separate fresh chat, try an explicit request beginning `$exec-summary` followed by the same Pedala prompt. In the Codex CLI or IDE, `/skills` or typing `$` also exposes the skill selector. This forced run is troubleshooting, not the identical-prompt comparison. **Checkpoint:** You have the two main answers and scores. Any explicitly forced run is saved separately. **the same Pedala prompt:** ```text Summarise these notes for my manager: Call notes– Pedala (e-bike subscriptions, Barcelona) – Tuesday - attendees: Marta (CEO), Jordi (ops), us - ~1,200 active subscribers; monthly churn up from 4% to 7% since June!! - Jordi thinks it's repair wait times: avg 6 days now vs 2 days in spring. Their mechanic left in May - Marta more worried about new competitor BiciYa, launched at €29/month vs Pedala €39/month - exit survey: 140 responses, 58% of churned users mention repairs, 22% mention price - runway ~9 months - options discussed: hire 2 mechanics (~€6k/month total), cut price to €32, or partner with a repair shop in Gràcia (no quote yet) - Marta wants a decision before the board meeting on 15 Nov - we owe them a recommendation by next Friday - someone mentioned Valencia expansion but parked (Pedala and BiciYa are fictional companies made up for this exercise.) ``` ### 5. Change the instruction in the installed file 1. Open a separate **New chat** in Skills Workshop for editing. 2. Copy the edit prompt below and send it. Codex will edit the installed local file; no ZIP upload is needed. 3. Open the changed file or the diff shown by Codex. Confirm the only instruction change is **120 → 60** in the word-limit line. The name and description should be unchanged. 4. Confirm the edited file is `.agents/skills/exec-summary/SKILL.md`. Editing a loose extracted copy elsewhere would not update the installed skill. 5. Start another fresh chat for testing. If the old rule still appears to be loaded, fully quit and reopen Codex before testing again. **Checkpoint:** The discovered skill file contains the 60-word rule. You checked the edit before running the task. **edit prompt:** ```text Open .agents/skills/exec-summary/SKILL.md in this practice folder. Replace only the line "- 120 words maximum in total. Count before you answer." with "- 60 words maximum in total. Count before you answer." Leave the name, description and all other instructions unchanged. Show me the before-and-after line and a diff. Do not generate a summary yet. ``` ### 6. Run the task again and check 60 words 1. In the fresh chat, keep the same model and reasoning setting. 2. Copy and send the same Pedala prompt again. Save the answer as **Codex — Edited skill**. 3. Count all words, including labels. Use a word-count tool or the count-only prompt below as a quick check; verify any model-provided count. 4. Compare this answer with the original with-skill answer. Record whether it meets **60 words** and what changed. **Checkpoint:** You have a third answer tied to a reviewed one-line edit, rather than a follow-up request that merely asked for a shorter summary. **Pedala prompt:** ```text Summarise these notes for my manager: Call notes– Pedala (e-bike subscriptions, Barcelona) – Tuesday - attendees: Marta (CEO), Jordi (ops), us - ~1,200 active subscribers; monthly churn up from 4% to 7% since June!! - Jordi thinks it's repair wait times: avg 6 days now vs 2 days in spring. Their mechanic left in May - Marta more worried about new competitor BiciYa, launched at €29/month vs Pedala €39/month - exit survey: 140 responses, 58% of churned users mention repairs, 22% mention price - runway ~9 months - options discussed: hire 2 mechanics (~€6k/month total), cut price to €32, or partner with a repair shop in Gràcia (no quote yet) - Marta wants a decision before the board meeting on 15 Nov - we owe them a recommendation by next Friday - someone mentioned Valencia expansion but parked (Pedala and BiciYa are fictional companies made up for this exercise.) ``` **word-count check:** ```text Count the words in the assistant's summary immediately above, including its labels. Report the count only. Do not rewrite the summary. ``` ### 7. Test automatic activation 1. Leave the edited exec-summary installed. Start a **New chat** in Skills Workshop, copy the Peru prompt, and send. Prediction: **No**. 2. Start another **New chat** in the same folder. Copy the article prompt including the article, then send. Prediction: **Yes**. 3. Start a third **New chat** in the same folder. Copy the poem prompt and send. Prediction: **No**. 4. For each run, inspect the visible activity if available and record **Yes**, **No** or **Unknown**. Do not add `$exec-summary` to these prompts: that would force selection. **Checkpoint:** Three fresh chats test the description’s boundaries. A matching-looking output alone does not prove that a file was read. **Peru test:** ```text What's the capital of Peru? ``` **article test:** ```text Can you condense this article into something my boss can read in 30 seconds? Campus bike repair pilot The student services team tested a bike repair desk for 4 weeks. It served 80 students, and 60 booked a second visit. Average turnaround was 2 days, compared with 5 days at the previous provider. The pilot cost €1,600. The team has a €2,000 budget for next month. It has not yet checked whether the provider can handle twice as many bookings. Ana will collect a capacity quote by Friday. The committee must decide on Monday whether to extend the pilot for another month. ``` **poem test:** ```text Write a poem about Barcelona. ``` ## Scorecard One point for each yes. Use separate tables if you complete both apps. | Check | Without | With | | --- | --- | --- | | Opens with a recommendation, not the topic | | | | Exactly 3 reasons; each has a number from the notes | | | | 120 words or fewer, including labels | | | | No invented numbers; every number traces to the notes | | | | Ends with who does what by when (TBD is allowed for missing details) | | | | Total / 5 | | | ## Trigger observations | Prompt | Expected | Observed: Yes / No / Unknown | | --- | --- | --- | | Peru | No | | | Article | Yes | | | Poem | No | | What changed after the 60-word edit? __________ ## Optional · try the STAR demo yourself Do this after the core exercise, or follow the facilitator’s demo. Keep the two workshop skills from competing. ### Claude - In Customize → Skills, turn exec-summary off. - Upload star-feedback.zip using the same upload steps, and enable it. - Open a new chat, paste the interview prompt below and send. ### Codex - In a setup chat in Skills Workshop, send the STAR-install prompt below. Review the moved and installed folders. - Open a fresh chat in that same folder; restart the app if discovery has not updated. - Paste the interview prompt and send. If needed, try an explicit $star-feedback request in a separate chat.Copy STAR installation prompt Read STAR installation prompt ```text In this practice folder only, move .agents/skills/exec-summary to parked-skills/exec-summary so it is outside the discovered skills directory. Keep that copy; do not delete it. Extract star-feedback.zip and install its star-feedback folder at .agents/skills/star-feedback. Keep references/rubric.md inside that folder. Stop if a destination already exists. Show the resulting tree. Do not score an interview answer yet. ``` Copy interview prompt Read the interview prompt ```text Tell me about a time you led a team. Here's my answer: In my previous job at a consulting firm we had a project that was delayed. The client was unhappy and the team was stressed. We decided to have daily stand-ups and I talked to the client a lot. In the end the project was delivered and the client was happy. I learned that communication is really important. ``` **Checkpoint** Look for reads of SKILL.md and references/rubric.md when visible, four scores from 1–4, and a rewritten answer that uses placeholders instead of inventing achievements. ## If something does not match Claude: I cannot find Skills or upload a ZIP Check code execution under Settings → Capabilities, then go to Customize → Skills. Refresh the page after enabling it. If an organization manages the account, its owner may need to allow code execution and skills. Ask a helper or pair up if blocked. Do not buy a plan just to follow this guide; Free accounts are supported. Claude: my edited skill still gives 120 words Reopen the file inside exec-summary-60.zip and check it contains 60. Confirm you uploaded that ZIP, removed the original workshop entry and enabled the new one. Run in a new chat. If it still fails, record a failed test; do not assume a correct upload guarantees compliance. ZIP: I see two exec-summary folders Find the inner folder that directly contains SKILL.md. That is the folder to compress or install. The final Claude ZIP path is exec-summary/SKILL.md; the final Codex path is .agents/skills/exec-summary/SKILL.md. Codex: I cannot see .agents in Finder or File Explorer Mac: press ⌘Shift. (Command, Shift, period) to show hidden items. Windows: File Explorer → View → Show → Hidden items. Or open the file link Codex gives you. The dot folder is normal. Codex: the local skill is missing or two copies appear Confirm the chat is in Skills Workshop and the file is at .agents/skills/exec-summary/SKILL.md. Restart Codex if needed. User-wide or plugin copies can coexist with the local skill; ask a helper to disable the other workshop copy. Do not delete unrelated skills or replace your entire config file. Codex: Git initialization is blocked The project-local route uses a practice Git repository so discovery has a clear root. If the app reports Git is unavailable, ask a helper to install/enable Git or use the Claude route. Do not change to your work repository to get past this step. I cannot tell whether the skill was used Record Unknown. Visible style and the model saying “I used it” are weaker evidence than a file-read trace. For troubleshooting, explicitly request the named skill in a separate fresh chat; keep that result separate from the automatic trigger tests. The without-skill answer scores just as well Keep the result. The model can already produce good summaries. Compare whether the requested format is consistent and then test the edited 60-word rule. A tie is useful evidence, not a reason to alter the baseline after seeing the answer. The Copy button does not work Open the matching “Read the exact…” panel. Select the text inside the prompt box, copy with ⌘C or Ctrl+C, then paste into your app. This also works when the browser restricts clipboard access on local files. Optional: I already use Codex CLI Use the same local folder and prompts. Open Terminal or PowerShell, type `cd ` (including the space), drag the Skills Workshop folder into the window, then press Enter. Type `codex` and press Enter. Sign in if asked. Use `/new` for each fresh conversation; if your version does not offer it, exit and relaunch `codex` in the same folder. Use `/skills` to inspect the selector or `$exec-summary` for a separate forced test. This optional route assumes the CLI is already installed; it is not required for the workshop. ## Sources and scope Product steps checked 15 October 2026. Exact interface labels can vary by version. The exercise design and prompts are workshop material; product installation and loading behavior are grounded in the sources below. - [Claude: enabling, uploading and managing skills](https://support.claude.com/en/articles/12512180-use-skills-in-claude) - [OpenAI: local skill paths, discovery, invocation and updates](https://learn.chatgpt.com/docs/build-skills) - [OpenAI: desktop app, local folders and Codex chats](https://learn.chatgpt.com/docs/app) Only complete one route in class. The separate setup and edit conversations prevent instructions from those conversations becoming part of the measured summary chat. Fresh chats still share account-level preferences and installed skills; this is a practical classroom comparison.