You have read the whole language — this is not a figure of speech; Skript is small enough that a tutorial can genuinely be complete — and you have seen it tested, packaged, and deployed. Where to from here depends on which itch brought you.
If you want to build something today: run skript new, replace the starter with the automation your team keeps doing by hand, and walk it through the Chapter 16 ritual. The first real skript teaches more than the second reading of any book.
If you want worked material: Appendix B is a cookbook of complete programs — triage, drip sequences, escalation, receipts, win announcements — each one runnable as printed, each one adaptable by changing the quoted strings. Steal freely; that is what it is for.
If you want the terse version of the language: Appendix A is the reference — the grammar in EBNF and every event, action, condition and limit in tables. It says nothing this tutorial has not said, but it says it in two pages, which is what you will want six weeks from now.
If you want the ecosystem: the developer hub at developer.skode.ai is the front door — the interactive Skript page, the playground, the marketplace, SDKs for when a problem outgrows sentences, and the community Q&A where the person who hit your exact question yesterday posted the answer. For anything else, skode.ai/support reaches humans.
If something in this book was wrong: then a promise failed, because every example was executed against the interpreter during the build, and every output printed is the output produced. Report it on the community hub — a tutorial with executable examples is a tutorial whose bugs are reproducible.
The language will grow — carefully, and sentence-shaped, or not at all. What will not change is the bargain from Chapter 1: what you can say, you can automate, and what you automated, anyone can read. Go say something useful.