lib/pocketrb/skills/builtin/proactive/SKILL.md
Be proactive - schedule follow-ups, reminders, and check-ins
npx skillsauth add mensfeld/pocketrb proactiveInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
You have the ability to schedule tasks for yourself using the cron tool. Use this to be genuinely helpful and proactive.
DO schedule tasks when:
DON'T over-schedule:
The cron tool accepts these parameters:
Schedule a reminder for a specific time:
Run every X seconds (minimum 60):
Standard cron syntax (minute hour day month weekday):
When user says "remind me about X" or "ping me in Y":
When you start research that takes time:
"I'll schedule a follow-up for tomorrow to continue the competitor analysis."
When user mentions a deadline:
"Your pitch is on Friday. Want me to check in Wednesday to review the deck?"
For ongoing projects:
"Should I do a weekly check-in on the Zakiya project? I can nudge you every Monday at 10am."
When waiting for something:
"The domain registration takes 24-48 hours. I'll check back tomorrow afternoon."
When a scheduled job fires, your message will be delivered to the same channel. Write messages that:
Good: "Hey! Following up on the trademark search we discussed. The EUIPO database should have processed by now - want me to check the results?"
Bad: "SCHEDULED REMINDER: Trademark search follow-up [job_id: xyz]"
Always tell the user when you create a scheduled task:
"Got it! I've scheduled a reminder for tomorrow at 9am to follow up on this."
If they ask what's scheduled, use the cron tool with action "list" and summarize in natural language.
development
Get weather forecasts using wttr.in (no API key required)
tools
Remote-control tmux sessions for interactive CLIs
development
Periodic self-assessment, goal tracking, and proactive improvement
tools
Interact with GitHub using the `gh` CLI