delivery-queue
Skill191 starsChanged 5 months agoMITView on GitHub
Schedule and deliver messages in timed segments to simulate human-like sending patterns.
In this repository12 other files it gives its agents.
- AGENTS.mdAGENTS.md
- workspace/AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- .github/copilot-instructions.mdCopilot instructions
- b2b-sdr-agentSkill
- chroma-memorySkill
- graphifySkill
- lead-discoverySkill
- quotation-generatorSkill
- sdr-humanizerSkill
- supermemorySkill
- telegram-toolkitSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 9
Avoid WhatsApp spam detection by pacing outbound messages
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 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
delivery-queue — Delayed Segmented Delivery
Schedule and deliver messages in timed segments to simulate human-like sending patterns.
Use Cases
- Break long product introductions into 3-5 digestible messages
- Schedule follow-ups at optimal times (e.g., prospect's local 9 AM)
- Drip campaigns: space out nurture messages over days
- Avoid WhatsApp spam detection by pacing outbound messages
Commands
deliver:schedule— Queue a message for future deliverydeliver:list— View pending deliveriesdeliver:cancel— Cancel a scheduled deliverydeliver:flush— Send all pending messages immediately
Configuration
default_delay_ms: 3000 # Delay between segments
max_segments: 10 # Max segments per delivery
timezone: "{{timezone}}" # Owner's timezone
quiet_hours: # Don't send during these hours
start: "22:00"
end: "07:00"Usage Example
Schedule a 3-part product intro to +1234567890:
1. Company overview (send now)
2. Product highlights (send after 5 min)
3. Pricing inquiry (send after 15 min)How It Works
- AI composes the full message sequence
- Skill splits into segments with timing
- Each segment is queued with a delivery timestamp
- Background worker sends at scheduled times
- Failed deliveries retry up to 3 times
File Structure
delivery-queue/
├── SKILL.md # This file
└── deliver.sh # Queue management scriptDoes 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.

