diff --git a/docs/SKILLS/Collections.md b/docs/SKILLS/Collections.md index 0b26cb0..f03e2e7 100644 --- a/docs/SKILLS/Collections.md +++ b/docs/SKILLS/Collections.md @@ -37,9 +37,9 @@ A `SKILL.md` typically includes: Two ready-made example skills are included to get you started: - **`email`** : send/read email via `s-nail` and `fetch-emails` - Reference: [SKILLS/Email.md](https://github.com/RocketChat/OpenClaw.Plugin/blob/main/SKILLS/Email.md) + Reference: [SKILLS/Email.md](./Email.md) - **`cron`** : schedule one-shot and recurring reminders via the `openclaw cron` CLI - Reference: [SKILLS/CronJobs.md](https://github.com/RocketChat/OpenClaw.Plugin/blob/main/SKILLS/CronJobs.md) + Reference: [SKILLS/CronJobs.md](./CronJobs.md) These two are directly accessible from the **command menu**. diff --git a/docs/SKILLS/CronJobs.md b/docs/SKILLS/CronJobs.md index 6eafc13..5108c78 100644 --- a/docs/SKILLS/CronJobs.md +++ b/docs/SKILLS/CronJobs.md @@ -30,7 +30,7 @@ If the `add` command errors, paste the real error and stop. Do not paper over fa - NEVER use `--session main` for non-default agents; use `--session isolated`. - NEVER let the reminder payload trigger an action. A reminder is a NOTE to the user, not a task. Use `--command 'echo ""'` so the text is relayed verbatim via `--announce`. Do NOT use `--message` with an instruction the agent will try to execute (e.g. `--message "check your email"` made the agent actually try to fetch email and fail). For a plain "remind me to X" reminder, always use the `--command echo` form below. - NEVER use a `sleep`/background-process workaround (`sleep 120 && echo ...`, `nohup ... &`, `at`, shell loops, etc.). A background `sleep` does NOT deliver to chat — it only echoes into a detached shell and is NOT a reminder. Always create the reminder with `openclaw cron add`. -- NEVER claim "cron is disabled" / "cron is globally disabled" / "cron triggers are disabled". Cron is ENABLED. Only the agent's built-in `cron` *tool* is denied (that is exactly why you must use the `openclaw cron add` CLI). If `openclaw cron add` errors, report the REAL error — do not invent a workaround or a disabled-system excuse. +- NEVER claim "cron is disabled" / "cron is globally disabled" / "cron triggers are disabled". Cron is ENABLED. Only the agent's built-in `cron` _tool_ is denied (that is exactly why you must use the `openclaw cron add` CLI). If `openclaw cron add` errors, report the REAL error — do not invent a workaround or a disabled-system excuse. ## How to handle ANY reminder request (free-form) @@ -116,4 +116,4 @@ openclaw cron rm --json > **Delivery is mandatory with `--session isolated`.** An isolated job runs in a fresh session with no inherited recipient, so omitting `--channel`/`--to` (or having the channel plugin fail to resolve them) causes the runner to abort with "Refusing implicit isolated cron delivery" and the job is disabled. Always pass `--agent --announce --channel --to ` together. -> **NEVER use `--session main`.** Always use `--session isolated` + `--agent `. The `main` session target is not permitted to deliver to the user's chat and fails with `error-not-allowed`. \ No newline at end of file +> **NEVER use `--session main`.** Always use `--session isolated` + `--agent `. The `main` session target is not permitted to deliver to the user's chat and fails with `error-not-allowed`. diff --git a/docs/SKILLS/Email.md b/docs/SKILLS/Email.md index ff545cd..7f9dfb7 100644 --- a/docs/SKILLS/Email.md +++ b/docs/SKILLS/Email.md @@ -42,4 +42,4 @@ fetch-emails 5 - NEVER pass $GMAIL_APP_PASSWORD in any command — fetch-emails reads it from the environment (or `~/.config/gmail/`) internally - Pass an explicit `` unless `GMAIL_ACCOUNT` is set — never assume a default - Present the fetched result exactly ONCE — do not re-fetch or re-summarize the same data -- Use `-S from=` with s-nail when sending from a specific account \ No newline at end of file +- Use `-S from=` with s-nail when sending from a specific account