Automate
Set up a scheduled headless Claude run that sends summaries to Telegram. Use when the user wants to automate a recurring task via launchd (macOS) with push-notified results.From its SKILL.md
npx -y skills add griffinwork40/agent-framework --skill automateAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 23 stars23 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
1.5 KB, as published. Nobody here has run it
Dispatch two sub-agents in parallel:
- Scout — inspect
~/.claude/automations/(scripts, plists, existing jobs) and the target project folder to surface conventions, naming, and overlapping jobs. Report any conflicts. - Prompt designer — draft the headless Claude prompt for the recurring task. Encode the input context explicitly and require a concise Telegram-ready summary as output.
When both return, generate:
- Shell script at
~/.claude/automations/scripts/<slug>.shthatcds into the target folder and runs:claude --dangerously-skip-permissions --channels plugin:telegram@claude-plugins-official "<prompt>" - launchd plist at
~/Library/LaunchAgents/com.claude.automate.<slug>.plistwith the requestedStartCalendarIntervalorStartInterval, plusStandardOutPath/StandardErrorPathpointing at~/.claude/automations/logs/<slug>.log.
Load it: launchctl bootstrap gui/$(id -u) <plist> and confirm with launchctl list | grep <slug>.
Dispatch a verification sub-agent to run the script once manually, confirm the Telegram summary arrives, and tail the log. On failure, diagnose (permissions, path, channel config, prompt shape) and fix before exiting. Report final status, script path, plist path, and next scheduled run time.