run-multiple-scans

name: run-multiple-scans description: "Run all stock scanners by dispatching staggered cron jobs 5 minutes apart. Triggered by Run, Run multiple scans, run scans."

Run Multiple Scans

Dispatch all 41 scanners via staggered cron jobs (5 minutes apart, one scanner per turn). This avoids gateway overload from firing all 41 messages simultaneously.

Trigger

When the user says any of the following (case-insensitive), run this skill immediately without asking questions: "Run", "Run multiple scans", "run scans", "Run scans", "run the scans"

How It Works

1. Create 41 one-shot cron jobs, each firing 5 minutes apart
2. Each cron job sends an agentTurn message to the coordinator's current session with the scanner's sessionKey
3. The coordinator receives the message and dispatches a single sessions_send (fire-and-forget, timeoutSeconds: 0) to that scanner
4. Each cron job auto-deletes after firing (deleteAfterRun: true)
5. Report completion after all 41 cron jobs are created

CRITICAL: Never fire all 41 sessions_send calls in one turn — this overloads the gateway and causes timeouts.

Dispatch Template

Step 1: Create staggered cron jobs

For each scanner, create a cron job 5 minutes apart:

cron({
  action: "add",
  job: {
    name: "dispatch-<scanner-name>",
    schedule: { kind: "at", at: "<ISO-8601 timestamp, 5 min apart>" },
    payload: { kind: "agentTurn", message: "DISPATCH: Send scan command to <scanner-name> at sessionKey <sessionKey>", timeoutSeconds: 60 },
    sessionTarget: "current",
    deleteAfterRun: true,
    enabled: true
  }
})

Step 2: When cron fires, dispatch the scanner

When the coordinator receives the DISPATCH message, call:

sessions_send({
  sessionKey: "<sessionKey>",
  message: "Read and run your own scanner skill now. Cover all your standard criteria and deliver results to your Discord channel.",
  timeoutSeconds: 0
})

Then reply NO_REPLY (no channel noise for each individual dispatch).

Scanner Table

Rules

• Stagger dispatches. Never send all 41 sessions_send calls in one turn. Always use staggered cron jobs 5 minutes apart.
• Fire-and-forget only. Use timeoutSeconds: 0 on all sessions_send calls. Do NOT wait for results.
• sessionTarget: "current". Cron jobs must use sessionTarget: "current" with payload.kind: "agentTurn" (non-default agents cannot use sessionTarget: "main").
• deleteAfterRun: true. Each cron job auto-deletes after firing.
• sessionKey format. Always use agent:{agentId}:discord:channel:{channelId}.
• Discord only. Every scanner posts to its own bound Discord channel.
• No questions. Start immediately on trigger.
• No channel noise. When a cron fires a DISPATCH, send the sessions_send and reply NO_REPLY.