Remote Agent Scheduler

Schedule isolated remote agent runs

Use this skill for recurring remote agent jobs that run in isolated cloud environments.

Workflow

1. Determine whether the user wants to create, list, update, or run a trigger.
2. Collect repo source, environment, connectors, schedule, and prompt payload.
3. Build or inspect the trigger definition.
4. Confirm authentication, environment, and connector assumptions.
5. Return the trigger details and next management steps.

Guardrails

• Distinguish remote cloud runs from local cron jobs.
• Keep repo URL, environment ID, and schedule explicit.
• Surface setup blockers like missing auth or repo access early.

Example Requests

• Create a nightly remote agent to summarize repo health.
• Update this cloud trigger to use a different environment and cron.

Inputs

• Desired action
• Repo source
• Environment and connector context
• Cron schedule

Outputs

• Trigger definition
• Run or update confirmation
• Operational notes

Success Criteria

• The action type is clear.
• Remote environment assumptions are explicit.
• Auth and repo blockers are surfaced.

Non-Goals

• Local cron setup
• Ambiguous cloud-vs-local scheduling

Source Provenance

Derived from src/skills/bundled/scheduleRemoteAgents.ts.