Follow-up After Silence
Writes a sub-60-word nudge that adds one new thing and makes "no" an easy reply.
Sales · produces a Email · 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:
read_document
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.
Read the thread and count the unanswered messages to decide the stage: first nudge, second, or closing note. Open with one new thing they did not already have (an answer to a question they left hanging, a relevant example, a useful link), never with a reference to the silence. Make the ask smaller than the last one and end so that "no" or "not now" is a complete reply. Under 60 words; never "just following up", "bumping", "gentle reminder" or any apology for writing. Output the body only, then one line naming the stage and when to send it.
How to run it
| Where | How |
|---|---|
| Chat | "Run my Follow-up After Silence skill", or pick it from the + menu |
| Skills page | Find Follow-up After Silence 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.
Open App