nudge
Skill2 starsChanged 56 days agoMITView on GitHub
Concierge — keeps conversations moving by alternating a public touch (a comment on their latest post) with a private one (a DM that brings something new), follows up on the dates people gave, and unblocks stuck Pastel sequence runs. Use for "follow up", silence after connecting, curious / timing / pushback conversations, or runs needing attention.
In this repository20 other files it gives its agents.
- AGENTS.mdAGENTS.md
- buying-committeeSkill
- call-readySkill
- campaign-launchSkill
- command-centerSkill
- competitor-watchSkill
- fit-checkSkill
- human-voiceSkill
- intent-radarSkill
- market-mapSkill
- message-writerSkill
- morning-briefSkill
- outbound-briefSkill
- post-studioSkill
- priority-rankSkill
- reach-checkSkill
- reply-deskSkill
- social-warmupSkill
- what-worksSkill
- why-nowSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 31
Stuck runs: read the failing step in pastel_get_sequence_run and prepare resolve_sequence_step with resolve or resend.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Nudge — Concierge
House rules: ../command-center/shared/house-rules.md · Pastel tools: ../command-center/shared/pastel-tools.md
Each follow-up adds something to the conversation: a thought on their latest post, an example from a similar company, a number they'd find useful.
In scope
curious,timing, andpushbackconversations fromreply-desk.- Connected, opening message sent, no answer yet.
- Pastel runs with
status="needs_attention".
The rhythm: public, then private
| Touch | When | Where |
| 1 | — | The opening message (from campaign-launch) |
| 2 | 3 business days of silence | Public: a comment on their latest post through social-warmup, if they posted in the last two weeks. If not, a DM with something useful attached to the conversation. |
| 3 | 8 business days after touch 2 | Private: a short DM that leaves the door open, with a reason to come back to it later. |
That's the whole rhythm. timing conversations skip it: one message, on the date they gave.
Steps
- Gather the conversations and runs in scope.
- Stuck runs: read the failing step in
pastel_get_sequence_runand prepareresolve_sequence_stepwithresolveorresend.confirmed_resendonly if the user accepts a possible duplicate. - Write the touch, then
human-voice. - Prepare
send_chat_messageon thechat_id, or the comment throughsocial-warmup, for approval.
Output
Same layout as message-writer, plus chat_id, touch number, channel, and the not before date.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.