A skill is a procedure you write once in markdown and run by typing its name: /weekly-review, or /weekly-review focus on work to point it at something. Saturn follows its steps for that one request, with no extra model call. Every action a skill leads to still asks for approval as usual: a skill never changes what asks first. saturn -p "/weekly-review" runs one headless.
::where they live
~/.saturn/skills/<name>/SKILL.md or ~/.saturn/skills/<name>.md
<folder>/.saturn/skills/<name>/SKILL.md or <folder>/.saturn/skills/<name>.mdIt's the same file shape Claude Code uses, so skills you already have work. A working folder's own .saturn/skills wins over a global skill of the same name. The name is the file name (the folder's, for SKILL.md): lowercase letters, digits, and hyphens. A skill named like a built-in command (/help, /memory, …) never runs, and startup and /skills say so. Skills are read from disk each time, so an edit runs without a restart.
---
name: weekly-review
description: Friday review — what got done, what slipped, what is next
---
1. List this week's calendar events and the reminders completed or overdue.
2. Read my note titled "This week" if there is one.
3. Answer in three short lists: done, slipped, next week.The frontmatter takes name and a one-line description. Other keys (allowed-tools, model, …) are ignored, and /skills show names them. Saturn reads only SKILL.md and runs nothing else in the folder. A body past 6,000 characters is cut, with a note saying so.
::commands
/skills list your skills, where they live, and who wrote each
/skills show <name> print one
/skills create <name> write a template to ~/.saturn/skills/<name>/SKILL.md
/skills delete <name> move one to the Trash (asks first)
/<name> [request] run a skill
/<name> --help show it instead of running it::saturn can write one
Say "save that as a skill called weekly-review" and Saturn drafts it with create_skill. The prompt shows the complete skill, every step, and it's saved only on your yes. That prompt always appears, whatever /policy says: there's no always-allow for it, and saturn -p never saves a skill. A drafted skill goes in ~/.saturn/skills and is at most 3,000 characters, so you can read all of it before you approve. /skills shows which skills Saturn drafted, and /undo takes a save back.
note
Saturn's file tools never write the skills folders, even approved: a skill is followed as your own words. Skills run only when you type their name; Saturn doesn't pick one on its own. Drafting is reliable on the 9b and up; the 4b tends to carry the steps out instead of saving them.