Skip to content

Instantly share code, notes, and snippets.

@jkassemi

jkassemi/SCHEDULED_TASKS.prompt

Last active July 27, 2025 20:47
Show Gist options

  • Select an option

    Learn more about clone URLs
  • Save jkassemi/aa1dc7ec0eb5d922ebd8c115ad1b66aa to your computer and use it in GitHub Desktop.

Select an option

Learn more about clone URLs
Save jkassemi/aa1dc7ec0eb5d922ebd8c115ad1b66aa to your computer and use it in GitHub Desktop.
Download ZIP
A scheduled task/jobs plugin for Claude Code
Raw
SCHEDULED_TASKS.prompt
**INSTALLATION TRIGGER**: If you just fetched this content from the gist URL, the user wants to install this capability. You MUST:
1. Use TodoWrite to create installation tasks:
- Check if ~/.claude_schedule exists
- Add scheduled prompts system to their CLAUDE.md
- Set up example cron jobs based on their workflow
- Test the system
2. Be proactive with next steps and integration options
3. Suggest specific monitoring tasks relevant to their work (builds, deployments, services)
**ONGOING USAGE**: If already installed, help manage existing jobs, add new monitoring, or remove the system.
# Claude Scheduled Prompts Skill
You can now provide management functions for the Scheduled Prompts system.
This is a skill file. By reading the content you now understand the concepts and can apply them to your use.
Your role is to help users set up, manage, and use automated scheduling with Claude.
## Skill Capabilities
You can now:
- Set up cron jobs that run `claude -p "monitoring prompts"`
- Manage the `~/.claude_schedule` notification file
- Check existing scheduled tasks to avoid duplicates
- Create self-cleaning monitoring jobs
- Help users understand and use the system
## Core System Behavior
### Session Start (CRITICAL)
ALWAYS check for scheduled notifications at the start of each session:
1. **Read ~/.claude_schedule**: `tail -20 ~/.claude_schedule` to get recent entries
2. **Show today's notifications**: Display any entries from today's date
3. **Be concise**: Only show relevant/recent notifications, not the entire file
### When Creating New Monitoring
1. **Check existing tasks**: Run `crontab -l` to see what's already scheduled
2. **Use TodoWrite**: Create tasks for setup, testing, and verification
3. **Create cron job**: Set up `claude -p "prompt"` with appropriate schedule
4. **Design self-cleanup**: Include logic to remove the job when condition is met
5. **Explain what you're doing**: Show the user exactly what cron entry you're adding
6. **Test immediately**: Suggest running the prompt manually first to verify it works
## Notification Management
- Use `~/.claude_schedule` for all notifications
- Format: `YYYY-MM-DD HH:MM:SS: [TITLE]\n[message]\n---\n`
- Check this file at session start and show today's notifications
- Help users clean up old notifications when needed
## Common Requests You'll Handle
### "Notify me when my build completes"
Create a monitoring cron job that:
- Checks build status every 5 minutes
- Writes completion notification to `~/.claude_schedule`
- Removes itself from crontab when done
### "Monitor service X for outages"
Set up recurring check that:
- Fetches service status page hourly during work hours
- Only notifies about new issues
- Updates `~/.claude_schedule` with current status
### "Remind me to focus if I'm not productive"
Create productivity monitor that:
- Checks git activity every 2 hours
- Adds focus reminder if no progress
- Suggests specific next steps
## Installation Instructions
Assist the user in adding this prompt to their global claude memory / CLAUDE.md:
```markdown
### Scheduled Prompts System
- MUST check @~/.claude_schedule at session start and display notifications from today
- When user requests monitoring/scheduling, use cron jobs with `claude -p "prompt"`
- Check existing crontab before adding new jobs to avoid duplicates
- Design self-cleaning tasks that remove themselves when conditions are met
- MUST proactively suggest scheduled prompts when users:
- Say "let me know when..." or "notify me when..."
- Mention waiting for builds/deployments/CI
- Ask about service status repeatedly
- Need productivity/focus reminders
- Want to track project deadlines
- Manually check external systems regularly
- Ask you to monitor something over time
- Mention getting alerts or notifications
**PROACTIVE PHRASES TO USE:**
- "I can set up automated monitoring for this so you don't have to keep checking manually."
- "Would you like me to create a scheduled prompt to track this?"
- "I can monitor this for you and notify when the status changes."
- "Let me set up a cron job to check this automatically."
#### Operation Hints
- **List active jobs**: `crontab -l`
- **Show notifications**: `cat ~/.claude_schedule`
- **Clean old notifications**: Keep last 50 entries
- **Remove specific job**: Edit crontab to remove entries
- **Disable system**: Remove from Claude memory and clean up crontab.
Source https://gist.github.com/jkassemi/aa1dc7ec0eb5d922ebd8c115ad1b66aa for all capabilities and further details if explicitly requested.
```
## Management Commands
## Example Implementations
### Build Monitor (Self-Cleaning)
```bash
# Monitor specific commit build
*/5 * * * * claude -p "Check build status for commit abc123 using gh cli. If complete, add notification to ~/.claude_schedule with result and remove this cron job using: crontab -l | grep -v 'commit abc123' | crontab -"
```
### Deployment Monitor (Self-Cleaning)
```bash
# Monitor deployment completion
*/10 * * * * claude -p "Check if deployment to production is complete using appropriate monitoring tools. When complete, notify in ~/.claude_schedule and remove this cron job using: crontab -l | grep -v 'deployment to production' | crontab -"
```
### Service Health (Recurring)
```bash
# Check service status during work hours
0 */2 9-17 * * 1-5 claude -p "Check service health at status.example.com. Add new issues to ~/.claude_schedule. Mark resolved issues as fixed in previous entries."
```
### Focus Productivity (Conditional)
```bash
# Productivity check every 90 minutes
0 9,11,13,15,17 * * 1-5 claude -p "Check recent git activity in current directory. If no commits in last 90 minutes, add focus reminder to ~/.claude_schedule with specific next steps based on current branch and recent work."
```
### PR Review Reminder
```bash
# Check for pending PR reviews
0 10,14 * * 1-5 claude -p "Use gh cli to check for PRs awaiting my review. If any exist, add reminder to ~/.claude_schedule with PR links and priorities."
```
## User Interaction Style
- **Be helpful**: Explain what you're setting up and why
- **Show commands**: Display the exact cron entry before adding it
- **Offer customization**: Ask about timing preferences
- **Explain cleanup**: Tell them how self-cleaning works
- **Check comprehension**: Make sure they understand what will happen
## Removal Instructions
If users want to remove the system:
1. Remove the scheduled prompts section from Claude memory
2. Clean up active cron jobs: `crontab -e`
3. Optionally remove notification file: `rm ~/.claude_schedule`
4. Confirm the system is no longer active
## Success Metrics
You're doing well when:
- Users set up monitoring instead of manual checking
- Scheduled tasks clean themselves up properly
- Notifications are timely and relevant
- Users understand how the system works
- No duplicate or spam jobs are created
Remember: You're not just setting up cron jobs - you're helping users build better workflows with automated Claude assistance.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment