cross-platform-scheduler
Skill298 starsChanged 6 months agoMITView on GitHub
Manage the YALC cross-platform background agent scheduler — start it, check status, or show setup instructions for keeping it alive across reboots. Use this skill when the user says: - "start my scheduled agents" - "is my scheduler running" - "how do I run agents on Windows" - "set up scheduled agents" - "agent cron", "cron for agents", "schedule agents" - "keep agents running in the background" - "scheduler status" YALC background agents are defined as YAML files in ~/.gtm-os/agents/.…
- Installs packages
In this repository37 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- answer-linkedin-commentsSkill
- build-routineSkill
- campaign-dashboardSkill
- campaign-strategySkill
- claap-weekly-recapSkill
- debuggerSkill
- enrich-with-signalsSkill
- find-lookalikesSkill
- fullenrich-content-engagersSkill
- fullenrich-event-attendeesSkill
- fullenrich-network-activationSkill
- fullenrich-plg-reverse-lookupSkill
- icp-importSkill
- import-leadsSkill
- integrate-with-yalcSkill
- launch-linkedin-campaignSkill
- lemlist-campaign-from-icpSkill
- list-adaptersSkill
- lost-deal-revival-agentSkill
- notion-reviewSkill
- personalize-messageSkill
- predictleads-dashboardSkill
- predictleads-lookalikesSkill
- predictleads-signalsSkill
- prospect-discovery-pipelineSkill
- provider-builderSkill
- qualify-leadsSkill
- research-prospectSkill
- run-competitive-intelSkill
- run-doctorSkill
- scrape-post-engagersSkill
- send-cold-emailSkill
- setupSkill
- show-routineSkill
- track-campaignsSkill
- yalc-orientationSkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 2 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 7
Use this skill when the user says:
- Very specific: line 29
If output is "No agents found", the user needs to install a framework first (framework:install <name>) or create a custom agent …
- Distinctive: line 41
Ask the user if they want the scheduler to survive reboots.
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
cross-platform-scheduler
Manage the YALC cross-platform background agent scheduler — start it, check status, or show setup instructions for keeping it alive across reboots.
Triggers
Use this skill when the user says:
- "start my scheduled agents"
- "is my scheduler running"
- "how do I run agents on Windows"
- "set up scheduled agents"
- "agent cron", "cron for agents", "schedule agents"
- "keep agents running in the background"
- "scheduler status"
What this skill does
YALC background agents are defined as YAML files in ~/.gtm-os/agents/. The cross-platform scheduler reads those YAMLs and runs each agent on its declared schedule using node-cron — no OS-level plumbing, works on macOS, Windows, and Linux.
Procedure
Step 1 — Check for agent YAMLs
Run:
npx tsx src/cli/index.ts scheduler:statusIf output is "No agents found", the user needs to install a framework first (framework:install <name>) or create a custom agent (agent:create). Stop here and guide them.
Step 2 — Start the scheduler
npx tsx src/cli/index.ts scheduler:startThis is a long-lived process. It prints each registered agent and its cron expression, then runs indefinitely.
Step 3 — Keep it alive across reboots (optional)
Ask the user if they want the scheduler to survive reboots. If yes:
Any platform (requires pm2):
npm install -g pm2
pm2 start "npx tsx /path/to/yalc-internal/src/cli/index.ts scheduler:start" --name yalc-scheduler
pm2 save
pm2 startup # follow the printed command to register with the OSmacOS only (launchd, no pm2 needed):
The existing agent:install --agent <id> command still writes a launchd plist for macOS users who prefer native scheduling.
Schedule format reference
Agent YAMLs support these schedule shapes:
# Daily at 08:00
schedule:
type: daily
hour: 8
minute: 0
# Weekly Monday at 09:00
schedule:
type: weekly
hour: 9
minute: 0
dayOfWeek: 1
# Every 30 minutes
schedule:
type: interval
intervalMinutes: 30
# Raw cron passthrough
schedule:
type: cron
expression: "0 9 * * 1-5" # weekdays at 09:00Key files
| File | Purpose |
src/lib/agents/cross-platform-scheduler.ts | Core scheduler — reads YAMLs, registers node-cron jobs |
src/lib/agents/yaml-loader.ts | Loads ~/.gtm-os/agents/*.yaml |
src/lib/agents/types.ts | AgentSchedule type (includes expression? for cron passthrough) |
src/cli/index.ts | scheduler:start and scheduler:status CLI commands |
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

