From 7973f494b3f3d910d698f398a63cc7b652b030f7 Mon Sep 17 00:00:00 2001
From: dodaa08 <dodaa08@users.noreply.github.com>
Date: Tue, 8 Sep 2026 00:40:17 +0530
Subject: [PATCH] Fix formatting

---
 docs/SKILLS/CronJobs.md | 15 ++++++---------
 docs/SKILLS/Email.md    | 13 +++++--------
 2 files changed, 11 insertions(+), 17 deletions(-)

diff --git a/docs/SKILLS/CronJobs.md b/docs/SKILLS/CronJobs.md
index b34b3a4..6eafc13 100644
--- a/docs/SKILLS/CronJobs.md
+++ b/docs/SKILLS/CronJobs.md
@@ -1,14 +1,11 @@
 ---
-
 name: cron
 description: "Schedule one-shot and recurring reminders via openclaw cron CLI. Use exec, NOT the cron tool (restricted to cron job context)."
 metadata:
-{
-"openclaw": {
-"emoji": "⏰",
-"requires": { "bins": ["openclaw"] }
-}
-}
+  openclaw:
+    emoji: "⏰"
+    requires:
+      bins: ["openclaw"]
 ---
 
 # Cron / Reminders
@@ -33,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 "<reminder text>"'` 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)
 
@@ -119,4 +116,4 @@ openclaw cron rm <job-id> --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 <your id> --announce --channel <plugin> --to <target>` together.
 
-> **NEVER use `--session main`.** Always use `--session isolated` + `--agent <your id>`. The `main` session target is not permitted to deliver to the user's chat and fails with `error-not-allowed`.
+> **NEVER use `--session main`.** Always use `--session isolated` + `--agent <your id>`. 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
diff --git a/docs/SKILLS/Email.md b/docs/SKILLS/Email.md
index 005914d..ff545cd 100644
--- a/docs/SKILLS/Email.md
+++ b/docs/SKILLS/Email.md
@@ -1,14 +1,11 @@
 ---
-
 name: email
 description: "Send emails via s-nail, read inbox via the fetch-emails script (reads password from env/config)."
 metadata:
-{
-"openclaw": {
-"emoji": "📧",
-"requires": { "bins": ["s-nail", "fetch-emails"] }
-}
-}
+  openclaw:
+    emoji: "📧"
+    requires:
+      bins: ["s-nail", "fetch-emails"]
 ---
 
 # Email
@@ -45,4 +42,4 @@ fetch-emails 5 <account>
 - NEVER pass $GMAIL_APP_PASSWORD in any command — fetch-emails reads it from the environment (or `~/.config/gmail/`) internally
 - Pass an explicit `<account>` 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=<email>` with s-nail when sending from a specific account
+- Use `-S from=<email>` with s-nail when sending from a specific account
\ No newline at end of file