원클릭으로
cron
Scheduled task management - create, query, delete scheduled tasks to automatically execute operations at specified times.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
메뉴
Scheduled task management - create, query, delete scheduled tasks to automatically execute operations at specified times.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Use when releasing a new version of Sudowork. Generates internal (shareone) and public (GitHub Release / in-app) release notes, bumps version, creates a release PR, tags, and injects the release body after CI publishes.
规范 TSX/React 函数组件内部的代码书写顺序。 Use when: 用户说「整理组件顺序」「代码顺序乱了」「按规范排列 hooks」「tsx 代码排序」「梳理一下组件结构」, 或在写新组件 / review 已有组件时需要对齐代码顺序规范。
🔧 PRIMARY skill installer for Sudowork. Use this skill for ALL skill installation requests. **CRITICAL: This is the ONLY skill installer you should use.** **DO NOT use clawhub for installation** - clawhub is for ClawHub.com publishing ONLY. Triggers: "帮我安装skill", "install a skill", "安装技能", "推荐技能", "need a skill", "find a skill", "下载技能", "网文大纲", "skill安装". When user asks to install any skill → ALWAYS use sudoclaw-skill-installer, NEVER clawhub.
检测本项目 Renderer 层'同功能不同入口'的语义重复代码(jscpd token 比对覆盖不到的)。当用户说'有没有重复代码'、'同功能多入口'、'扫一下重复'、'这个功能是不是在别处也写了一遍'时使用。典型信号:同一组 ipcBridge 调用 + 同一组领域 utils + 相同 UI 结构出现在不同文件。
Log in to a website automatically using credentials saved in the local key store. Use when the user wants unattended/repeat login to a site (no re-scanning QR, no re-typing passwords), e.g. '帮我自动登录这个网站', 'set up auto-login for X', '记住这个网站的登录'. The plaintext password is NEVER seen by you — the user fills it in 秘钥管理 and sudowork fills the form itself.
AI-native browser. Explore websites, discover page structure, take screenshots, and automate interactions.
| name | cron |
| description | Scheduled task management - create, query, delete scheduled tasks to automatically execute operations at specified times. |
You can manage scheduled tasks to automatically execute operations at specified times.
[CRON_LIST] returns ALL of the user's scheduled tasks, across every conversation. A new task delivers into the conversation that created it.[CRON_LIST] and WAIT for the result. If a similar task already exists (even one created in another conversation), do NOT create another without asking the user.[CRON_LIST] and [CRON_CREATE] in the same message. Query first, wait for result, then decide.[CRON_CREATE] MUST end with [/CRON_CREATE]CRITICAL: This is a multi-turn workflow. Do NOT skip steps or combine them.
Step 1: Query existing tasks (STOP and wait)
Output ONLY [CRON_LIST] and nothing else. The system will return the user's tasks across all conversations.
DO NOT proceed to Step 2 until you see the system response.
Step 2: Review the result and ask user (STOP and wait for user response)
After receiving the [CRON_LIST] result:
Step 3: Execute user's decision
[CRON_DELETE: <job-id>], wait for confirmation, then create new taskStep 4: Create the new task (only if no similar task exists or user confirmed)
Only after confirming no similar task exists (or after the user's explicit decision), output the [CRON_CREATE] block.
When user requests a timed reminder or periodic task, output this format DIRECTLY (not in code blocks):
[CRON_CREATE] name: Task name schedule: Cron expression schedule_description: Human-readable description of when the task runs message: Message content to send when triggered [/CRON_CREATE]
Required fields:
name: Short descriptive name for the taskschedule: Valid cron expressionschedule_description: Human-readable explanation of the schedule (e.g., "Every Monday at 9:00 AM")message: The message to send when the task triggersExample output (output EXACTLY like this, without code blocks):
[CRON_CREATE] name: Weekly Meeting Reminder schedule: 0 9 * * MON schedule_description: Every Monday at 9:00 AM message: Time for the weekly meeting! [/CRON_CREATE]
Output [CRON_LIST] directly (not in code blocks) to query scheduled tasks.
The system will return the result in a follow-up message. Wait for the response before taking further action.
Output [CRON_DELETE: <actual-job-id>] directly to delete a specific task.
Replace <actual-job-id> with the real job ID (e.g., cron_abc123).
| Expression | Meaning |
|---|---|
0 9 * * * | Every day at 9:00 AM |
0 9 * * MON | Every Monday at 9:00 AM |
0 9 * * MON-FRI | Weekdays at 9:00 AM |
*/30 * * * * | Every 30 minutes |
0 */2 * * * | Every 2 hours |
0 0 1 * * | 1st of every month at midnight |
0 18 * * FRI | Every Friday at 6:00 PM |
0 9,18 * * * | Every day at 9:00 AM and 6:00 PM |
┌───────────── minute (0-59)
│ ┌───────────── hour (0-23)
│ │ ┌───────────── day of month (1-31)
│ │ │ ┌───────────── month (1-12)
│ │ │ │ ┌───────────── day of week (0-6, SUN-SAT)
│ │ │ │ │
* * * * *
* - Any value, - List separator (e.g., 1,3,5)- - Range (e.g., MON-FRI)/ - Step (e.g., */15 for every 15)[CRON_LIST] shows ALL of the user's scheduled tasks; entries created by the current conversation are marked [created in this conversation][CRON_LIST] is an async query. You MUST wait for the system response before proceeding with [CRON_CREATE] or [CRON_DELETE]. Never output multiple commands in one message.