Menu
Schedule deferred or recurring work via the isanagent cron tool—add/remove jobs with correct runtime context fields.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
MaxEvolve Triton/PyTorch to JAX/Pallas porting with GpuToJax 12-step pipeline, interpret=True validation, MAP-Elites evolution, and Colab/SSH hardware profiling.
Manage Google Colab sessions and execute code on remote Colab VMs via the colab-cli.
Use when you need to generate a synthetic dataset. You can use Afterimage Python package to create, conversational, tool-calling, multi-choice questions, or other types of structured output datasets for SFT, or preference data for DPO.
Configure long wall clocks and use execution_run_background + job polling for ML or hours-long runs without blocking the agent loop.
Run numeric or ML code through isanagent execution tools without flooding context—artifacts, incremental runs, sandbox paths.
Turn papers and docs into a concrete training or evaluation recipe (datasets, metrics, hyperparameters, fine-tuning code).
| name | cron |
| description | Schedule deferred or recurring work via the isanagent cron tool—add/remove jobs with correct runtime context fields. |
cron tool)Use this when the task requires you to register, update, or tear down a scheduled follow‑up message to the same or a known chat/channel.
cron.add | remove. (There is no list yet—do not assume you can enumerate jobs.)add requires: action, chat_id, channel, message, plus exactly one schedule among every_seconds, at, cron_expr.remove requires: action, job_id, chat_id, channel.Always copy chat_id and channel from the RUNTIME CONTEXT block you were given—do not invent them.
every_seconds: simple periodic nudges. Forbidden when the deployment has [multi_tenant_edge].cron_scheduling_enabled = true—the tool will error; use at or cron_expr instead.at: one shot at an ISO datetime. You must include the correct numeric timezone offset from runtime context (e.g. 2026-04-24T15:00:00+03:00). Do not default to Z unless context is UTC.cron_expr: recurring. With multi‑tenant edge cron enabled, use a 6‑field UTC expression (second minute hour day month weekday). Otherwise follow the host’s 7‑field cron rules.list allows you to view all currently active cron jobs across all chats and channels. Use this when you need to verify if a job is running or retrieve a lost job_id.add assigns the job_id (returned in the success string, e.g. Successfully scheduled job abcdef12 …). Store it in your reasoning if you may need remove later; you cannot choose the id yourself today.remove with that exact job_id.message so a future turn knows what to do when the job fires—include intent, constraints, and any ids/paths the follow‑up needs.