matthew/claw-apply
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Document LinkedIn rate limit and 1-job-per-run pacing

Browse Source 
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
This commit is contained in:
Matthew Jackson
2026-03-06 15:49:35 -08:00
parent 59e410b9c4
commit 561e666323
1 changed files with 3 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
SKILL.md
View File

@@ -97,9 +97,11 @@ Scheduling is managed via OpenClaw cron jobs (not system crontab):
|-----|----------|-------------|
| Searcher | `0 */12 * * *` America/Los_Angeles | Search every 12 hours |
| Filter | `30 * * * *` America/Los_Angeles | AI filter every hour at :30 |
| Applier | `*/5 * * * *` America/Los_Angeles | 1 job per run, silent (no Telegram noise) |
| Applier | `*/3 * * * *` America/Los_Angeles | 1 job per run, silent (no Telegram noise) |
| Telegram Poller | `* * * * *` America/Los_Angeles | Process answer replies every minute |
**Rate limiting:** LinkedIn enforces a minimum ~3 minutes between applications. The applier processes 1 job per run (`max_applications_per_run: 1` in settings.json) — control pacing via the cron interval. Running more frequently or processing multiple jobs per run risks account lockout.
**Notification defaults:** all crons use `delivery: none`. The scripts send their own Telegram summaries directly — no need for OpenClaw cron announcements on top.
The lockfile mechanism ensures only one instance of each agent runs at a time.