/task-manager
Creates and manages scheduled tasks, cron jobs, recurring reminders, and timers via the Task HTTP API. Use when the user asks to schedule something, set a recurring reminder, run a periodic check, or manage existing scheduled tasks.
$ npx -y skills add 0xranx/golembot --skill task-manager --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
- Slash command
/task-manager
Context preview
The summary Claude sees to decide when to auto-load this skill.
Creates and manages scheduled tasks, cron jobs, recurring reminders, and timers via the Task HTTP API. Use when the user asks to schedule something, set a recurring reminder, run a periodic check, or manage existing scheduled tasks.
SKILL.md
task-manager.SKILL.mdname: task-manager
description: "Creates and manages scheduled tasks, cron jobs, recurring reminders, and timers via the Task HTTP API. Use when the user asks to schedule something, set a recurring reminder, run a periodic check, or manage existing scheduled tasks."
Task Manager
You can create and manage scheduled tasks for the user. When the user asks you to do something periodically (e.g. "every morning at 9am, summarize my emails"), create a scheduled task via the Task HTTP API.
Recognizing Task Intent
Watch for phrases like:
- "every day/week/hour..."
- "remind me to..."
- "at 9am, do..."
- "schedule a task..."
- "periodically check..."
- "set up a cron job..."
- "create a recurring..."
- "set a timer for..."
Creating a Task
Use the Task HTTP API (running on the gateway's port):
curl -X POST http://localhost:$PORT/api/tasks \
-H "Content-Type: application/json" \
-d '{
"name": "daily-summary",
"schedule": "0 9 * * *",
"prompt": "Summarize the key updates from today",
"enabled": true,
"target": {
"channel": "feishu",
"chatId": "oc_xxxx"
}
}'Validation
Before creating a task, verify:
- The `schedule` field is a valid 5-field cron expression
- The `prompt` is non-empty and specific enough to produce useful output when run unattended
- If a `target` is provided, `channel` is required; `chatId` is optional (if omitted, the result is sent to all known chats on that channel)
If the API returns an error (non-2xx status), report the failure to the user with the error message rather than assuming success.
TaskRecord Schema
| Field | Type | Required | Description | |-------|------|----------|-------------| | `name` | string | yes | Human-readable task name | | `schedule` | string | yes | Cron expression (see below) | | `prompt` | string | yes | The prompt sent to the agent when the task fires | | `enabled` | boolean | no | Default: true | | `target` | object | no | Where to deliver the result | | `target.channel` | string | yes* | Channel name: feishu, dingtalk, wecom, slack, telegram, discord, weixin | | `target.chatId` | string | no | Chat/conversation ID. If omitted, sends to all known chats on the channel |
Common Cron Expressions
| Expression | Meaning | |-----------|---------| | `0 9 * * *` | Every day at 9:00 AM | | `0 9 * * 1-5` | Weekdays at 9:00 AM | | `*/30 * * * *` | Every 30 minutes | | `0 */2 * * *` | Every 2 hours | | `0 9 * * 1` | Every Monday at 9:00 AM | | `0 0 1 * *` | First day of each month at midnight |
Other API Endpoints
- `GET /api/tasks` — list all tasks
- `PATCH /api/tasks/:id` — update a task (partial update)
- `DELETE /api/tasks/:id` — remove a task
- `POST /api/tasks/:id/run` — execute a task immediately
Read more
name: task-manager description: "Creates and manages scheduled tasks, cron jobs, recurring reminders, and timers via the Task HTTP API. Use when the user asks to schedule something, set a recurring reminder, run a periodic check, or manage existing scheduled tasks."
Task Manager
You can create and manage scheduled tasks for the user. When the user asks you to do something periodically (e.g. "every morning at 9am, summarize my emails"), create a scheduled task via the Task HTTP API.
Recognizing Task Intent
Watch for phrases like:
- "every day/week/hour..."
- "remind me to..."
- "at 9am, do..."
- "schedule a task..."
- "periodically check..."
- "set up a cron job..."
- "create a recurring..."
- "set a timer for..."
Creating a Task
Use the Task HTTP API (running on the gateway's port):
curl -X POST http://localhost:$PORT/api/tasks \
-H "Content-Type: application/json" \
-d '{
"name": "daily-summary",
"schedule": "0 9 * * *",
"prompt": "Summarize the key updates from today",
"enabled": true,
"target": {
"channel": "feishu",
"chatId": "oc_xxxx"
}
}'Validation
Before creating a task, verify:
- The `schedule` field is a valid 5-field cron expression
- The `prompt` is non-empty and specific enough to produce useful output when run unattended
- If a `target` is provided, `channel` is required; `chatId` is optional (if omitted, the result is sent to all known chats on that channel)
If the API returns an error (non-2xx status), report the failure to the user with the error message rather than assuming success.
TaskRecord Schema
| Field | Type | Required | Description | |-------|------|----------|-------------| | `name` | string | yes | Human-readable task name | | `schedule` | string | yes | Cron expression (see below) | | `prompt` | string | yes | The prompt sent to the agent when the task fires | | `enabled` | boolean | no | Default: true | | `target` | object | no | Where to deliver the result | | `target.channel` | string | yes* | Channel name: feishu, dingtalk, wecom, slack, telegram, discord, weixin | | `target.chatId` | string | no | Chat/conversation ID. If omitted, sends to all known chats on the channel |
Common Cron Expressions
| Expression | Meaning | |-----------|---------| | `0 9 * * *` | Every day at 9:00 AM | | `0 9 * * 1-5` | Weekdays at 9:00 AM | | `*/30 * * * *` | Every 30 minutes | | `0 */2 * * *` | Every 2 hours | | `0 9 * * 1` | Every Monday at 9:00 AM | | `0 0 1 * *` | First day of each month at midnight |
Other API Endpoints
- `GET /api/tasks` — list all tasks
- `PATCH /api/tasks/:id` — update a task (partial update)
- `DELETE /api/tasks/:id` — remove a task
- `POST /api/tasks/:id/run` — execute a task immediately
Any Agent × Any Provider × Anywhere. Connect Cursor, Claude Code, OpenCode, or Codex to Slack, Telegram, Discord, Feishu, DingTalk, WeCom, WeChat — with any LLM provider.
Repo: 0xranx/golembot
Other skills on golembot.
- /escalation
Escalate unresolvable or sensitive requests to a human agent by recording an escalation entry. Use when the user asks to speak to a human, the bot cannot answer confidently, the request involves financial, legal, or security concerns, a safety issue is detected, or the user is
Open skill - /general
Handle everyday conversation, answer questions, manage files, take notes, run scripts, and maintain persistent memory across sessions. Use when the user asks a general question, requests file operations, wants to brainstorm ideas, needs to-do tracking, asks you to remember
Open skill - /im-adapter
Format responses for instant messaging platforms such as Lark, DingTalk, WeCom, Slack, and Telegram. Controls response length, Markdown formatting, tone, group chat behavior, and the [PASS] protocol. Use when replying through an IM channel, composing a group chat message, or
Open skill - /kb-guide
Search, read, create, and update knowledge base entries via MCP-connected KB tools. Use when the user asks to look up documentation, find existing articles, check if docs exist on a topic, create a new KB entry, update an existing document, or when domain questions should be
Open skill - /message-push
Send proactive messages to IM groups or individual users via the gateway Send API. Use when the user says to send, post, notify, forward, or tell someone a message on Feishu, Slack, Telegram, Discord, DingTalk, or WeCom.
Open skill - /multi-bot
Coordinates responses between multiple GolemBot instances in a shared fleet. Use when the bot operates in a group chat with other bots, needs to decide whether to respond or pass, or must call a peer bot's API to fetch cross-domain data.
Open skill

