This is the official tutorial for Skode Skript, release 0.2.0 — the English-like automation language of the Skode platform. It is written in the tradition of the great language tutorials: informal, complete, and built on examples you can run.
Every example is real. This book is compiled by a build system that extracts each program from the manuscript and executes it against the actual Skript interpreter; the output printed beneath an example is the output it produced during that build, byte for byte (with two cosmetic courtesies: run timings are normalised, and a few symbols the print fonts lack are substituted). Error examples work the same way — each was genuinely rejected by the interpreter, and the message shown is its real reply. If an example had failed, this PDF would not have compiled. More than sixty verified executions stand behind these pages.
Whom it is for. Readers with no programming background can start at Chapter 1 and read straight through; the language was designed for you, and the book assumes nothing. Experienced programmers may prefer to skim Chapters 3–10 and lean on Appendix D, the Python/JavaScript translation table — the interesting parts for you are what the language refuses to have, and why.
How to read it. With a terminal open. Installation is one command (Chapter 2), each example is a file away from running, and the interpreter's traces are half the teaching. The book is short because the language is small: Chapters 1–12 are the whole language, 13–16 are craft (errors, testing, packaging, production), and the appendices are the reference you will come back to.
Conventions. Programs appear in dark boxes; their real output in light boxes beneath. Inline code marks anything you would type. Command lines beginning with $ are typed at a shell. The names Maya, Sam and Ada stand for your teammates and customers, and bear no relation to persons living, dead, or fictional — except Ada, obviously.
The language, the CLI, this book's build system, and the book itself live at developer.skode.ai/skript. Corrections and questions are welcome on the community hub; the examples being executable means your bug report is reproducible by definition.
Now, to the appetite.