OpenParable
Skip to content
← Back to skills

Scheduled Task Management

Productivity

Scheduled Task Management is an Agent Skill for productivity published in the B-M-Capital-Research/honeclaw repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

Register, update, cancel, and enrich user scheduled push tasks, including event-driven reminders for portfolio holdings

View on GitHub ↗
QUICK START

How to use this skill

Bring this guide into your coding agent with a prompt tailored to the tool you use.

  1. Open your project in Codex.
  2. Copy and paste the prompt below.
  3. Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/B-M-Capital-Research/honeclaw/blob/HEAD/skills/scheduled_task/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/scheduled-task-management, but wait for my approval before writing files or running scripts.

Copying this prompt does not install or run the skill. Review third-party files before use.

Scheduled Task Management Skill

Users can configure scheduled push tasks. Hone will execute them automatically at the specified time and push the result. Each user can have up to 5 scheduled tasks.

Tool Guide

ActionTool call
Add a taskcron_job(action="add", name="task name", hour=9, minute=30, repeat="workday", task_prompt="...")
List all taskscron_job(action="list")
Cancel by IDcron_job(action="remove", job_id="task id")
Cancel by namecron_job(action="remove", name="Musk")
Update by IDcron_job(action="update", job_id="task id", hour=14, minute=43)
Update by namecron_job(action="update", name="Musk", hour=14, minute=43)

Parameter Reference

repeat values:

ValueMeaning
dailyEvery day
weeklyEvery week (requires weekday, where 0 = Monday and 6 = Sunday)
workdayWeekdays only (Monday through Friday)
trading_dayTrading days only (excluding holidays)
holidayHolidays and weekends
onceRun once

push_type values:

ValueMeaning
analysisResearch briefing
portfolio_newsPortfolio news
earnings_calendarEarnings calendar
price_alertPrice threshold alert

Natural-Language Examples

  • "Every day at 8 AM" -> hour=8, minute=0, repeat="daily"
  • "9:30 AM every Monday" -> hour=9, minute=30, repeat="weekly", weekday=0
  • "9:30 AM on workdays" -> hour=9, minute=30, repeat="workday"
  • "Alert me when AAPL hits 200" -> push_type="price_alert", symbols=["AAPL"], threshold=200, direction="above"
  • task_prompt should summarize what the scheduled task should do, such as "summarize the latest portfolio updates"

Strict Rules

  • Any add, update, or cancel action must actually call the cron_job tool; never reply "updated" or "added" without calling the tool
  • Updates are single-step: call update directly, and the tool saves immediately without extra confirmation
  • You must check the success field in the tool response. If it is false, do not say the task succeeded; explain the error and retry.
  • Prefer job_id for exact matching. If job_id is unknown, you may pass a name keyword and let the tool find the unique match

Event-Driven Reminder Linkage

If the current context involves the user's holdings or a portfolio-focused scheduled task, proactively check for major events instead of delegating to another skill:

  1. Call portfolio(action="get") to inspect holdings when the user asks for portfolio-linked reminders or briefings
  2. Use data_fetch(data_type="earnings_calendar") for near-term earnings, and use web_search for other major catalysts such as product launches, FDA decisions, or management events when relevant
  3. If a major event is found within the next few days, automatically add a one-time reminder with cron_job(action="add")
  4. In the user-facing reply, explicitly say that the reminder task has already been scheduled and why