You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
h5p-author skill: the owner's flow: type, then author and licence or a skip, then the source, then the best build for the situation #184
The owner's flow for the h5p-author skill, 2026-11-11:
agent ask to select content type -> user selects -> agent ask to fill author and license, user should fill or skip to default (known name or some default value) -> agent generate json -> agent propose the best variant to create H5P file using generated json (inside app like claude or link to build page etc it depends on situation)
How the skill's text differs today, on #183's branch:
Step 1 asks for the author with the type, "in the reply that proposes the type, or in one of its own", and a model that read "a quiz" took the type as named: on Haiku, four of six runs chose a Question Set themselves.
There is no skip: a user who gives no name is asked again, or the build is refused.
Step 3 tries npx first wherever it is, then the files, then the build page, and says nothing to the user about which.
So:
the order written out before step 1, one question at a time;
step 1: unless the user named a type from the table ("a quiz" names none), propose one or two and wait; once they have chosen, ask for the author's name and the licence in a message of its own, and say they may skip it;
a skip takes the name the model knows the user by, or "Unknown", and the licence U (undisclosed), in SKILL.md, the brief and every content type's file;
step 3 opens with the three ways to build and what each needs: here with npm, here from two files, or in the user's browser with no attempt here first; take the first that applies and tell the user which.
Activity
fix(author): the skill follows the owner's flow: type, then author an…