Skip to main content
Summer’s skills, templates, references and the engine class reference. 5 operations. How to call them, and what the answers mean: Operations reference.
Generated from the operation catalog: src/lib/ops/public-catalog.json in publicsummerengine at 0d85f61e2b and the summer-engine npm package 4.0.0 for engine and local operations. If something here is wrong, the operation’s definition is wrong.

engine_api

docs.engine_api: Engine api Offline engine class-reference lookup — verify a property, method, signal, or constant before writing script code instead of guessing names. Inputs:
Example: Engine api

feedback

docs.feedback: Feedback Report how library entries worked out (worked, wrong, outdated, …) so Summer can fix and re-rank them; fire-and-forget, opt-out honored. Inputs:
Example: Feedback

plan

docs.plan: Plan Plan the right Summer workflow for a game-building task: skill routes, tool groups, confirmation gates, and verification steps. Inputs:
Example: Plan

read

docs.read: Read a Summer doc Read one Summer skill, Studio guide or docs page by its id from docs.search, as Markdown. Long texts are cut at maxCharacters and say so. Free. Inputs:
Example: The publishing guide, start to finish.

docs.search: Search Summer docs Search Summer’s own skills, Studio guides and docs pages by describing the task in plain words. Returns ids, titles and summaries. Free. Next: docs.read with an id. Inputs:
Example: Find the publishing guide.