What it writes
Two acts share one door. Saving writes the skill Ask Tightly drafted in a conversation as a Draft at Tells you, the shortest rope, with the worked examples and corrections from the conversation kept as its cases from the first day. A saved draft runs nothing: publishing it, and every rung above the first, is a person's press on the skill's own page. Firing runs a published skill once, by hand, from Ask Tightly. The run keeps every gate the skill carries, its rung, the fields it may change, its ceilings and its wait; firing routes work and never widens what the skill may do.
Who may press it
A read-write seat, for both. The person who confirms the save is the skill's creator, and every run of that skill executes as them, whoever fires it later. Firing takes the same permission as running the skill from the Skills page; a read-only seat is refused in words and nothing runs. Publishing and promotion are never acts of Ask Tightly: they are presses behind the Skills door, an admin or someone named on the Approvals page. On Tightly Lite neither act is offered, because skills are sold from Essentials up.
Over a connected client, a skill is drafted through the conversation and saved with Save as a draft skill once the person has confirmed it. Firing is refused there: a run executes as the skill's creator, so a relayed question cannot set one off, and the person runs it from the Skills page instead.
What you see
In a skill-writing conversation the draft rides every answer, so the sequence on Write a skill fills before anything is saved, with the badge Draft, not saved. The chip Save as a draft skill carries its confirm, naming the skill and its rung and saying it runs nothing until it is published:
Save "{name}" as a draft skill at Tells you; it runs nothing until it is published.
The receipt carries the skill's door and two dry runs. The back test says, for a skill fired by an event, how many of the matching events on the 90-day ledger it fired on and how many it missed; a skill that is not fired by an event is not back-tested, and the receipt says why. The cases result says how many of its cases passed on the saved version. Firing answers with the run: the skill's name and the run's key, and the run's page is where its steps and changes are read.
What to do
A saved draft has nothing to undo, because it ran nothing; the receipt offers the door. Publish it from the skill's page when it reads right, and it starts at Tells you. A fired run's way back is Undo everything on the run's page, which puts every reversible change back in one press; a change with no before-value cannot go back, and the refusal names which.
Refusals you may read
No such skill in this organization.
A skill that is not published cannot be fired; the sentence names the skill and says only live skills can be fired. A read-only seat is told that firing a skill takes the same permission as running it from the Skills page, and that this seat is read-only. A run that could not be started:
The skill could not be started. Nothing ran.
A draft with a hole in it is refused at the save with the validation's own sentence, naming what is missing, and the conversation keeps going until it is whole.