h5p-author: a type's fields without npm, and one link in the hand-over
Closes #192.
This PR changes two things in the h5p-author skill's text (skills/h5p-author/SKILL.md) and updates the matching rules in design/author.md. No code changes, and the build is unchanged.
What changes
- A type with no type file, where npm cannot install. Step 1 now says to fetch the build tool and the type's bundle, as step 3 does, and run
node h5p-author.mjs schema <Type> --libraries parts. - One web address in the hand-over:
- Step 3's two commands print the build page's link alone. For a source that names files, they print
No link: the source names files, which a link cannot carry.instead of the feedback line. - Step 5 hands over the package, its source file and that link, and gives no other web address.
- Step 5 no longer hands over the feedback line, the
libraries.txtlink, the tools to go to next, orreport.jsonand its revision. The licences stay as a sentence and the screenshot stays. - The preview command goes over only where there is no link.
- Step 3's two commands print the build page's link alone. For a source that names files, they print
- Where nothing is built here (cubic's review): step 5 now opens by sending the hand-over to step 3's build page route: the link, or the whole source and the page's address. Step 3's paragraph for that case names the address and holds only where nothing is built here. Before this, step 5's "Give no other web address" and "the preview command where there is no link" contradicted step 3.
- design/author.md:
- The schema bullet records the measurement.
- The hand-over rule becomes The hand-over carries the source and one web address, the build page's link, and records the build page route's case.
Tested
All runs used Haiku as a subagent, the weakest model first.
Schema: the skill read by its link, with no package registry. Crossword and Find the Words, two runs each per text.
| Old text | New text | |
|---|---|---|
Fields at the first schema call | 0 of 4 | 4 of 4 |
| Built a package | 3 of 4 | 4 of 4, all at the first try |
All 7 packages pass h5p-verify.
Hand-over: the skill installed, with a shell and npm, the verifier left out. Same prompts as 0.9.5's measurement.
| 0.9.5's text | New text | |
|---|---|---|
| Three-question Question Set: web addresses in the reply | 2 or 3 (2 runs) | 1 (3 runs) |
| Multiple Choice with the user's picture: web addresses | 1 or 2 (3 runs) | none (2 runs) |
| Question Set reply length | 3,146 and 3,724 characters | 2,250 to 2,737 characters |
- In every Question Set run with the new text, the one address was the build page's link and decoded to the source exactly.
- Every picture run with the new text handed over the preview command instead.
- Every run handed over the source file.
Commands: both one-liners run as written. A plain source gives one line: a link that decodes to the source byte for byte. A source that names a file gives the reason alone.
The build page's route (after cubic's review): Haiku as a chat with no tools, the skill's text and the type's file pasted in. Five chats per text: three Question Sets, and two Multiple Choice questions naming the user's picture.
| This PR's first text | With the fix | |
|---|---|---|
Whole source in one json block beside the page's address, no link | 5 of 5 | 5 of 5 |
| A preview command | 0 of 5 | 0 of 5 |
| The picture named, to choose on the page | 2 of 2 | 2 of 2 |
- Haiku already did this right before the fix. The fix is for a model that reads step 5's list to the letter.
- With a shell and npm, the fix changed nothing: 2 of 2 Question Sets handed over the exact link alone, and the picture run gave no address and the preview command.
What is lost and not covered
- None of the 5 new replies told the user to say how it went at the foot of the build page, although step 5 asks the chat to write it. Feedback on a package built in a chat now depends on its user scrolling down the build page.
- The h5p-verify skill, where installed, still asks the chat to give the
revision. - The build page has to keep
id="feedback-heading", because installed copies of 0.9.5 print its address.
Release
This is a patch, h5p-author 0.9.6, skill text only. After it: the org site's pin bump, npx skills update -g, and a new Claude app zip.
Summary by cubic
Updates the h5p-author skill's text so two gaps are closed: a type's fields are fetched without npm, and the hand-over carries one web address, the build page's link. No code changes; the design rules in design/author.md are updated to match.
A type's fields where npm cannot install
- Step 1 now says to fetch the build tool and the type's bundle, as step 3 does, and run
node h5p-author.mjs schema <Type> --libraries parts. - Given only the npx form with no registry, Haiku ran without
--librariesin 4 of 4 runs; with the command, 4 of 4 got the fields and built a packageh5p-verifypassed.
One web address in the hand-over
- Step 3's two commands print the build page's link alone, and
No link: the source names files, which a link cannot carry.for a source that names files. - Step 5 hands over the package, the source file and that link; the feedback line, the
libraries.txtlink, the preview command, the next-step tools, andreport.jsonwith its revision are gone. Licences stay a sentence, the screenshot stays, and the preview command is given only where there is no link. - Where nothing is built in the chat, step 3's build page route is the whole hand-over: the link, or the whole source with the page's address, and never the preview command.
- Question Set replies carried the link as their sole address in 3 of 3 runs, against 2 or 3 before; picture sources got no address and the preview command instead.