Menu
The review-first prompt is selected by default. You can switch to a direct command or download a local copy.
Read SKILL.md and any companion files shown by SkillsMP before deciding whether to install.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
A direct command skips the review prompt. Inspect the source before running it.
npx skills add https://github.com/octos-org/octos --skill cronThe command stays on one line. Scroll horizontally to inspect it before copying.
Prefer a local copy? Download the files currently available to SkillsMP.
Showing SKILL.md
List and control smart-home devices (lights, thermostats, switches, covers, speakers) via the profile's configured bridge. Triggers: smart home, turn on/off, lights, thermostat, dim, brightness, temperature, unlock, devices, 智能家居, 开灯, 关灯, 空调, 窗帘, 灯光, 设备.
Batch ASR (via dedicated ASR_API_URL or OminiX fallback), preset-voice TTS with emotion/speed control, and model management via Qwen3 models on Apple Silicon. For voice cloning and custom voice profiles, use mofa-fm. Triggers: voice, transcribe audio, text to speech, speak this, read aloud, model management, download model, 语音识别, 语音合成, 模型管理.
Summarizes a text file into a compact report. Used as a third-party compatibility harness. Triggers: summarize, summary, compat-test, harness check.
Based on SOC occupation classification
| name | cron |
| description | Schedule reminders and recurring tasks using the cron tool. |
| version | 1.0.0 |
| author | octos |
| always | true |
Use the cron tool to schedule reminders and recurring tasks.
NEVER add, remove, enable, or disable cron jobs unless the user explicitly asks you to. Do NOT proactively create scheduled tasks, reminders, or recurring jobs. Only use the cron tool when the user's message clearly requests scheduling (e.g., "remind me every day at 9am", "set up a recurring check", "schedule a task"). Listing jobs is always allowed.
{"action": "add", "name": "standup", "message": "Time for daily standup!", "every_seconds": 86400}
{"action": "add", "name": "morning", "message": "Good morning check-in", "cron_expr": "0 0 9 * * * *", "timezone": "America/Los_Angeles"}
{"action": "add", "name": "reminder", "message": "Meeting in 5 minutes", "at_ms": 1707552000000}
{"action": "list"}
By exact ID:
{"action": "remove", "job_id": "abc12345"}
By name (partial match, preferred when user says "cancel X"):
{"action": "remove", "name": "ua877"}
This removes ALL jobs whose name or message contains "ua877" (case-insensitive). Always prefer name-based removal — don't ask the user for a job ID.
{"action": "enable", "job_id": "abc12345"}
{"action": "disable", "job_id": "abc12345"}
To deliver responses to a specific channel:
{"action": "add", "name": "alert", "message": "Check metrics", "every_seconds": 3600, "channel": "telegram", "chat_id": "123456"}
IMPORTANT: Cron expressions are evaluated in UTC by default. You MUST use the timezone parameter when the user specifies a local time. Use IANA timezone names.
Before creating any cron job with a specific time, you MUST confirm the user's timezone. Ask: "What is your timezone? (e.g. America/Los_Angeles for Pacific Time, Asia/Shanghai for China Standard Time)". Do NOT guess or assume — always ask if you don't know.
Once confirmed, always include timezone in the cron tool call:
{"action": "add", "name": "daily-report", "message": "Send report", "cron_expr": "0 0 9 * * * *", "timezone": "Asia/Shanghai"}
Common timezones: America/Los_Angeles (Pacific), America/New_York (Eastern), Asia/Shanghai (China), Asia/Tokyo (Japan), Europe/London (UK), Europe/Berlin (Central Europe).
Standard 7-field cron: sec min hour day-of-month month day-of-week year
| Expression | Meaning |
|---|---|
0 0 9 * * * * | Every day at 9:00 AM (in the configured timezone) |
0 0 */2 * * * * | Every 2 hours |
0 30 9 * * 1-5 * | Weekdays at 9:30 AM |
0 0 0 1 * * * | First of every month |