免费在 GitHub 公开

use-iris

Operate Iris jobs and tasks, from submission and monitoring to debugging and recovery. The skill also guides scheduling checks, coordination between clusters, controller deployments, development GPU or TPU reservations, and investigation of stuck CoreWeave pods.

中文简介正在准备中。当前显示英语简介。

原文查看原文说明

Use Iris to submit, inspect, debug, monitor, or recover jobs and tasks; diagnose scheduling and federation; deploy controllers; or reserve dev GPUs and TPUs. Use for ordinary Iris operations, including babysitting a job, controller rollouts, accelerator sessions, and stuck CoreWeave pods. Use a narrower production-run or Zephyr skill when that workflow is explicitly requested.

marin-community/marin

集成工具Kubernetes

查看安装方法

适用场景

Monitoring Iris jobs and investigating failures
Diagnosing scheduling delays and cross-cluster coordination
Deploying or rolling back controllers
Reserving GPUs or TPUs for development
Investigating CoreWeave pods stuck during termination

包含的文件（5）

SKILL.md2.9 KB
references/controller-rollout.md2.1 KB
references/dev-accelerators.md1.6 KB
references/monitor-job.md1.5 KB
references/stuck-pod.md1.9 KB

SKILL.md（原文）

安装前可以查看交给 AI 代理的指令内容。

Use Iris

Read only the material needed for the request:

Normal jobs, tasks, scheduling, auth, or CoreWeave: lib/iris/OPS.md.
Federation: lib/iris/docs/federation.md.
Continuous job monitoring: references/monitor-job.md.
Controller deploy or rollback: references/controller-rollout.md.
Interactive GPU or TPU: references/dev-accelerators.md.
Stuck terminating CoreWeave pod: references/stuck-pod.md.
Temporary task outputs: lib/iris/docs/task-outputs.md.
Logs or measurements: use query-finelog.

Resolve cluster facts from lib/iris/config/<cluster>.yaml; do not copy live coordinates from memory.

Common reads

uv run iris --cluster=<cluster> job describe <job>
uv run iris --cluster=<cluster> task describe <task>
uv run iris --cluster=<cluster> task events <task>
uv run iris --cluster=<cluster> rpc controller list-backends

For a pending federated root, inspect all three parent-side views:

uv run iris --cluster=<parent> job list --prefix <root-job>
uv run iris --cluster=<parent> rpc controller list-peers
uv run iris --cluster=<parent> query \
  "SELECT job_id, peer_id, handoff_state FROM federated_jobs WHERE job_id='<root-job>'"

Only root jobs federate; their whole tree stays on the peer. Parent job describe is the liveness source, while forwarded logs may lag. CoreWeave tasks normally read regional S3 and GCP tasks read GCS.

Temporary outputs

Write bounded diagnostics to $IRIS_OUTPUT_DIR. Iris preserves that directory as one outputs.tar.zst archive per attempt without changing the command outcome when capture fails. Find the archive URI and its uploaded, empty, failed, or unavailable state with:

uv run iris --cluster=<cluster> attempt describe <task>:<attempt>

Use direct object-storage writes for large or durable outputs. See lib/iris/docs/task-outputs.md for retention, limits, and data-access boundaries.

Boundaries

Start read-only and name the evidence that distinguishes each cause.
Never run iris cluster restart without explicit approval for the named cluster; it kills all workers and jobs.
Treat a controller restart as a deployment and require an explicitly named target.
Cancel, complete, fail, preempt, resubmit, or change Kubernetes state only when the request or selected reference authorizes that exact action.
Avoid kubectl describe pod on task pods because it can print environment values.

评价

还没有评价。欢迎分享你的使用感受。

无需登录即可发表。欢迎分享使用感受、提问，或说明在哪些环境下无法运行。

还没有评论。来写第一条吧。

同一仓库的技能

ab-test-zephyr

免费

Run an explicitly requested Zephyr control/treatment benchmark on the same pre-normalized sample and compare Finelog stage metrics.

中文简介正在准备中。当前显示原文说明。