brainstorming
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation).
managed-jobsLaunch and debug SkyPilot managed jobs, recovery, queues, logs, cancellation, job groups, and pools.
Independent GitHub snapshot · Automated classification · Original documentation governs
Use this sub-skill when the user needs SkyPilot sky jobs workflows: production or long-running batch/training jobs, managed spot recovery, job queues/logs/cancel, job groups, job pools, or job recovery tuning.
references/jobs-workflows.md for launch patterns, queue/log/cancel commands, SDK equivalents, managed pipelines, spot recovery, job groups, and pools.references/troubleshooting.md when a job is stuck, failed, preempted, cancelled, missing logs, confused by job IDs/names, blocked by pools, or running cloud-bound native tests.scripts/jobs_command_builder.py --help to print safe commands for launch, queue, logs, cancel, and pool operations without executing cloud actions.resources, file_mounts, volumes, envs, and secrets syntax to ../task-yaml/SKILL.md.../infrastructure-storage/SKILL.md.../serving/SKILL.md; pools here are only managed-job pools.../sdk-api-server/SKILL.md.sky jobs launch -n <job-name> <task.yaml> -y.sky jobs launch -n <job-name> --infra <infra> --cpus 2+ "python train.py" -y.-d / --detach-run, then inspect with sky jobs queue and sky jobs logs <job-id>.sky jobs queue -a, then sky jobs logs <job-id> --no-follow for user logs and sky jobs logs --controller <job-id> --no-follow for provisioning/recovery logs.sky jobs cancel <job-id> -y; use sky jobs cancel -n <name> -y only when the name identifies the active job unambiguously.sky jobs --help, sky jobs launch --help, and python sub-skills/managed-jobs/scripts/jobs_command_builder.py --help are safe local checks.sky jobs launch, pool creation, recovery, and smoke tests require configured cloud/Kubernetes resources and should be treated as cloud-bound unless the user explicitly authorizes them.