奥克德夫
- 作者仓库星标 0
- 作者仓库 skills-registry
- 领域
- 运维部署
- 作者声明的智能体
- 未找到明确声明;不据此推断已兼容或已测试
- 静态检查
- 88 / 100 · 启发式扫描,不代表运行安全
- 运行环境证据
- 未执行;当前没有隔离运行测试证据
- 作者 / 版本 / 许可证
- @tomevault-io · 未声明许可证
- 上下文用量评级
- 低消耗
- 接入复杂程度
- 需简单配置
- 是否需要外部接口密钥
- 不需要
- 兼容的系统
- 未声明(默认跨平台)
- 运行环境要求
- 未检出明确要求
- 检测到的文件与系统行为
-
- 只读
- 命令执行
- 网络行为
- 仅限本地
- 安装命令数
- 无(仅作为资料)
需要注意: 未声明工具权限范围;实际权限由运行环境决定。
# 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.
- Use `okdev up --reconcile` when workload-shaping config changed and the user wants those changes applied.
- Use `okdev sync --reset` when local/background sync state is stale but the workload itself is still the intended one.
- `okdev ssh` is the okdev-managed interactive path; `ssh okdev-<session>` is the plain SSH host alias path.
- For sync, SSH, and port-forward issues, `okdev status --details` is usually the first useful diagnostic.
---
> Source: [acmore/okdev](https://github.com/acmore/okdev) — distributed by [TomeVault](https://tomevault.io).
<!-- tomevault:4.0:skill_md:2026-05-22 -->
章节与文件索引
按说明文件中的顺序排列。
概述
何时使用
工作作风
快速启发法
文件/命令 -> okdev · docs/quickstart.md · docs/command-reference.md · docs/config-manifest.md · docs/troubleshooting.md · okdev init · status · ssh
内容校验值 -> 059bbd5fe500
当前原文的自动摘译,尚未人工审校。
概述
使用此技能来解答最终用户有关
okdevCLI 的问题。与通用 Kubernetes 或 SSH 建议相比,更喜欢okdev原生工作流程,并在提供详细指导之前将答案锚定在存储库文档中。主要文档:docs/quickstart.mddocs/command-reference.mddocs/config-manifest.md何时使用
当请求涉及以下内容时使用此技能:
okdev init、up、status、ssh、exec、cp、sync、ports、down、prune配置发现或.okdev.yaml/.okdev/okdev.yaml同步行为、会话重用、端口转发或 SSH 访问清单支持的工作负载,例如job、generic或pytorchjob工作作风
首先确定工作负载形状:简单 Pod 与清单支持的工作负载。与低级的
kubectl解决方法相比,更喜欢okdev命令和记录的配置字段。为了进行故障排除,请要求公开状态的最小okdev输出,通常是okdev status --details。仅当okdev输出不够时升级到kubectl检查。当问题涉及多 Pod 行为时,请阅读references/multipod.md。快速启发法
配置发现顺序为:显式的
--config、.okdev/okdev.yaml、.okdev.yaml、okdev.yaml。默认情况下,okdev up重用现有的会话工作负载。当工作负载调整配置发生更改并且用户希望应用这些更改时,请使用okdev up --reconcile。当本地/后台同步状态过时但工作负载本身仍然是预期的时,请使用okdev sync --reset。okdev ssh是okdev管理的交互路径;ssh okdev-<session>是普通的 SSH 主机别名路径。