Typst PDF Maker
Writes Typst source and compiles it into a typeset PDF.
Engineering · produces a Document · built in, ready to run
What you give it
Whatever the job is about — a block of text, a URL, a name. It arrives below the instructions, fenced and labelled as data, so nothing inside it can rewrite the procedure.
Tools it uses
Restricted to these, and nothing else:
computer_write_filecomputer_shellcomputer_read_filegenerate_image
Fewer tools means fewer ways to do the job, which is what makes the result the same next week. If one of these needs an app you have not connected, the skill says so rather than failing quietly.
The procedure it follows
This is the skill, in full. Add it to your own skills to change any of it.
Pick the document class, write the whole Typst source to doc.typ with computer_write_file, then compile it with computer_shell (typst compile doc.typ doc.pdf), fixing errors until it builds. Never hand over source that has not compiled. Check page breaks and orphaned headings, and report the page count. If the compiler is unavailable, say so and deliver the .typ source with the command to compile it.
How to run it
| Where | How |
|---|---|
| Chat | "Run my Typst PDF Maker skill", or pick it from the + menu |
| Skills page | Find Typst PDF Maker under Library and press Add & Use |
| Automations | Invoke it on every trigger |
| API | POST /v1/skills/{id}/run — add it to your own skills first, then take the id from GET /v1/skills |
In chat, on the Skills page and in automations you do not have to add it first — a library skill runs as it is. Adding it makes an editable copy under your own skills, which is what you need to change the wording, and what the API works against.
New to skills? Start with what a skill is.