How do I install the Ark Devspace skill?

Run npx get-skill add tomevault-io/ark-devspace 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.

What does the Ark Devspace skill do?

Run Ark from cloned source using devspace Use when this capability is needed. It is listed under AI & ML on SkillMD.

Is Ark Devspace safe to use?

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

Which AI agents work with Ark Devspace?

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 Ark Devspace free to use?

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

Who published Ark Devspace?

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

Ark Devspace by tomevault-io — Agent Skill

Name: Ark Devspace
Author: tomevault-io

File contents

Ark DevSpace

Run Ark from a cloned repository using devspace for development/PR testing.

CRITICAL: Failure Behavior

If devspace fails, you MUST STOP and report the error. Do NOT try alternative approaches like ark-cli or npm install. DevSpace failures must be diagnosed and fixed.

When to use

Testing Ark pull requests
Running Ark from source code

Prerequisites

Ark repo cloned (e.g., /workspace/ark or /workspace/agents-at-scale-ark)
Kind cluster running (use kind-setup skill if needed)
Verify cluster: kubectl cluster-info

Steps

Navigate to ark repo

cd /workspace/ark  # or /workspace/agents-at-scale-ark

Deploy with devspace (non-interactive)
```
devspace deploy
```
This deploys all components and exits. Check the exit code - if non-zero, STOP and troubleshoot.

Verify deployment succeeded

kubectl get pods -n ark-system
kubectl get pods -n cert-manager

Wait for pods to be ready

kubectl wait --for=condition=Ready pods --all -n ark-system --timeout=300s

Check services
```
kubectl get svc -n ark-system
```

Troubleshooting

Check devspace logs

ls -la .devspace/logs/
cat .devspace/logs/default.log

Common failures

"namespace not found" - Set namespace first
```
devspace use namespace ark-system
```
"image pull error" - Build images locally
```
devspace build
```

Cert-manager not ready - Wait for it

kubectl wait --for=condition=Available deployment --all -n cert-manager --timeout=120s

Cluster connectivity - Re-export kubeconfig

kind export kubeconfig --name ark-cluster --internal

If devspace exits with error

Check the exit code and error message
Check .devspace/logs/ for detailed logs
Check pod status: kubectl get pods -A
Check events: kubectl get events -A --sort-by='.lastTimestamp'
STOP and report the specific error - do not try workarounds

Cleanup

devspace purge
kubectl delete ns ark-system --ignore-not-found

Converted and distributed by TomeVault — claim your Tome and manage your conversions.

---name: ark-devspacedescription: Run Ark from cloned source using devspace Use when this capability is needed.---# Ark DevSpaceRun Ark from a cloned repository using devspace for development/PR testing.## CRITICAL: Failure Behavior**If devspace fails, you MUST STOP and report the error. Do NOT try alternative approaches like ark-cli or npm install. DevSpace failures must be diagnosed and fixed.**## When to use- Testing Ark pull requests- Running Ark from source code## Prerequisites- Ark repo cloned (e.g., `/workspace/ark` or `/workspace/agents-at-scale-ark`)- Kind cluster running (use kind-setup skill if needed)- Verify cluster: `kubectl cluster-info`## Steps1. **Navigate to ark repo** ```bash cd /workspace/ark # or /workspace/agents-at-scale-ark ```2. **Deploy with devspace (non-interactive)** ```bash devspace deploy ``` This deploys all components and exits. Check the exit code - if non-zero, STOP and troubleshoot.3. **Verify deployment succeeded** ```bash kubectl get pods -n ark-system kubectl get pods -n cert-manager ```4. **Wait for pods to be ready** ```bash kubectl wait --for=condition=Ready pods --all -n ark-system --timeout=300s ```5. **Check services** ```bash kubectl get svc -n ark-system ```## Troubleshooting### Check devspace logs```bashls -la .devspace/logs/cat .devspace/logs/default.log```### Common failures1. **"namespace not found"** - Set namespace first ```bash devspace use namespace ark-system ```2. **"image pull error"** - Build images locally ```bash devspace build ```3. **Cert-manager not ready** - Wait for it ```bash kubectl wait --for=condition=Available deployment --all -n cert-manager --timeout=120s ```4. **Cluster connectivity** - Re-export kubeconfig ```bash kind export kubeconfig --name ark-cluster --internal ```### If devspace exits with error1. Check the exit code and error message2. Check `.devspace/logs/` for detailed logs3. Check pod status: `kubectl get pods -A`4. Check events: `kubectl get events -A --sort-by='.lastTimestamp'`5. **STOP and report the specific error - do not try workarounds**## Cleanup```bashdevspace purgekubectl delete ns ark-system --ignore-not-found```---> Converted and distributed by [TomeVault](https://tomevault.io/claim/dwmkerr) — claim your Tome and manage your conversions.

Frequently asked questions

Ark Devspace