okdev

DevOps Community

Skill notes

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

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

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.

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.

Fluxly profile Runtime and permissions are inferred by Fluxly static checks, not author declarations or runtime test results.
Domain
DevOps
Author-declared agents
No explicit declaration found; this is not inferred or tested compatibility
Static check
88 / 100 · heuristic scan, not runtime safety proof
Runtime evidence
Not run; no isolated runtime test evidence is currently recorded
Author / version / license
@tomevault-io · no license declared
Token usage
Lean
Setup complexity
Guided setup
External API key
Not required
Operating systems
Unspecified (assume cross-platform)
Runtime requirements
No explicit requirements detected
Detected file/system behavior
  • Read-only
  • Shell exec
Network behavior
Local-only
Install commands
None (reference only)

Heads up: Tool permissions are not declared; actual access depends on the runtime.

Author source file SKILL.md

# 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 -->

Discussion

Powered by GitHub Discussions. Sign in with GitHub to comment, react, or subscribe.