How do I install the Okdev skill?

Run npx skillmds@latest add tomevault-io/okdev in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Okdev safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Okdev?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Okdev free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

tomevault-io (@tomevault-io) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Okdev by tomevault-io — Agent Skill

Name: Okdev
Author: tomevault-io

File contents

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

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 --details.
Escalate to kubectl checks only when okdev output 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 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 — distributed by TomeVault.

---name: okdevdescription: Use when helping someone use okdev to initialize, start, inspect, connect to, sync with, troubleshoot, or tear down Kubernetes dev sessions, including manifest-backed and PyTorchJob workloads.---# okdev## OverviewUse 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 UseUse 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 SSHDo 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 Style1. 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).

Frequently asked questions

Okdev