Skip to content

The guide goes by what a chat has, not by its name - #81

Merged
alekswebnet merged 5 commits into
mainfrom
docs/guide-by-capability
Nov 20, 2026
Merged

alekswebnet merged 5 commits into
mainfrom
docs/guide-by-capability

Conversation

@alekswebnet

@alekswebnet alekswebnet commented Nov 20, 2026 •

Copy link
Copy Markdown
Contributor

Closes #80.

The how-to and the build page gave their steps by product: where the skill goes in Claude, ChatGPT and Grok, which of them builds the file, and what each lacks. Chats change within weeks, as Grok's place for skills did between 2026-11-13 and 2026-11-15, and each change left a step sending its reader the wrong way. The pages now go by what a chat has, which a reader can see in their own chat.

What changes

  • The guide, step 1 (the skill): three cases in place of three products, with "take the first of these that fits". An agent with a terminal comes before them, with its one command, since it has no settings to look in.
    • A place for skills takes h5p-author.zip, once. A switch for running code, if there is one, goes on.
    • Plugins and no skills take h5p-author-chatgpt.zip, the same skill laid out as a plugin. The case says that plugins come in more than one layout, and that a chat which refuses this one takes the zip attached.
    • Neither, or a refused upload: the zip goes with the message, in each new chat.
  • The guide, step 4 (the file): the chat hands over the .h5p where its code runs Node.js and gets the build tool, and the source otherwise. The build archive moves here from step 1, with its own #archive anchor. Nobody knows beforehand whether a chat's code can download the tool, and the skill's reply offers the archive where it would help. It goes into a project where the chat has projects, and with the message where it has none or the chat does not find it there.
  • The guide's other sections:
    • The lead says the same in one sentence.
    • With a local model names no app: where an app runs no code, or its code is not Node.js, the chat hands over the source.
    • The help entries say "attached to your message" and "if your chat has projects".
    • The chat's link builds nothing said a link is made by running code. The skill gives the build page's plain address and no link, so the entry now says that.
  • The build page: "Works with your AI chat", the line under "How it works" and its first and third steps say what a chat can do. The third step links to #archive.
  • The skill page and the README describe the two zips by what takes them, "installed once" against "attached to the message in each new chat". The README records the rule and keeps what was seen in each chat, with its date.

What stays

  • The titles, descriptions and the guide's heading still say "ChatGPT, Claude or Grok". They are examples of an AI chat and what people search for, and say nothing of any one of them.
  • Names that are not claims about a chat: the plugin zip's file name, "Claude Haiku made the sample", and "from Ollama or LM Studio".
  • The comments in vite.config.ts, which are dated records of what was tried.

Tested

  • Build: pnpm install --frozen-lockfile and pnpm build, which runs tsc, pass.
  • Links: every link and anchor of the two built pages resolves, the new #archive among them.
  • Layout: the changed sections were looked at in Chromium at 1280 px and 390 px. Neither page scrolls sideways.
  • Text: in the two built pages no sentence is left that says what a named chat does or lacks.
  • Not tested: a project of a chat other than ChatGPT. The step says what to do where the chat does not find the archive there.

Summary by cubic

The guide and build page now describe steps by what a chat has — a place for skills, plugins, projects, or code that runs — rather than by naming Claude, ChatGPT, or Grok.

  • Chats change what they offer within weeks, so product-named steps can send readers the wrong way.
  • Step 1 leads with the terminal agent's one command, described by what it does with no product named, since it has no settings to look in; the step says the command needs Node.js and falls back to a zip when it does not list the agent. Then goes by what a chat has: the plugin zip is one layout of several, and a chat that refuses it takes the zip attached.
  • The build archive instructions move from step 1 to step 4, with its own #archive anchor; help entries, the README, and the skill page describe the two zips by what takes them.
  • The README records what was seen in each chat as a dated observation, not a standing condition.

Written for commit 62966e9. Summary will update on new commits.

View guided diff Turn on auto-fix

The how-to and the build page gave their steps by product: where the
skill goes in Claude, ChatGPT and Grok, which of them builds the file,
and what each lacks. Grok imported the zip under Skills on 2026-11-13
and had no place for one two days later, so such a step sends its
reader the wrong way until it is edited again.

Each step now names what a reader can look for in their own chat and
says what to do with it and without it: a place for skills, plugins, or
neither for the skill; code that runs Node.js and gets the build tool,
or the source for the build page; and for the build archive a project,
or the message. No page says what one product does or lacks. The chats
in the titles stay as examples, and what was seen in each chat stays in
the comments and the README with its date.

The help entry on a chat's link said a link is made by running code:
the skill gives the build page's plain address and no link (h5p-toolkit#215).

Closes #80.
@alekswebnet
alekswebnet force-pushed the docs/guide-by-capability branch from 216facc to d5bcecc Compare November 20, 2026 07:42

@cubic-dev-ai cubic-dev-ai Bot left a comment •

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Review completed against the latest diff

Reply with feedback, questions, or to request a fix.

View guided diff | Turn on auto-fix | Re-trigger cubic

Comment thread README.md Resolved
Comment thread src/h5p/create-with-ai/index.njk Resolved
Comment thread src/h5p/create-with-ai/index.njk Resolved
Comment thread src/h5p/skill/index.njk Resolved
…as one layout

From the review of #81:
- an agent with a terminal comes before the cases and outside them: taken
  in order, the cases sent it to the zip attached to each message before
  it reached `npx skills add`;
- the plugin case says plugins come in more than one layout, and that a
  chat which refuses this one takes the zip attached;
- the skill page and the README say "installed once" against "attached
  to the message in each new chat".

@cubic-dev-ai cubic-dev-ai Bot left a comment •

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

All reported issues were addressed across 3 files (changes from recent commits).

Reply with feedback, questions, or to request a fix.

View guided diff | Turn on auto-fix | Re-trigger cubic

Comment thread src/h5p/create-with-ai/index.njk Resolved
Comment thread README.md Resolved

@cubic-dev-ai cubic-dev-ai Bot left a comment •

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

All reported issues were addressed across 2 files (changes from recent commits).

Reply with feedback, questions, or to request a fix.

View guided diff | Turn on auto-fix | Re-trigger cubic

Comment thread src/h5p/create-with-ai/index.njk Resolved
@alekswebnet
alekswebnet merged commit e5038bd into main Nov 20, 2026
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

The guide says what each chat does, and chats change within weeks

1 participant