acp-connector
Skill136 starsChanged 3 days agoMITView on GitHub
Self-reminders and agent-managed cron via the acp-connector bridge MCP tools. Use when running behind acp-connector (Telegram/Discord bridge) and needing to schedule follow-ups, snooze checks, or create recurring jobs.
The file
We split this skill into the rules it gives an agent
6 rules. About 0 are common, 2 are distinctive, and 4 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 14
When running behind it, an agent-reminders MCP server is injected into your session with reminder_* and cron_* tools.
- Very specific: line 36
When [Reminder <id>] arrives: check for a reply.
- Very specific: line 38
No reply → reminder_create again with growing delay (15m → 30m → 1h → 3h).
- Distinctive: line 39
After ~24h of silence: stop rescheduling and notify the user through the normal channel instead of looping forever.
- Very specific: line 50
Use for periodic work (daily checks, polling loops).
- Distinctive: line 72
After manual config edits the bridge must be restarted.
≈ “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
ACP Connector
acp-connector is the thin bridge that connects you (an ACP agent) to the operator's messaging platforms (Telegram, Discord, HTTP, A2A peers). Every inbound message — user chats, cron fires, reminders — lands in one serialized prompt queue and reaches you as a plain prompt.
When running behind it, an agent-reminders MCP server is injected into your session with reminder_* and cron_* tools. If those tools aren't visible, the bridge or the agent harness doesn't support MCP servers — scheduling isn't available; tell the user.
reminder_* tools — one-shot self-reminders
| Tool | Purpose |
reminder_create({ prompt, in?, at? }) | Schedule a one-shot reminder. Exactly one of in/at |
reminder_list() | Pending reminders with id + firesAt (UTC) |
reminder_cancel({ id }) | Cancel |
reminder_update({ id, in?, at?, prompt? }) | Snooze/reschedule/reword |
in= delay from now:"10m","30m","2 hours","1 day".at= absolute time:"tomorrow 10am","mañana 10:00", or ISO ("2026-03-01T10:00"). Naive times parse in the operator's configuredtimezone(default: system TZ);firesAtis stored in UTC.- On fire you receive
[Reminder <id>] <prompt>as a new prompt — writepromptfully self-contained: who, what to check, what to do next. You won't see this conversation then. - Delivery is guaranteed-ish: if no session is active when it fires, the bridge keeps it and retries on reconnect. Max 50 active; entries 7+ days past
firesAtare dropped.
Follow-up loop pattern (WhatsApp / email / any outreach)
The canonical use: after sending a message that needs a reply, schedule a check — never fire-and-forget.
- Send the message (e.g. WhatsApp to a contact).
reminder_create({ prompt: "Check WhatsApp chat with <name>: did they reply to <topic>? If yes, <next step>. If not, resched with backoff.", in: "15m" }).- When
[Reminder <id>]arrives: check for a reply.- Replied → handle it, done. No new reminder.
- No reply →
reminder_createagain with growing delay (15m → 30m → 1h → 3h). Include elapsed time in the prompt.
- After ~24h of silence: stop rescheduling and notify the user through the normal channel instead of looping forever.
cron_* tools — recurring jobs you own
| Tool | Purpose |
cron_create({ every | expr, prompt }) | New recurring job. every: "30m", "1h", "1d", "1w" (even divisors only); expr: raw 5-field cron ("0 9 * * *") |
cron_list() | All jobs; yours are managed: "agent", operator's are readOnly: true |
cron_update({ id, every?, expr?, prompt?, enabled? }) | Change schedule/prompt/pause — agent jobs only |
cron_delete({ id }) | Delete — agent jobs only |
- Use for periodic work (daily checks, polling loops); use
reminder_*for one-offs. - Agent jobs persist in
acp-connector.jsoncwithmanaged: "agent"— they survive restarts. - You cannot modify operator jobs. If one needs changing, tell the user — never work around it by creating a duplicate.
Operator config (acp-connector.jsonc)
Single JSONC file next to where the bridge runs. Keys an agent may need to touch with permission:
{
"agentCmd": "devin acp",
"timezone": "America/Argentina/Tucuman", // timezone for `at` reminder times (default: system TZ)
"platforms": { "telegram": { "token": "...", "allowedChatIds": [123] } },
"cron": [ { "name": "...", "schedule": "0 9 * * *", "prompt": "...", "enabled": true, "managed": "agent" } ],
"routines": [ { "name": "briefing", "prompt": "..." } ],
"echoInjectedPrompts": true,
"logLevel": "info"
}- Reminder state lives in
.acp-connector/reminders.json— do not edit by hand; use the tools. managed: "agent"on a cron job means "the agent owns this" — set it only viacron_create, not by hand-editing (the runtime won't know).- After manual config edits the bridge must be restarted; it reloads cron/reminders on boot and delivers anything past due.
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.

