cron-helper▌
tclawde/openclaw-skills-user · updated Apr 8, 2026
MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.
Purpose: Guides me to use openclaw cron CLI for time-based tasks and send logs on create/remove.
Cron Helper Skill
Purpose: Guides me to use openclaw cron CLI for time-based tasks and send logs on create/remove.
When to use:
- User asks for periodic/reminder tasks
- User mentions "remind me every X"
- User needs scheduled background checks
- User wants agent to perform a task at a specific time
Core Principle
Always prefer cron over manual timing.
Reason: I lack an internal clock. Manual "track time yourself" fails because I can get absorbed in reading/thinking and lose track of time. Cron is an external clock that works reliably.
Main vs Isolated Session
Isolated Session (RECOMMENDED for tasks) ✅ Best Practice
Use --session isolated when you want the agent to actually perform a task:
- Agent receives the message and executes it
- Can use tools (exec, read, message, etc.)
- Can deliver output to a channel
- Does not pollute main conversation history
Format:
openclaw cron add \
--name "job_name" \
--cron "0 9 * * *" \
--session isolated \
--message "Task instructions for the agent" \
--deliver \
--channel feishu
Main Session (simple notifications only)
Use --session main with --system-event for simple notifications only:
- Just displays a message in main chat
- Agent does NOT execute any tasks
- No tool calls, no delivery
Format:
openclaw cron add \
--name "reminder" \
--at "+30m" \
--session main \
--system-event "Reminder: check email"
How I Should Respond
Step 1: Detect the request
Keywords: "every", "remind", "schedule", "定时", "每小时/每天/每周", "在X分钟后执行"
Step 2: Ask for details
Get from user:
- What - task description or notification message
- When - schedule (e.g., "every 2 hours", "at 9am daily", "in 10 minutes")
- Delivery - does output need to be sent to a chat? (default: no)
- Name - job name (optional, auto-generated if not provided)
Step 3: Create cron job
For agent tasks (RECOMMENDED):
openclaw cron add \
--name "task_name" \
--at "+10m" \
--session isolated \
--message "Your task instructions here" \
--deliver \
--channel feishu
For simple reminders:
openclaw cron add \
--name "reminder" \
--at "+10m" \
--session main \
--system-event "Your reminder message"
Remove a cron job:
openclaw cron rm <job_id>
List all cron jobs:
openclaw cron list
Other useful commands:
openclaw cron status # 查看调度器状态
openclaw cron run <job_id> # 立即触发任务
openclaw cron enable <job_id> # 启用任务
openclaw cron disable <job_id> # 禁用任务
openclaw cron runs <job_id> # 查看执行历史
Delivery Options
When using --session isolated, you can deliver output to a chat:
| Option | Description |
|---|---|
--deliver |
Enable delivery (required for channel output) |
--channel <name> |
Channel: feishu, telegram, slack, whatsapp, etc. |
--to <dest> |
Channel-specific target (chat ID, phone, etc.) |
--post-mode full |
Post full output instead of summary |
Examples:
# Deliver to Feishu
--deliver --channel feishu
# Deliver to Telegram
--deliver --channel telegram --to "-1001234567890"
# Deliver with full output
--deliver --channel feishu --post-mode full
Common Options
| Option | Description |
|---|---|
--cron <expr> |
Cron expression (5-field or 6-field with seconds) |
--every <duration> |
Run every duration (e.g., 10m, 1h) |
--at <when> |
Run once at time (ISO or +duration, supports m/s) |
--tz <iana> |
Timezone (default: local) |
--session main|isolated |
Target session (default: main) |
--system-event <text> |
System event payload (main session only) |
--message <text> |
Agent message payload (isolated session only) |
--delete-after-run |
Delete one-shot job after success |
--disabled |
Create job in disabled state |
Step 4: Send log
On CREATE/REMOVE only:
After creating or removing cron jobs, send ONE log with the exact command:
Log format:
# 新增任务
[HH:MM] CRON ✅
$ openclaw cron add \
--name "job_name" \
--at "+10m" \
--session isolated \
--message "task description" \
--deliver \
--channel feishu
# 删除任务
[HH:MM] CRON ❌
$ openclaw cron rm <job_id>
Examples:
# 新增
[21:30] CRON ✅
$ openclaw cron add \
--name "daily-summary" \
--cron "0 9 * * *" \
--tz "Asia/Shanghai" \
--session isolated \
--message "总结今天的工作" \
--deliver \
--channel feishu
# 删除
[21:41] CRON ❌
$ openclaw cron rm 983a0f0e-0976-414a-b3d0-fd09c533e301
Key points:
- Send log ONLY on create/remove, NOT on execution
- Keep it minimal: One command block, no extra text
Cron → Human mapping (五位 - 分时日月周):
*/5 * * * *→ 每5分钟*/30 * * * *→ 每30分钟0 * * * *→ 每1小时0 */2 * * *→ 每2小时0 9 * * *→ 每天1次(09:00)0 10,22 * * *→ 每天2次(10:00,22:00)0 9 * * 1→ 每周1次(周一09:00)
Cron → Human mapping (六位 - 秒分时日月周):
*/1 * * * * *→ 每1秒*/5 * * * * *→ 每5秒*/30 * * * * *→ 每30秒
Best Practice Summary
| Use Case | Session | Payload | Delivery |
|---|---|---|---|
| Agent performs task | isolated |
--message |
--deliver ✅ |
| Simple notification | main |
--system-event |
❌ |
Rule of thumb: If you want the agent to do something (use tools, send messages), use --session isolated + --message.
What NOT To Do
❌ Don't say "I'll set a reminder myself"
❌ Don't try to track time manually
❌ Don't use --system-event when you need the agent to execute tasks
❌ Don't forget --deliver when you need output sent to chat
❌ Don't send execution logs (only log on create/remove)
✅ Always use the openclaw cron CLI
✅ Use --session isolated for agent tasks
✅ Use --session main for simple notifications only
✅ Send log on create/remove only
✅ Keep log simple and clean
Common Schedule Patterns
五位 Cron(分 时 日 月 周)
| Frequency | Cron Expression | CLI Flag |
|---|---|---|
| Every 5 min | */5 * * * * |
--cron "*/5 * * * *" |
| Every 30 min | */30 * * * * |
--cron "*/30 * * * *" |
| Every hour | 0 * * * * |
--cron "0 * * * *" |
| Every 2 hours | 0 */2 * * * |
--cron "0 */2 * * *" |
| Daily at 9am | 0 9 * * * |
--cron "0 9 * * *" |
| Twice daily (10am, 10pm) | 0 10,22 * * * |
--cron "0 10,22 * * *" |
| Weekly (Monday 9am) | 0 9 * * 1 |
--cron "0 9 * * 1" |
六位 Cron(秒 分 时 日 月 周)
| Frequency | Cron Expression | CLI Flag |
|---|---|---|
| Every 1 second | */1 * * * * * |
--cron "*/1 * * * * *" |
| Every 5 seconds | */5 * * * * * |
--cron "*/5 * * * * *" |
| Every 30 seconds | */30 * * * * * |
--cron "*/30 * * * * *" |
Duration flags:
| Frequency | CLI Flag |
|---|---|
| Every 10 minutes | --every "10m" |
| Every 2 hours | --every "2h" |
| Once in 20 minutes | --at "+20m" |
| Once in 20 seconds | --at "+20s" |
Loaded automatically when skill is installed.
How to use cron-helper on Cursor
AI-first code editor with Composer
Prerequisites
Before installing skills in Cursor, ensure your development environment meets these requirements:
- ›Cursor installed and configured on your development machine
- ›Node.js version 16.0+ with npm package manager (verify with
node --version) - ›Active project directory or workspace where you want to add cron-helper
Execute installation command
Execute the skills CLI command in your project's root directory to begin installation:
The skills CLI fetches cron-helper from GitHub repository tclawde/openclaw-skills-user and configures it for Cursor.
Select Cursor when prompted
The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:
Verify installation
Confirm successful installation by checking the skill directory location:
Reload or restart Cursor to activate cron-helper. Access the skill through slash commands (e.g., /cron-helper) or your agent's skill management interface.
Security & Verification Notice
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.
List & Monetize Your Skill
Submit your Claude Code skill and start earning
Use Cases▌
User Story & Requirements Generation
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Competitive Analysis
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Roadmap Prioritization
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
Make data-driven prioritization decisions faster
Stakeholder Communication
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Implementation Guide▌
Prerequisites
- ›Claude Desktop or compatible AI client
- ›Access to product documentation and roadmap tools (Jira, Notion, etc.)
- ›Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
- ›Stakeholder contact information and communication channels
Time Estimate
30-60 minutes to see productivity improvements
Installation Steps
- 1.Install product management skill
- 2.Start with user story generation for known feature
- 3.Progress to competitive analysis: research 2-3 competitors
- 4.Use for roadmap prioritization: apply RICE/ICE scoring
- 5.Draft stakeholder communications and refine based on feedback
- 6.Build template library for recurring PM tasks
- 7.Share effective prompts with product team
Common Pitfalls
- ⚠Not validating competitive research—verify facts before sharing
- ⚠Accepting user stories without involving engineering team
- ⚠Over-relying on frameworks without qualitative judgment
- ⚠Not customizing outputs to company culture and communication style
- ⚠Skipping stakeholder validation of generated requirements
Best Practices▌
✓ Do
- +Validate research and competitive analysis with real data
- +Collaborate with engineering when generating technical requirements
- +Customize frameworks and templates to your company context
- +Use skill for first drafts, refine with stakeholder input
- +Document successful prompt patterns for PM tasks
- +Combine AI efficiency with human judgment and intuition
✗ Don't
- −Don't publish competitive analysis without fact-checking
- −Don't finalize user stories without engineering review
- −Don't make prioritization decisions solely on AI scoring
- −Don't skip customer validation of generated requirements
- −Don't ignore company-specific context and culture
💡 Pro Tips
- ★Provide context: company goals, constraints, customer feedback
- ★Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
- ★Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
- ★Use skill for 70% generation + 30% customization to company needs
When to Use This▌
✓ Use When
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid When
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
Learning Path▌
- 1Basic: user stories, feature specs, status updates
- 2Intermediate: competitive analysis, prioritization frameworks, PRDs
- 3Advanced: product strategy, go-to-market planning, OKR setting
- 4Expert: product vision, market positioning, business model innovation
Discussion
Product Hunt–style comments (not star reviews)- No comments yet — start the thread.
Ratings
4.5★★★★★25 reviews- ★★★★★Nikhil Nasser· Dec 24, 2024
We added cron-helper from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
- ★★★★★Neel Chawla· Dec 20, 2024
Solid pick for teams standardizing on skills: cron-helper is focused, and the summary matches what you get after install.
- ★★★★★Nikhil Ndlovu· Nov 15, 2024
cron-helper fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
- ★★★★★Nikhil Dixit· Nov 11, 2024
Registry listing for cron-helper matched our evaluation — installs cleanly and behaves as described in the markdown.
- ★★★★★Tariq Okafor· Oct 6, 2024
cron-helper has been reliable in day-to-day use. Documentation quality is above average for community skills.
- ★★★★★Dev Harris· Oct 2, 2024
Useful defaults in cron-helper — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
- ★★★★★Yash Thakker· Sep 13, 2024
cron-helper fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
- ★★★★★Yusuf Tandon· Sep 13, 2024
Solid pick for teams standardizing on skills: cron-helper is focused, and the summary matches what you get after install.
- ★★★★★Hiroshi Dixit· Sep 9, 2024
cron-helper is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
- ★★★★★Li Ramirez· Aug 28, 2024
cron-helper reduced setup friction for our internal harness; good balance of opinion and flexibility.
showing 1-10 of 25