The guide: ChatGPT builds from the archive kept in a Project

The guide told people using ChatGPT to attach h5p-author-build.tar.gz to the message where
they ask, in every chat. On the owner's free account the archive kept in a ChatGPT Project built
a Question Set in a chat of that project, on 2026-11-14. So the guide's install step, its step
on getting the file, its help entry and the build page's third step name the Project first, and
attaching the archive as the way outside one.

Closes #49.

Author: alekswebnet

README.md

@@ -14,7 +14,7 @@ The site of the [missing-elements](https://github.com/missing-elements) web comp
 | `/h5p/bundles/` | The skill's build tool and a library bundle per content type, for a chat that runs Node but cannot reach npm; and `h5p-author-build.tar.gz`, the tool and every library in one archive, for a person to attach to a chat whose code can download nothing | written by [vite.config.ts](vite.config.ts) |
 | `/h5p/build/types/` | The skill's type files, which the build page copies for the chat | written by [vite.config.ts](vite.config.ts) |
 
-A chat takes the skill installed: from a zip in Claude, ChatGPT and Grok, or with `npx skills add` in an agent with a terminal, as `/h5p/create-with-ai/` says. Where the skill cannot reach npm, it builds from the tool and a bundle in `/h5p/bundles/`, at the addresses `/h5p/skill/` lists, if it can run Node and fetch a file: Grok did, on 2026-11-13. Where its code runs Node but can fetch nothing, as in ChatGPT, it builds from `h5p-author-build.tar.gz` once the person attaches it, and otherwise gives them a link to `/h5p/build/`, which builds in their browser. The tool is a Node.js program, so a chat whose code runs no Node, as most chat apps for local models, takes the link; an agent with a terminal and a local model builds offline from the archive.
+A chat takes the skill installed: from a zip in Claude, ChatGPT and Grok, or with `npx skills add` in an agent with a terminal, as `/h5p/create-with-ai/` says. Where the skill cannot reach npm, it builds from the tool and a bundle in `/h5p/bundles/`, at the addresses `/h5p/skill/` lists, if it can run Node and fetch a file: Grok did, on 2026-11-13. Where its code runs Node but can fetch nothing, as in ChatGPT, it builds from `h5p-author-build.tar.gz` once the person attaches it or keeps it in a ChatGPT Project (the owner's free account, 2026-11-14), and otherwise gives them a link to `/h5p/build/`, which builds in their browser. The tool is a Node.js program, so a chat whose code runs no Node, as most chat apps for local models, takes the link; an agent with a terminal and a local model builds offline from the archive.
 
 Until 2026-11-13 the site's prompts sent a chat to read the skill at `/h5p/skill/` instead. That worked only in chats that now take the zip, so the prompts name the installed skill, and no page links to `/h5p/skill/`. Its page and files stay: the copies of the skill already installed name that address, and so do the prompts people copied before.
 

src/h5p/build/index.njk

@@ -141,7 +141,7 @@ csp: "default-src 'self'; script-src 'self'; style-src 'self'; img-src 'self' da
         </li>
         <li>
           <h3>Play it, then download it</h3>
-          <p>Claude and Grok build the <code>.h5p</code> file in the chat, and so does ChatGPT with <a href="/h5p/create-with-ai/#install">the build archive</a> attached. Without it, ChatGPT hands over a link that opens the activity here, or its source, to <a href="#build-it">open or paste below</a>.</p>
+          <p>Claude and Grok build the <code>.h5p</code> file in the chat, and so does ChatGPT with <a href="/h5p/create-with-ai/#install">the build archive</a>, kept in a Project or attached. Without it, ChatGPT hands over a link that opens the activity here, or its source, to <a href="#build-it">open or paste below</a>.</p>
         </li>
       </ol>
       <div class="prompt-box">

src/h5p/create-with-ai/index.njk

@@ -48,8 +48,9 @@ csp: "default-src 'self'; script-src 'self'; style-src 'self'; img-src 'self'; o
 
   {#- The steps are drawn as the skill page's timeline (site.css). The first is the install: the
       zips are written by vite.config.ts from the release the site pins, and each was uploaded as
-      it is, by the owner, on 2026-11-13, Claude's into Grok too. Its heading keeps the id that
-      the top bar and the skill's page link to. -#}
+      it is, by the owner, on 2026-11-13, Claude's into Grok too. The archive kept in a ChatGPT
+      Project built there on the owner's free account on 2026-11-14 (#49). Its heading keeps the
+      id that the top bar and the skill's page link to. -#}
   <section class="step" aria-labelledby="install">
     <h2 id="install"><span class="step-marker"><span class="step-number">1</span></span> Install the skill, once</h2>
     <p>
@@ -66,10 +67,12 @@ csp: "default-src 'self'; script-src 'self'; style-src 'self'; img-src 'self'; o
         <strong>ChatGPT</strong>: download
         <a href="/h5p/skill/h5p-author-chatgpt.zip" download>h5p-author-chatgpt.zip</a> and upload it
         under Plugins. ChatGPT's code cannot download the build tool, so download
-        <a href="/h5p/bundles/h5p-author-build.tar.gz" download>h5p-author-build.tar.gz</a> once too,
-        and attach it to the message where you ask: ChatGPT then builds the <code>.h5p</code> file in
-        the chat. Without it, ChatGPT hands over a link to the build page; if the page says the link
-        arrived damaged, ask for the source as a file and open that on the build page.
+        <a href="/h5p/bundles/h5p-author-build.tar.gz" download>h5p-author-build.tar.gz</a> once too.
+        Make a Project in ChatGPT, add the archive to it, and ask in a chat of that project:
+        ChatGPT then builds the <code>.h5p</code> file in the chat, with nothing to attach.
+        Outside a project, attach the archive to the message where you ask. Without it, ChatGPT
+        hands over a link to the build page; if the page says the link arrived damaged, ask for
+        the source as a file and open that on the build page.
       </li>
       <li>
         <strong>Grok</strong>: download
@@ -124,7 +127,7 @@ csp: "default-src 'self'; script-src 'self'; style-src 'self'; img-src 'self'; o
       runs Node.js:
     </p>
     <ul>
-      <li>the <code>.h5p</code> file itself, from a chat whose code runs Node.js and can reach the build tool, as Claude's and Grok's can, and ChatGPT's with the build archive attached;</li>
+      <li>the <code>.h5p</code> file itself, from a chat whose code runs Node.js and can reach the build tool, as Claude's and Grok's can, and ChatGPT's with the build archive, kept in a Project or attached;</li>
       <li>a link that opens the activity on the build page, as ChatGPT gives without it;</li>
       <li>or its source, as a file or a block of JSON: open or paste it <a href="/h5p/build/#build-it">on the build page</a> and choose Build.</li>
     </ul>
@@ -291,8 +294,9 @@ csp: "default-src 'self'; script-src 'self'; style-src 'self'; img-src 'self'; o
     <p>
       Download <a href="/h5p/bundles/h5p-author-build.tar.gz" download>h5p-author-build.tar.gz</a>
       and attach it to your next message: a chat whose code runs Node.js builds the file from it,
-      without installing or downloading anything. A chat whose code runs no Node.js gives you a
-      link to the build page instead.
+      without installing or downloading anything. In ChatGPT, keep the archive in a Project and
+      ask in a chat of it: there is then nothing to attach again. A chat whose code runs no
+      Node.js gives you a link to the build page instead.
     </p>
 
     <h3>The build lists problems</h3>