service-manage
Skill558 starsChanged 3 years agoApache-2.0View on GitHub
Manage services in Kurtosis enclaves. Add, inspect, stop, start, remove, update services. View logs, shell into containers, and execute commands. Use when you need to interact with running services.
In this repository21 other files it gives its agents.
- cleanSkill
- cli-local-buildSkill
- cluster-manageSkill
- context-manageSkill
- docker-debugSkill
- docker-local-buildSkill
- dumpSkill
- enclave-inspectSkill
- engine-manageSkill
- files-inspectSkill
- gatewaySkill
- graflokiSkill
- import-composeSkill
- k8s-clean-clusterSkill
- k8s-debug-podsSkill
- k8s-dev-deploySkill
- lintSkill
- portalSkill
- port-forwardSkill
- run-packageSkill
- starlark-devSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 1 is distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 87
Always confirm stop/start/rm succeeded:
- Distinctive: line 125
Use file artifacts in Starlark:
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Service Manage
Manage services running inside Kurtosis enclaves.
List services
# Services are shown in enclave inspect output
kurtosis enclave inspect <enclave-name>View logs
# View logs
kurtosis service logs <enclave-name> <service-name>
# Follow logs in real time
kurtosis service logs <enclave-name> <service-name> -f
# Show all logs (not just recent)
kurtosis service logs <enclave-name> <service-name> -aShell and exec
# Get an interactive shell
kurtosis service shell <enclave-name> <service-name>
# Execute a single command
kurtosis service exec <enclave-name> <service-name> -- ls -la /data
# Execute with pipes (wrap in sh -c)
kurtosis service exec <enclave-name> <service-name> -- sh -c "cat /etc/hosts | grep localhost"Inspect a service
kurtosis service inspect <enclave-name> <service-name>Shows detailed info including ports, status, and container ID.
Stop and start
# Stop a service (keeps it in the enclave, just stops the container)
kurtosis service stop <enclave-name> <service-name>
# Restart a stopped service
kurtosis service start <enclave-name> <service-name>Remove a service
kurtosis service rm <enclave-name> <service-name>Add a service manually
kurtosis service add <enclave-name> <service-name> <image>Update a service
kurtosis service update <enclave-name> <service-name>Common patterns
Verify after operations
Always confirm stop/start/rm succeeded:
# Check service state changed as expected
kurtosis enclave inspect <enclave-name>
# For start: verify the service responds
kurtosis service exec <enclave-name> <service-name> -- wget -qO- http://localhost:8080/healthCheck if a service is healthy
# HTTP health check
kurtosis service exec <enclave-name> <service-name> -- wget -qO- http://localhost:8080/health
# Check process is running
kurtosis service exec <enclave-name> <service-name> -- ps aux
# Check listening ports
kurtosis service exec <enclave-name> <service-name> -- netstat -tlnpDebug a crashing service
# Check recent logs
kurtosis service logs <enclave-name> <service-name>
# Check all logs from the start
kurtosis service logs <enclave-name> <service-name> -a
# Inspect for error status
kurtosis service inspect <enclave-name> <service-name>Copy data between services
Use file artifacts in Starlark:
# Store files from one service
artifact = plan.store_service_files(service_name="source-svc", src="/data/output", name="shared-data")
# Mount in another service
plan.add_service(name="dest-svc", config=ServiceConfig(
image="my-image",
files={"/input": artifact},
))Troubleshooting
| Symptom | Cause | Fix |
| Service won't start | Port conflict or image issue | Check logs with kurtosis service logs, verify image exists |
| Exec command hangs | Container has no shell | Use a base image with shell or exec -- /bin/sh -c "command" |
| Logs show no output | Service crashed immediately | Use kurtosis service logs -a to see full history |
| Service not listed | Wrong enclave | Run kurtosis enclave ls and kurtosis enclave inspect to find it |
| Stop has no effect | Service already stopped | Check status with kurtosis enclave inspect first |
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

