create_guide
ChatGPTStart generating a narrated Scrimba guide from your briefing and get back a URL for the user. Use this whenever the user wants — or would clearly benefit from — a guide that walks through, explains, tours, or breaks down something: code, a diff, a file, an architecture, a concept, a bug, anything. Scrimba authors a spoken, narrated guide and returns a URL where it builds live. You are the Teacher briefing a Teaching Assistant. The TA wraps and narrates the material with its own teaching judgment and may add context, but it only knows what you give it and will not fetch anything afterwards — there is no follow-up data exchange. So the briefing must be complete and directive: - Include ALL material the guide needs, inline (code, diffs, file contents, errors, data — the prompt is markdown). - State exactly what must be taught: what to explain, what to focus on, which connections to make ("make sure they understand X causes Y"), what misconceptions to head off. - Describe the structure you want, and what the learner already knows, so the TA pitches it right. Everything you direct will be covered; anything you omit will be missing from the guide. All of the above is internal guidance for composing the call — don't narrate it to the user (no explaining briefings, TAs, or why you're including material). Just tell them you're creating their Scrimba guide. IMPORTANT: As soon as this returns, give the user the URL. They must be signed in to Scrimba when opening it — the first signed-in user to open the link becomes the owner.
create_guide
ChatGPTStart generating a narrated Scrimba guide from your briefing and get back a URL for the user. Use this whenever the user wants — or would clearly benefit from — a guide that walks through, explains, tours, or breaks down something: code, a diff, a file, an architecture, a concept, a bug, anything. Scrimba authors a spoken, narrated guide and returns a URL where it builds live. You are the Teacher briefing a Teaching Assistant. The TA wraps and narrates the material with its own teaching judgment and may add context, but it only knows what you give it and will not fetch anything afterwards — there is no follow-up data exchange. So the briefing must be complete and directive: - Include ALL material the guide needs, inline (code, diffs, file contents, errors, data — the prompt is markdown). - State exactly what must be taught: what to explain, what to focus on, which connections to make ("make sure they understand X causes Y"), what misconceptions to head off. - Describe the structure you want, and what the learner already knows, so the TA pitches it right. Everything you direct will be covered; anything you omit will be missing from the guide. All of the above is internal guidance for composing the call — don't narrate it to the user (no explaining briefings, TAs, or why you're including material). Just tell them you're creating their Scrimba guide. IMPORTANT: As soon as this returns, give the user the URL. They must be signed in to Scrimba when opening it — the first signed-in user to open the link becomes the owner.
finish_guide_stream
ChatGPTFinalize an open guide stream. Call this when you are done pushing — the guide stops showing as generating and narration becomes playable for viewers.
finish_guide_stream
ChatGPTFinalize an open guide stream. Call this when you are done pushing — the guide stops showing as generating and narration becomes playable for viewers.
push_guide_chunk
ChatGPTAppend a chunk of OPML to an open guide stream. Chunks accumulate into one growing document — never resend earlier content. Viewers see it render live. Returns remaining budget.
push_guide_chunk
ChatGPTAppend a chunk of OPML to an open guide stream. Chunks accumulate into one growing document — never resend earlier content. Viewers see it render live. Returns remaining budget.
start_guide_stream
ChatGPTOpen a guide stream where YOU author the content. Scrimba creates an empty guide, returns a link plus the OPML contract, and renders whatever OPML you push — live, as you push it. Use this instead of create_guide when you want full control over the guide's content and structure (custom narration, mermaid diagrams, code walkthroughs composed by you). Returns: the guide url (anyone with the link can view), a claim_url (give this one to the user — opening it signed in makes them the owner), a stream_token for pushing, and the complete OPML authoring contract. Read the contract carefully before pushing.
start_guide_stream
ChatGPTOpen a guide stream where YOU author the content. Scrimba creates an empty guide, returns a link plus the OPML contract, and renders whatever OPML you push — live, as you push it. Use this instead of create_guide when you want full control over the guide's content and structure (custom narration, mermaid diagrams, code walkthroughs composed by you). Returns: the guide url (anyone with the link can view), a claim_url (give this one to the user — opening it signed in makes them the owner), a stream_token for pushing, and the complete OPML authoring contract. Read the contract carefully before pushing.
