Okdev 会话排查
- 作者仓库星标 0
- 作者仓库 skills-registry
okdev
Overview
Use this skill for end-user questions about the okdev CLI. Prefer okdev-native workflows over generic Kubernetes or SSH advice, and anchor answers in the repo docs before giving detailed guidance.
Primary docs:
docs/quickstart.mddocs/command-reference.mddocs/config-manifest.mddocs/troubleshooting.md
When to Use
Use this skill when the request involves:
okdev init,up,status,ssh,exec,cp,sync,ports,down,prune- config discovery or
.okdev.yaml/.okdev/okdev.yaml - sync behavior, session reuse, port forwards, or SSH access
- manifest-backed workloads such as
job,generic, orpytorchjob - attachable pod behavior, multi-pod sessions, or inter-pod SSH
Do not use this skill for:
- editing the
okdevsource code itself - generic cluster administration unrelated to
okdev - generic SSH or tmux advice that does not depend on
okdev
Working Style
- Identify the workload shape first: simple pod vs manifest-backed workload.
- Prefer
okdevcommands and documented config fields over low-levelkubectlworkarounds. - For troubleshooting, ask for the smallest
okdevoutput that exposes state, usuallyokdev status --details. - Escalate to
kubectlchecks only whenokdevoutput is not enough. - When the question is about multi-pod behavior, read
references/multipod.md. - When the question is about symptoms or failures, read
references/troubleshooting.md. - When the question is about normal usage flow, read
references/workflows.md.
Quick Heuristics
- Config discovery order is: explicit
--config,.okdev/okdev.yaml,.okdev.yaml,okdev.yaml. okdev upreuses an existing session workload by default.- Use
okdev up --reconcilewhen workload-shaping config changed and the user wants those changes applied. - Use
okdev sync --resetwhen local/background sync state is stale but the workload itself is still the intended one. okdev sshis the okdev-managed interactive path;ssh okdev-<session>is the plain SSH host alias path.- For sync, SSH, and port-forward issues,
okdev status --detailsis usually the first useful diagnostic.
<!-- tomevault:4.0:skill_md:2026-05-22 -->Source: acmore/okdev — distributed by TomeVault.
- 流狐分类
- 运维部署
- 作者声明 Agent
- 未找到明确声明;不据此推断已兼容或已测试
- 静态检查
- 88 / 100 · 启发式扫描,不代表运行安全
- 作者 / 版本 / 许可
- @tomevault-io · 未声明 license
- 流狐 Token 估算
- 低消耗
- 流狐接入估算
- 需简单配置
- 是否需要外部 API Key
- 未发现要求
- 检测到的系统要求
- 未声明
- 底层运行要求
- 未声明
- 检测到的文件与系统行为
-
- 只读
- Shell 执行
- 检测到的网络行为
- 仅限本地
- 安装命令数
- 无(仅作为资料)
档案由构建时根据 SKILL.md 与安装命令自动衍生,可能与作者实际意图存在差异。
需要注意: 未限定 allowed-tools,默认拥有全部工具权限。
作者没有在当前 SKILL.md 中定义固定输出样例。 Use this skill for end-user questions about the okdev CLI. Prefer okdev-native workflows over generic Kubernetes or SSH advice, and anchor answers in the repo docs before giving detailed guidance. Primary docs: docs/quickstart.md
Use this skill when the request involves: okdev init, up, status, ssh, exec, cp, sync, ports, down, prune config discovery or .okdev.yaml / .okdev/okdev.yaml
Identify the workload shape first: simple pod vs manifest-backed workload. Prefer okdev commands and documented config fields over low-level kubectl workarounds. For troubleshooting, ask for the smallest okdev output that exposes state, usually okdev status…
Config discovery order is: explicit --config, .okdev/okdev.yaml, .okdev.yaml, okdev.yaml. okdev up reuses an existing session workload by default. Use okdev up --reconcile when workload-shaping config changed and the user wants those changes applied.
# okdev
## Overview
Use this skill for end-user questions about the `okdev` CLI. Prefer `okdev`-native workflows over generic Kubernetes or SSH advice, and anchor answers in the repo docs before giving detailed guidance.
Primary docs:
- `docs/quickstart.md`
- `docs/command-reference.md`
- `docs/config-manifest.md`
- `docs/troubleshooting.md`
## When to Use
Use this skill when the request involves:
- `okdev init`, `up`, `status`, `ssh`, `exec`, `cp`, `sync`, `ports`, `down`, `prune`
- config discovery or `.okdev.yaml` / `.okdev/okdev.yaml`
- sync behavior, session reuse, port forwards, or SSH access
- manifest-backed workloads such as `job`, `generic`, or `pytorchjob`
- attachable pod behavior, multi-pod sessions, or inter-pod SSH
Do not use this skill for:
- editing the `okdev` source code itself
- generic cluster administration unrelated to `okdev`
- generic SSH or tmux advice that does not depend on `okdev`
## Working Style
1. Identify the workload shape first: simple pod vs manifest-backed workload.
2. Prefer `okdev` commands and documented config fields over low-level `kubectl` workarounds.
3. For troubleshooting, ask for the smallest `okdev` output that exposes state, usually `okdev status --details`.
4. Escalate to `kubectl` checks only when `okdev` output is not enough.
5. When the question is about multi-pod behavior, read `references/multipod.md`.
6. When the question is about symptoms or failures, read `references/troubleshooting.md`.
7. When the question is about normal usage flow, read `references/workflows.md`.
## Quick Heuristics
- Config discovery order is: explicit `--config`, `.okdev/okdev.yaml`, `.okdev.yaml`, `okdev.yaml`.
- `okdev up` reuses an existing session workload by default.
… 作者原文负责流程事实;流狐只索引当前章节、要点、文件与命令。
章节 -> Overview → When to Use → Working Style → Quick Heuristics
要点 -> Use this skill for end-user questions about the okdev CLI. · 1. Identify the workload shape first: simple pod vs manifest-backed workload. · - Config discovery order is: explicit --config, .okdev/okdev.yaml, .okdev.yaml, okdev.yaml. · --- > Source: [acmore/okdev](https://github.com/acmore/okdev) — distributed by [TomeVault](https://tomevault.io).
文件/命令 -> okdev · docs/quickstart.md · docs/command-reference.md · docs/config-manifest.md · docs/troubleshooting.md · okdev init · status · ssh
内容 SHA-256 -> 059bbd5fe500
原文结构
适用与边界
原文中的明确线索
okdev、docs/quickstart.md、docs/command-reference.md、docs/config-manifest.md、docs/troubleshooting.md、okdev init、status、ssh