Menu
Scheduled task management - create, query, update scheduled tasks to automatically execute operations at specified times.
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.
Based on SOC occupation classification
Maintain durable task plans, findings, and progress logs in workspace files for long-running or research-heavy work. Use when a task spans many steps or sessions, needs an auditable evidence trail, or risks losing important decisions to context limits. Do not use for short tasks that fit comfortably in the active conversation.
Turn a hiring brief into a complete job description, platform-specific recruiting copy, visual briefs, and a safely confirmed publishing flow. Use when drafting or publishing recruitment campaigns for X, Xiaohongshu, LinkedIn, or similar social and hiring platforms.
Use this skill when the user wants a .pptx with smooth cross-slide animation — PowerPoint Morph transitions, Keynote-style continuous motion, shapes that grow / move / rotate as the slide advances. Trigger on: 'morph', 'morph transition', 'smooth transition', 'continuous animation across slides', 'Keynote-style transition', 'animated slide sequence', 'shape continuity across slides'. Output is a single .pptx. This skill is a scene layer on top of officecli-pptx — inherits every pptx v2 rule (visual floor, grid, palettes, connector canon, Delivery Gate 1–5a). DO NOT invoke for a generic deck, pitch deck, or board review without cross-slide motion — route those to officecli-pptx base or officecli-pitch-deck.
Use this skill when the user is building a fundraising / investor pitch deck — seed, Series A / B / C, convertible note, SAFE round, strategic raise. Trigger on: 'pitch deck', 'investor deck', 'Series A deck', 'Series B deck', 'Series C deck', 'fundraising deck', 'seed pitch', 'VC deck', 'raising capital', 'term sheet presentation'. Output is a single .pptx. This skill is a scene layer on top of officecli-pptx — inherits every pptx v2 rule (visual floor, grid, palettes, connector canon, Delivery Gate). DO NOT invoke for a generic board review, sales deck, all-hands, or product launch — route those to officecli-pptx base.
Use this skill any time a .pptx file is involved -- as input, output, or both. This includes: creating slide decks, pitch decks, or presentations; reading, parsing, or extracting text from any .pptx file; editing, modifying, or updating existing presentations; combining or splitting slide files; working with templates, layouts, speaker notes, or comments. Trigger whenever the user mentions 'deck', 'slides', 'presentation', 'pitch', or references a .pptx filename.
Use to connect to and drive a NomiFun instance from an external agent (Claude Code / Cursor / any MCP client). Drive its browser / computer / knowledge base / files and manage the platform over MCP or REST, with a per-companion access token (you run AS the bound companion). Use this whenever the user asks to control, automate, or hand work off to "NomiFun", "their NomiFun", "the desktop companion", or a running NomiFun server.
| name | cron |
| description | Scheduled task management - create, query, update scheduled tasks to automatically execute operations at specified times. |
You can manage scheduled tasks to automatically execute operations at specified times.
[CRON_CREATE] MUST end with [/CRON_CREATE], [CRON_UPDATE] MUST end with [/CRON_UPDATE]This is a two-step workflow. Each step is one message turn.
Step 1: Query
Output [CRON_LIST] (nothing else in this message) and wait for the system response.
Step 2: Act (based on system response)
[CRON_CREATE] in this message. Do NOT ask the user for extra confirmation — they already told you what they want.[CRON_UPDATE: <job-id>] to modify in place.Output this format DIRECTLY (not in code blocks):
[CRON_CREATE] name: Task name schedule: Cron expression schedule_description: Human-readable description message: Message content [/CRON_CREATE]
Required fields:
name: Short descriptive nameschedule: Valid cron expression (see reference below)schedule_description: Human-readable schedule (e.g., "Every Monday at 9:00 AM")message: The prompt sent to the AI when triggered — must be a complete, self-contained instructionHow to write message:
The message is what the AI receives each time the task fires. It must tell the AI exactly what to do — NOT restate the user's request.
| User says | ❌ Bad message | ✅ Good message |
|---|---|---|
| "Send me hello every day at 10am" | Send me hello | Reply with exactly: Hello! |
| "Remind me to drink water daily" | Remind me to drink water | Reply with a friendly reminder to drink water |
| "Summarize AI news every Monday" | Summarize AI news | Search for the latest AI news from this week and produce a concise bullet-point summary report |
Example (output EXACTLY like this, no code blocks):
[CRON_CREATE] name: Weekly Meeting Reminder schedule: 0 9 * * MON schedule_description: Every Monday at 9:00 AM message: Reply with a short weekly meeting reminder that includes the current date and time. [/CRON_CREATE]
Use this to modify an existing task in place (preserves all associated conversations).
[CRON_UPDATE: ] name: Updated task name schedule: New cron expression schedule_description: Human-readable description message: Updated message content [/CRON_UPDATE]
Replace <job-id> with the real job ID from [CRON_LIST] result.
All four fields are required — provide the full updated values.
Output [CRON_LIST] directly. The system will return the result in a follow-up message.
Format: minute hour day-of-month month day-of-week — e.g. 0 9 * * MON-FRI = weekdays at 9:00 AM.